Description of problem: When trying to upgrade from Mageia 2 to Mageia 3 RC, mageia-prepare-upgrade does not properly configure lilo. It includes the "vga=xxx" line in the "append" line causing an error when lilo is run. Because of this error, the new option to upgrade doesn't appear in the bootloader menu. This could be either because lilo crashes due to the append error, or because mageia-prepare-upgrade does not run lilo after modifying the lilo.conf file. Version-Release number of selected component (if applicable): n/a How reproducible: Only get chance to try it once! Steps to Reproduce: 1. Take a Mageia 2 using lilo as the bootloader 2. Install mageia-prepare-upgrade 3. Reboot I managed to fix it by manually editing the lilo.conf file, then running lilo. All then worked as expected. Reproducible: Steps to Reproduce:
CC: sysadmin-bugs => (none)Component: Release (media or process) => RPM PackagesBlocks: (none) => 9744Assignee: bugsquad => mageia
Priority: Normal => release_blockerCC: (none) => davidwhodgins, ennael1, mageia, tmb
CC: (none) => pierre-malo.denielou
I'm not sure this should be a "release blocker" as it's a package that is to be shipped to Mageia 2 and release blockers are really only handled for the current release! I accept it needs fixed (even if only ~12 people use lilo ;)) The issue is that I specifically tried to preserve the vga= line as it was lost for grub users. http://svnweb.mageia.org/packages/updates/2/mageia-prepare-upgrade/current/SOURCES/mageia-prepare-upgrade-bootloader-config?r1=410003&r2=410002&pathrev=410003 Reverting this commit should be OK, but then there will be a graphical regression for grub users. I guess I need to find the "right" way to do this.
Priority: release_blocker => High
lilo is default apparently if installed on raid due to bug 9524 so it may affect more than expected.
CC: (none) => eeeemail
I just disagrees that we should even support that setup and I would strongly advise against anyone using it. Use a separate /boot if you want this kind of mode is my recommendation.
Should be fixed in the next build. I don't have any lilo systems so if you are able to test it, that would be awesome :)
I think I still have one non-upgraded machine with LiLo, but I'm on a long shift today, so won't get chance to try it until tomorrow (Tuesday). Will it be on the servers by then? Or alternatively, can you send me a link to the fixed version?
It should be on all the mirrors by then happily. It's the 2-0.10 version if you want to double check via urpmq -r first.
Yes, that seemed to work fine! Many thanks!
Cool, thanks for checking :)
Status: NEW => RESOLVEDResolution: (none) => FIXED