Bug 199819

Summary: zmd cannot resolve dependencies because of conflicting i586/i686 package, yet YaST can.
Product: [openSUSE] SUSE Linux 10.1 Reporter: Forgotten User --EoyBps8f <forgotten_--EoyBps8f>
Component: ZenworksAssignee: Jawaad Tariq <jtariq>
Status: RESOLVED FIXED QA Contact: Mauro Parra Miranda <mauro>
Severity: Critical    
Priority: P5 - None CC: andreas.hanke, schubi, suse-beta
Version: Final   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: zmd-backend.log
zmd-messages

Description Forgotten User --EoyBps8f 2006-08-16 19:04:30 UTC
When I try to update the ffmpeg-packages I get the following error. YaST does install this without any problems from the same source.

To me it seems that zmd runs in a circle with this, if I understand the message correctly.

Unresolved dependencies:
Updating ffmpeg-0.4.9-6.pm.svn20060811.i586[System packages] to ffmpeg-0.4.9-7.pm.svn20060815.i586[20060808-231413]

libffmpeg0-0.4.9-6.pm.svn20060811.i586[System packages] provides libffmpeg0 == 0.4.9-6.pm.svn20060811, but is scheduled to be uninstalled.

Can't satisfy requirement libffmpeg0 == 0.4.9-6.pm.svn20060811 for ffmpeg-0.4.9-6.pm.svn20060811.i586[System packages]

Can't install ffmpeg-0.4.9-7.pm.svn20060815.i686[20060808-231413], since ffmpeg-0.4.9-7.pm.svn20060815.i586[20060808-231413] is already marked as needing to be installed

Marking this resolution attempt as invalid.
Comment 1 Forgotten User --EoyBps8f 2006-08-23 04:56:26 UTC
Got another one. both packages could be updated, but are not because of i586-i686 issues.

Unresolved dependencies:
Updating amarok-xine-1.4.1-37.1.i586[System packages] to amarok-xine-1.4.2-3.1.i586[20060711-195659]
amarok-1.4.1-37.1.i586[System packages] provides amarok == 1.4.1-37.1, but is scheduled to be uninstalled.
Can't satisfy requirement amarok == 1.4.1 for amarok-xine-1.4.1-37.1.i586[System packages]
Can't install amarok-xine-1.4.2-1.guru.suse101.i686[guru], since amarok-xine-1.4.2-3.1.i586[20060711-195659] is already marked as needing to be installed
Marking this resolution attempt as invalid.
Comment 2 Jawaad Tariq 2006-09-07 22:07:22 UTC
Do you have the zypp/zmd patches installed from online update?
Comment 3 Forgotten User --EoyBps8f 2006-09-07 23:52:28 UTC
Yes, all offered updates are installed.
Comment 4 Forgotten User --EoyBps8f 2006-09-19 23:20:35 UTC
This is still valid after today's zmd update and there is another bug, since it does not really matter whether those packages are i686 or i586 on a i686 system.

Unresolved dependencies:
Updating ffmpeg-0.4.9-7.pm.svn20060817.i686[System packages] to ffmpeg-0.4.9-7.pm.svn20060918.i686[20060808-231413]
faac-1.25-0.pm.0.i586[20060808-231413] provides faac == 1.25-0.pm.0, but has another architecture.
There are no installable providers of faac >= 1.25 for ffmpeg-0.4.9-7.pm.svn20060918.i686[20060808-231413]

libffmpeg0-0.4.9-7.pm.svn20060817.i686[System packages] provides libffmpeg0 == 0.4.9-7.pm.svn20060817, but is scheduled to be uninstalled.
Can't satisfy requirement libffmpeg0 == 0.4.9-7.pm.svn20060817 for ffmpeg-0.4.9-7.pm.svn20060817.i686[System packages]
Comment 5 Andreas Hanke 2006-09-19 23:48:30 UTC
zypp does not switch the architecture of installed packages for a reason. It will break things (unlikely on i686 with i586/i686 packages, but *fatal* on x86_64 with ix86/x86_64 packages).

This does usually not constitute a problem with SUSE packages because they don't switch architectures, but it can be a problem with 3rd party packages.

Maybe the i586/i686 switch can be special-cased? i586/i686 are "really" compatible while ix86/x86_64 are just "fake" compatible (the ix86/x86_64 case is why zypp doesn't switch archtectures, but the i586/i686 case puts it into question).

Btw. this is more likely a libzypp issue than a zmd issue.

Maybe also interesting: The case where noarch packages are involved in an architecture switch.
Comment 6 Andreas Hanke 2006-09-20 00:35:03 UTC
This bug is mis-assigned. It's a libzypp issue: All these dependency-related messages in zmd are from libzypp, the libzypp-zmd-backend helper writes them to stdout or maybe a pipe and zmd just grabs them from there.

Please re-assign this to a libzypp guy.
Comment 7 Andreas Hanke 2006-09-20 00:47:03 UTC
*** Bug 206707 has been marked as a duplicate of this bug. ***
Comment 8 Andreas Hanke 2006-09-20 00:52:46 UTC
Re-assigning it myself because neither the current Assignee nor the current QA Contact even receives mail about this report. *Sigh*

Logfiles are missing here, but they are present in the duplicate bug 206707: https://bugzilla.novell.com/attachment.cgi?id=99077
Comment 9 Klaus Kämpf 2006-09-20 07:29:50 UTC
The original comment states "YaST does install this without any problems from the same source."
As ZMD (libzypp-zmd-backend) and YaST share the same dependency solver (inside libzypp), the solver - when driven by YaST - does the right thing.

So this seems to be a zen-updater bug, requesting .i586 and .i686 packages in parallel.

But only logs can tell for sure. Sven, Andreas, please provide logs (and, if possible, /var/lib/zmd/zmd.db immediately after the error occurs.)

Comment 10 Forgotten User --EoyBps8f 2006-09-20 07:42:30 UTC
Created attachment 99156 [details]
zmd-backend.log
Comment 11 Forgotten User --EoyBps8f 2006-09-20 07:48:33 UTC
Created attachment 99157 [details]
zmd-messages
Comment 12 Forgotten User --EoyBps8f 2006-09-20 07:50:39 UTC
zmd.db is too big, even as bz2. You can get it at http://www-users.rwth-aachen.de/sven.burmeister/zmd.db.tar.bz2 and attach it to the bug, in case novell-employees can attach bigger files than users.
Comment 13 Jim Henderson 2006-09-20 13:38:03 UTC
It isn't just zen-updater - I can duplicate with rug as well.

See bug 206707, which was flagged as a duplicate of this bug.  I included the zen-backend.log file there that shows this with rug.
Comment 14 Jim Henderson 2006-09-25 06:54:52 UTC
The latest update to libzypp (or one of the related updates that came down with that a couple days ago) seems to have fixed this issue for me.  I just downloaded an ffmpeg and libffmpeg0 update combination that would've failed prior to the update and it worked fine.
Comment 15 Federico Lucifredi 2006-10-11 22:45:58 UTC
presuming fixed in 10.2, mauro will regress.