]# urpmi argyllcms installing argyllcms-1.4.0-1.mga2.x86_64.rpm from /home/mageia/cauldron/x86_64/media/core/release Preparing... ##################################################################################################################################################### Installation failed: file /usr/bin/iccdump from install of argyllcms-1.4.0-1.mga2.x86_64 conflicts with file from package icclib-2.13-1.mga2.x86_64 file /usr/bin/icclu from install of argyllcms-1.4.0-1.mga2.x86_64 conflicts with file from package icclib-2.13-1.mga2.x86_64 file /usr/bin/icctest from install of argyllcms-1.4.0-1.mga2.x86_64 conflicts with file from package icclib-2.13-1.mga2.x86_64 ~]# urpmq -l icclib-2.13-1.mga2 /usr/bin/iccdump /usr/bin/icclu /usr/bin/icctest ]# urpmq -l argyllcms-1.4.0 |grep bin/icc /usr/bin/iccdump /usr/bin/iccgamut /usr/bin/icclu /usr/bin/icctest
Assigning to maintainer.
CC: (none) => sander.lepikAssignee: bugsquad => dmorganec
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
The same RPM's are still in MGA2 and Cauldron.
Keywords: NEEDINFO => (none)
Whiteboard: (none) => MGA2TOO
Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D
Depends on: (none) => 7464
I don't see the need for blocker when the packages in updates does'nt need the fix..
Depends on: 7464 => (none)
I can't reproduce in 5Beta3. Close, likely to have been fixed.
Status: NEW => RESOLVEDCC: (none) => nicResolution: (none) => FIXED