|
Bugzilla – Full Text Bug Listing |
| Summary: | yast claims dependency conflict when installing debug packages. | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Jarl Friis <jarl> |
| Component: | libzypp | Assignee: | Jan Blunck <jblunck> |
| Status: | RESOLVED WONTFIX | QA Contact: | Duncan Mac-Vicar <dmacvicar> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | coolo, hmuelle, schubi |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | 64bit | ||
| OS: | openSUSE 10.3 | ||
| Whiteboard: | |||
| Found By: | Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | y2logs.tar.bz2 | ||
Created attachment 179807 [details]
y2logs.tar.bz2
You probably need this one, created with "Generate Dependecy Resolver test case" menu command.
not my playground Is it possible getting a testcase ?: http://en.opensuse.org/Bugs/YaST#I_want_to_report_a_bug_related_to_package_dependencies_and_libzypp_solver._Which_logs_to_attach.3F (In reply to comment #4 from Stefan Schubert) > Is it possible getting a testcase ?: > http://en.opensuse.org/Bugs/YaST#I_want_to_report_a_bug_related_to_package_dependencies_and_libzypp_solver._Which_logs_to_attach.3F > This link states: "Since openSUSE 10.2/SLES10 SP1 you can create additional information by selecting the menu entry: Extras/Generate_Dependency_Resolver_Test_Case in the single package selection frame." This is exactly was I have provided in comment #1 Is anything else needed? Ups, sorry my fault. Yes you are right. There should be also an update of glibc-debuginfo on the updated stack. Only glibc is available. Harald ? We do not release debuginfo packages for 10.3 yet. comment #7: So I cannot do very much here. (In reply to comment #7 from Harald Mueller-Ney) > We do not release debuginfo packages for 10.3 yet. > Many questions arises: 1) Just because you don't release debuginfo packages for 10.3 yet, this bug shouldn't be marked WONTFIX, rather INVALID because it is apparently related to a feature which you haven't released (yet). 2) Why don't you release debuginfo packages for 10.3 (yet) ? The main reason I wanted to install these debug packages in the first place was to provide you with more usefull information in a nother bug. (see bug 330615 comment 6) 3) Now that apparently have decided that you do not release debuginfo packages for 10.3 (yet), why does this unreleased feature show up in the YAST package manager? Basically why is there a user interface for a non-released feature. Jarl |
I have a quite normal AMD64 bit installation. I have update everything until now, which happens to include glibc (from version 2.6.1-18 to 2.6.1-18.2 Now I want to install glibc-debuginfo (which depends on glibc, actually it depends on glibc-2.6.1-18. Which gives me this strange dependency conflict: #### YaST2 conflicts list - generated 2007-10-22 21:15:20 #### This would invalidate atom:glibc-2.6.1-18.2.x86_64. atom:glibc-2.6.1-18.2.x86_64 has unfulfilled requirements === atom:glibc-2.6.1-18.2.x86_64 === atom:glibc-2.6.1-18.2.x86_64 will be evaluated for installation (freshened) by glibc-2.6.1-18.2.x86_64 (glibc == 2.6.1-18.2) glibc-2.6.1-18.2.x86_64 provides glibc == 2.6.1-18.2, but is scheduled to be uninstalled. glibc-2.6.1-18.2.i586[Update] provides glibc == 2.6.1-18.2, but another version of that package is already installed. Can't satisfy requirement glibc >= 2.6.1-18.2 for atom:glibc-2.6.1-18.2.x86_64 (null) Conflict Resolution: ( ) delete glibc #### YaST2 conflicts list END ### To be honest I feel quite comfortable with the basics of RPM, yet I find this message strange. Somehow I have an idea that this is an issue solely for 64bit package installations, but I may be wrong. How do I install debug packages for packages that has already been updated?