Bug 393192

Summary: Yast refuses to install the glibc-debuginfo package
Product: [openSUSE] openSUSE 10.3 Reporter: Bart Van Assche <bart.vanassche>
Component: Update ProblemsAssignee: Stephan Kulow <coolo>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Major    
Priority: P5 - None CC: lslezak
Version: Final   
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE 10.3   
Whiteboard:
Found By: Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Screenshot with Yast2 warning.
Yast2 logs

Description Bart Van Assche 2008-05-21 16:01:01 UTC
This issue can be reproduced as follows:
* Install OpenSUSE 10.3.
* Perform an online update.
* Add the debug repository to the software repositories.
* Try to install glibc-debug.
* Result: yast displays an error message that installing glibc-debug would invalidate the atom glibc-2.6.1-18.3.i586.

This might be caused because the debug RPM's are missing in the repository with online updates (http://download.opensuse.org/update/10.3/rpm/x86_64/).

I experienced this issue not only on x86_64, but also on ppc.
Comment 1 Bart Van Assche 2008-05-21 16:01:42 UTC
Created attachment 217347 [details]
Screenshot with Yast2 warning.
Comment 2 Robert Vojcik 2008-05-22 15:05:46 UTC
Hello, 

send please all yast2 logs.
If you are unsure follow: http://en.opensuse.org/Bugs/YaST

Thanks !
Comment 3 Bart Van Assche 2008-05-22 17:40:18 UTC
Created attachment 217602 [details]
Yast2 logs
Comment 4 Bart Van Assche 2008-05-22 17:40:47 UTC
Provided the requested Yast2 logs.
Comment 5 Ladislav Slezák 2008-05-27 07:48:52 UTC
The problem is that the debug info for the updated glibc package is missing.

The update repo (http://download.opensuse.org/update/10.3/rpm/x86_64/) contains glibc-2.6.1-18.3.x86_64.rpm while the debug repo (http://download.opensuse.org/distribution/10.3/repo/debug) contains glibc-debuginfo-2.6.1-18.x86_64.rpm.

I don't know what's the policy for debug info of updated packages and who is resposible for this problem. Coolo?
Comment 6 Stephan Kulow 2008-05-27 07:53:42 UTC

*** This bug has been marked as a duplicate of bug 233122 ***