User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101230 Mandriva Linux/1.9.2.13-0.2mdv2010.2 (2010.2) Firefox/3.6.13 Build Identifier: Description of problem: in the grub/gfxboot screen after installation and during first boot, F1 F2 F3 have no text... Reproducible: Steps to Reproduce:
Priority: Normal => release_blockerCC: (none) => shikamaru
CC: (none) => dmorganecAssignee: ahmadsamir3891 => bugsquad
*** Bug 178 has been marked as a duplicate of this bug. ***
CC: (none) => dglent
fixed in mageia 1 alpha 2
Blocks: (none) => 56
@AL13N, not an upgrade-related bug (how many other reports did you set as blocking 56?).
Status: NEW => RESOLVEDBlocks: 56 => (none)Resolution: (none) => FIXED
all the ones that were working in mandriva 2010.1 and not anymore after upgrading to mageia 1 alpha 2. i think you are mistaken in removing all those dependencies, wasn't the tracker specifically made to make sure the upgrade path is valid? and completely successfull? i don't think this tracker is just used for direct upgrade errors during installation itself. all broken packages after installation are IMHO also blocking the upgrade.
(In reply to comment #4) > all the ones that were working in mandriva 2010.1 and not anymore after > upgrading to mageia 1 alpha 2. > > i think you are mistaken in removing all those dependencies, wasn't the tracker > specifically made to make sure the upgrade path is valid? and completely > successfull? > > i don't think this tracker is just used for direct upgrade errors during > installation itself. all broken packages after installation are IMHO also > blocking the upgrade. The scope of bug 56 is "bugs that happen during the upgrade process", e.g.: - if an mdv package doesn't get replaced by its mga counterpart (e.g. task-x11-2010.1 in mdv and task-x11-1- in mga) - if there're file conflicts due to files moving from one package to another - if the post/postun scriptlets don't get executed due to name change (e.g. mandriva-gfxboot-theme >> mageia-gfxboot-theme) Let's take this bug report for example, it's about a bug in mageia-gfxboot-theme, it's not an upgrade issue simply because you'd get the same exact bug with a clean install of Alpha1. Another issue is, what's the point of marking bug reports that have already been _fixed_ as blocking of a tracker bug? the whole point of having a tracker is to easily examine all the reports that block it to fix them, if they're already fixed, what's the point?