Description of problem: Update of devel packages fails when both (i586 and x86_64) devel packages are installed. In my case only x86_64 version was pulled to be updated and that caused collisions and the whole update failed. I had to stop the update, then go to the installation dialog and then mark both archs for update manually. The same repeated again for different devel packages. libxdmcp & lib64xdmcp libxau6-devel & lib64xau6-devel ... Even if the problem can be solved manually, it would be nice to have it fixed. Version-Release number of selected component (if applicable): 5.30-1.mga2 How reproducible: probably always?
Created attachment 1712 [details] screenshot
NOTE to the screenshot: The newer version (1.0.7-1) of the libxau6 devel package was available for both archs, byt the dependency reslution failed for some reason and took the i586 version as 1.0.6-4 (previous one = currently locally installed).
That's not a rpmdrake issue. Both packages provides the same files (include headers). On upgrade, if they do not end in the same transaction, CRC sums will differ between packages and the upgrade will fail. And they won't end in the same transaction since there's no tags (requires, conflicts, ...) to enforce that Anyway, installing devel files for 2 different architectures doesn't make much sense...
CC: (none) => thierry.vignaudSource RPM: rpmdrake-5.30-1.mga2.src.rpm => libxau
I don't remember exactly how that happened, but it seems to be somehow related to 'wine', because it's 32-bit only and thus needs 32-bit libxdmcp. I don't install devel packages unless they're needed by something and as the devel packages somehow appeared for both archs it seems to me as easily reachable and valid state.
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
Can anyone confirm if this is still a valid bug for Mageia 2 and/or Mageia 3 Roelof
CC: (none) => r.wobben
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as OLD.
Status: NEW => RESOLVEDCC: (none) => marja11Resolution: (none) => OLD