Description of problem: After migration I had a weird problem with Evolution due to some mismatched files. This caused me to LOSE several e-mail messages, so it is rather bad. After migration the system had: libgdk-pixbuf2-0.22.0-16mdv2010.1 - left over from Mandriva gdk-pixbuf2.0-2.22.1-3.mga1 - added with the migration to Mageia This mismatch was causing a crash in Evolution as it appears Evolution relies on the library. The correct library for Mageia should be: libgdk_pixbuf2.0_0-2.22.1-3.mga1 I received this instruction on IRC: <dmorgan> eracc: migration pb , and ask in the bugreport to add an obsolete to make the update goes smoothly Hopefully you guys know what that means. :)
CC: (none) => stormiSource RPM: (none) => libgdk_pixbuf2.0_0
Summary: Migration Problem for Mandriva 2010.2 to Mageia 1 => libgdk_pixbuf2.0_0 must obsolete libgdk-pixbuf2 (Migration Problem for Mandriva 2010.2 to Mageia 1)Source RPM: libgdk_pixbuf2.0_0 => gdk_pixbuf2.0_0
Erwan, could you have a look to this migration problem regarding gdk-pixbuf ? I wanted to fix it but I fear I would mess it up, as I don't know this package at all.
Assignee: bugsquad => erwanaliasr1Summary: libgdk_pixbuf2.0_0 must obsolete libgdk-pixbuf2 (Migration Problem for Mandriva 2010.2 to Mageia 1) => gdk-pixbuf must obsolete libgdk-pixbuf2 (Migration Problem for Mandriva 2010.2 to Mageia 1)
There is gdk-pixbuf2.0-2.22.1-3.1 in updates, is this bug resolved ?
Source RPM: gdk_pixbuf2.0_0 => gdk-pixbuf2
Pinging, because nothing has happened with this report for more than 3 months, it still has the status NEW or REOPENED. @ Erwan Please set status to ASSIGNED if you think this bug was assigned correctly. If for work flow reasons you can't do that, then please put OK on the whiteboard instead.
CC: (none) => marja11
CC: (none) => remco
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
(In reply to comment #4) ... > @ 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. Nothing new from me. As all of my clients are currently migrated to Mageia, and most are on Mageia 2 at this time, this is a non-issue for me now. > @ 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. I never saw a request for information on this bug. > Thanks all :-D You're welcome.
This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => WONTFIX