On installation, mgaonline replaces the Mandriva mirrorlist URL with mageia url. However, it fails to invalidate the mirror cache, and urpmi.addmedia stupidly (bug) uses the cache and thus re-adds the Mandriva medias instead of adding the Mageia medias. This breaks migration by following http://mageia.org/en/1/migrate/ . It should be fixed by rm'ing /var/cache/urpmi/mirrors.cache when an mdv system is migrated.
duplicate *** This bug has been marked as a duplicate of bug 1557 ***
Status: NEW => RESOLVEDResolution: (none) => DUPLICATE
Same symptoms but two different tools, reopening.
Status: RESOLVED => REOPENEDHardware: i586 => armResolution: DUPLICATE => (none)
Also, installing the Mageia updater ought to have an RPM-conflict with the Mandriva one. I ended up with both the Mageia and Mandriva online updaters running simultaneously in my KDE system tray! I suggest that the mgaonline-2.77.29-1.mga1 RPM should have an explicit conflict with mdkonline-2.77.15.17-1.2mdv2009.0.
CC: (none) => mageia
mgaonline already obsoletes mdkonline, however you need to kill the mdkapplet process manually, or just log out -> log in.
(In reply to comment #4) > mgaonline already obsoletes mdkonline, however you need to kill the mdkapplet > process manually, or just log out -> log in. Sorry - I don't think this is right. I'd been using my new Mga system for several hours (after rebooting into it) when I noticed this problem. I certainly had to manually "rpm -r mdkonline".
$ urpmq --obsoletes mgaonline mdkonline[< 2.77.30-2.mga2] I don't know what went wrong on your box though..
(In reply to comment #6) > $ urpmq --obsoletes mgaonline > mdkonline[< 2.77.30-2.mga2] > > I don't know what went wrong on your box though.. Indeed...well, that's obviously final; a bit puzzling how it happened though. /var/log/user.log doesn't tell me much, excepting that I installed mgaonline-2.77.29-1.mga1 as the very first step in my upgrade.
CC: (none) => thierry.vignaudAssignee: bugsquad => thierry.vignaud
We could kill mdkapplet in %post. I'll make it invalidate the cache like installer now does I'll look at the obsoletes/provides too
(In reply to comment #8) > We could kill mdkapplet in %post. > I'll make it invalidate the cache like installer now does > I'll look at the obsoletes/provides too @ Thierry, pinging because this bug still has the reopened status and nothing happened to it since august. Please set status to ASSIGNED or, if for work flow reasons you can't do that, put OK on the whiteboard instead. RESOLVED will do, too, when applicable ;)
CC: (none) => marja11
3 monthly ping
I've fixed the cache invalidation (needs backporting as an update to mga1 though). Anybody can add & test a "%triggerpostun - mdkonline" for upgrading mdv to mga
Keywords: (none) => Junior_job
Since the package is in testing, the QA need an announcement/advisory to validate that update.
Keywords: Junior_job => (none)Hardware: arm => All
Advisory: ========= This update fixes mgaonline so that when performing a live update, it invalidates urpmi cache of mirrors so that before adding new release media, else it could break the upgrade.
Thanks
Assignee: thierry.vignaud => qa-bugs
arf I don't have seen the other bug, sorry *** This bug has been marked as a duplicate of bug 5609 ***
Status: REOPENED => RESOLVEDResolution: (none) => DUPLICATE