The help messages of the boot menue when booting from the install CD refers to "Yast2", see attached screen-shot. I verified the text for German and English. Both show "Yast2"
Created attachment 575 [details] Screenshot showing "Yast2"
Hardware: i586 => AllVersion: 1 => Cauldron
Component: Release (media, process) => RPM PackagesSource RPM: (none) => mageia-gfxboot-theme
Assigning to maintainer now that our maintainers database has an entry for this package. Please assign back to bugsquad@mageia.org in case of a mistake from me.
CC: (none) => stormiAssignee: bugsquad => balcaen.john
CC: (none) => balcaen.johnAssignee: balcaen.john => watersnowrock
Is this still the case with the latest install from a boot.iso from cauldren? Also, does it still occur from Mageia 1 final?
My screenshot is from Mageia 1. Why not just grep -ir yast on the sources?
pinging. because nothing happened to this report since more than 3 months ago, and it still has the status NEW or REOPENED @ Donald 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
Hartmut: Can you check with current caulron as I am away from my laptop now. If it is still present, then I will look into it again when I get back, otherwise I will mark it as resolved.
Status: NEW => ASSIGNED
Donald: Are you kidding? Are you really expecting me to download a ISO-image, set up a virtual machine and test, where a simple grep -ir yast on the sources would do? The grep is *much* easier and much more reliable then testing.
Hartmut: I am asking for confimation that it still exists. As I said, I am away from home and don't have access to a linux machine so I cant just grep the sources. Which I did when you first reported the bug, and nothing showed, hence why I am asking for a confirmation that it still exists.
There is no note in here that you did anything. So sorry for being to harsh. I tried testing <http://www.mageia.org/en/downloads/get/?q=Mageia-2-alpha2-LiveCD-KDE4-Europe1-Americas-i586-CD.iso>, but only got "Sorry no help texts."
Yeah well, posting to tell you that a grep turns up no results doesn't really seem pointful to me, especially when you don't confirm that the bug is still present. Thanks for the test, I'm not sure what to make of the no help texts being available, I will check in more on this next week.
in fact it's more a job for the iso builder since it's hardcoded, sorry :/
CC: (none) => ennael1, mageia, tmbSeverity: normal => minor
I was beginning to think that most of the bugs against gfxboot-theme were more iso issues, as I wasn't finding anything that could cause them.
http://svnweb.mageia.org/soft/theme/mageia-gfxboot-theme/trunk/help-install/*/main%3A%3Aopt%3A%3Anetwork.html?view=log line 11 in the english one
Keywords: (none) => Junior_job
Blocks: (none) => 5275
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
This is still valid: $ svn co svn://svn.mageia.org/soft/theme/mageia-gfxboot-theme/trunk/ mageia-gfxboot-theme [...] Checked out revision 4706. $ grep -ril yast mageia-gfxboot-theme| wc -l 75 $
Keywords: NEEDINFO => (none)CC: (none) => sander.lepik
This is still valid for revision 8608 (checked the same way as in comment #15).
For the reference, two files (for English) have to be edited: main::opt::network.html and main::opt::o_vnc.html http://gitweb.mageia.org/software/design/bootloader-theme/tree/help-install/en/main::opt::network.html http://gitweb.mageia.org/software/design/bootloader-theme/tree/help-install/en/main::opt::o_vnc.html You can go to the help-install dir and run: $ sed -i 's/YaST2/DrakX/g' */* $ sed -i 's/YaST/DrakX/g' */* (in this order, in the NL translation the "2" was dropped it seems). -- Actually I pushed the changes, it's now fixed in git. The package still needs to be rebuilt with the proper sources.
CC: (none) => remi
Freeze push asked for, so this should be closed. I wonder if this is the last incorrect reference in Mageia from the initial import?
Status: ASSIGNED => RESOLVEDResolution: (none) => FIXED
But it's not yet pushed, will close when it's done. (could be great to not close before it's done, something similar happens with mga3, and it was never really fixed until release, event some months after with a release) [copy text]
Status: RESOLVED => REOPENEDResolution: FIXED => (none)
Package pushed
Status: REOPENED => RESOLVEDResolution: (none) => FIXED