Description of problem: plymouth menu screen shows Mageia 5 instead of 6 Clean network install+updates Problem shows up in VirtualBox and plain hardware installs. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. clean install and boot run level 5
Created attachment 7562 [details] grub/plymouths menu from same system
Summary: mga6: plymouth menu screen shows Mageia 5 instead of 6 => mga6: grub menu screen shows Mageia 5 instead of 6Source RPM: plymouth-0.9.2-4.mga6.src.rpm => mageia-gfxboot-theme
Right side of attachment shows boot menu on right has Mageia 5 instead of Mageia 6. Grub menu on left side of attachment shows no such items.
Summary: mga6: grub menu screen shows Mageia 5 instead of 6 => mga6: Boot menu screen shows Mageia 5 instead of 6
Well the "boot menu" is grub in graphical mode, so my title was correct. Plymouth is the part after starting up the kernel, where it displays a graphical animation instead of the textual list of starting services.
Assigning to all packagers collectively, since there is no maintainer for this package.
Keywords: (none) => 6dev1CC: (none) => marja11Assignee: bugsquad => pkg-bugs
I had a look at the source and the file mageia-gfxboot-theme-4.5.6.9/po/bootloader.pot needs editing to replace Mageia 5 with Mageia 6 also mageia-gfxboot-theme-4.5.6.9/NEWS needs editing as well. I changed the source and edited the spec file and built mageia-gfxboot-theme-4.5.6.9-2.rpm. Updated and the boot screen is correct. What can I do now?
CC: (none) => nic
(In reply to Nic Baxter from comment #5) > I had a look at the source and the file > mageia-gfxboot-theme-4.5.6.9/po/bootloader.pot needs editing to replace > Mageia 5 with Mageia 6 also mageia-gfxboot-theme-4.5.6.9/NEWS needs editing > as well. I changed the source and edited the spec file and built > mageia-gfxboot-theme-4.5.6.9-2.rpm. Updated and the boot screen is correct. > What can I do now? My recommendation is to get a consensuses if it is desirable to always have to dink with the rpm on every release. My suggestion is to take the release level out of the screen or the code/script that builds mageia-release src.rpm need to automagically redo the mageia-gfxboot-theme rpm.
(In reply to Nic Baxter from comment #5) > I had a look at the source and the file > mageia-gfxboot-theme-4.5.6.9/po/bootloader.pot needs editing to replace > Mageia 5 with Mageia 6 also mageia-gfxboot-theme-4.5.6.9/NEWS needs editing > as well. I changed the source and edited the spec file and built > mageia-gfxboot-theme-4.5.6.9-2.rpm. Updated and the boot screen is correct. > What can I do now? Thanks Nic. The source comes from http://gitweb.mageia.org/software/design/bootloader-theme and ennael already made almost all the needed changes long ago: http://gitweb.mageia.org/software/design/bootloader-theme/commit/?id=488f8251278b653e417c33f3e26d65092bd31238 However, in that commit the pot file was not updated.... Maybe that caused the problems like in the last two commits: http://gitweb.mageia.org/software/design/bootloader-theme/commit/?id=e9dfe0a09f16e72cea9603532dd503a0a95ab3cf http://gitweb.mageia.org/software/design/bootloader-theme/commit/?id=5886ea43ac62b1ddf803c7f4e7f6bf58ce1acc09 Where "Mageia 6 Cauldron" was reverted to "Mageia 5" :-( Re-assigning to ennael, but also CC'ing i18n team and yurchor (In reply to Bit Twister from comment #6) > > My recommendation is to get a consensuses if it is desirable to always have > to dink with the rpm on every release. > > My suggestion is to take the release level out of the screen > or the code/script that builds mageia-release src.rpm need to automagically > redo the mageia-gfxboot-theme rpm.
CC: (none) => i18n-bugs, yurchorAssignee: pkg-bugs => ennael1
Sorry for that trouble, but we, translators, only translate what developers produce (that was clearly stated many times ago). As you can see: http://gitweb.mageia.org/software/design/bootloader-theme/tree/po/bootloader.pot has #. txt_linux msgid "Boot Mageia 5" msgstr "" So we translate this way. Nothing we can do until developers fix POT. :'(
(In reply to Yuri Chornoivan from comment #8) > Sorry for that trouble, but we, translators, only translate what developers > produce (that was clearly stated many times ago). > > As you can see: > > http://gitweb.mageia.org/software/design/bootloader-theme/tree/po/bootloader. > pot > > has > > #. txt_linux > msgid "Boot Mageia 5" > msgstr "" > > So we translate this way. Nothing we can do until developers fix POT. :'( I just changed "Mageia 5" into "Mageia 6 Cauldron" everywhere in the pot file and po files. http://gitweb.mageia.org/software/design/bootloader-theme/commit/ However, I did not bump version in the Makefile, nor add anything to the news, nor create a new tarball for mageia-gfxboot-theme I prefer waiting to see whether something was wrong with my changes
> I just changed "Mageia 5" into "Mageia 6 Cauldron" everywhere in the pot > file and po files. > http://gitweb.mageia.org/software/design/bootloader-theme/commit/ > > However, I did not bump version in the Makefile, nor add anything to the > news, nor create a new tarball for mageia-gfxboot-theme > > I prefer waiting to see whether something was wrong with my changes Thanks! Pushed manually to Transifex to avoid troubles with tx <-> git synchronization.
(In reply to Yuri Chornoivan from comment #10) > > Thanks! > > Pushed manually to Transifex to avoid troubles with tx <-> git > synchronization. Great, thx Yuri :-) Btw, I added "POT-Creation-Date: 2016-03-16 20:00+0100\n" to the pot file, because I thought pot files need such a line. However, it was in fact not created, but just updated at that time. Is such a line needed, and, if so, would "POT-Revision-Date: etc." have been ok, too, or even better?
(In reply to Marja van Waes from comment #11) > (In reply to Yuri Chornoivan from comment #10) > > > > > Thanks! > > > > Pushed manually to Transifex to avoid troubles with tx <-> git > > synchronization. > > Great, thx Yuri :-) > > Btw, I added "POT-Creation-Date: 2016-03-16 20:00+0100\n" to the pot file, > because I thought pot files need such a line. However, it was in fact not > created, but just updated at that time. > Is such a line needed, and, if so, would "POT-Revision-Date: etc." have been > ok, too, or even better? Tx uses it to distinguish what is newer, template or translations. For other aspects, it is not important.
(In reply to Yuri Chornoivan from comment #12) > (In reply to Marja van Waes from comment #11) > > > > Btw, I added "POT-Creation-Date: 2016-03-16 20:00+0100\n" to the pot file, > > Tx uses it to distinguish what is newer, template or translations. For other > aspects, it is not important. Good to know :-) Date is wrong, btw, I hadn't seen that my clock had switched to showing 29-03-16 instead of 2016-03-29 and had only looked at the last two numbers :-/
(In reply to Bit Twister from comment #6) > > My recommendation is to get a consensuses if it is desirable to always have > to dink with the rpm on every release. > > My suggestion is to take the release level out of the screen > or the code/script that builds mageia-release src.rpm need to automagically > redo the mageia-gfxboot-theme rpm. If I hadn't forgotten to answer you, then maybe I wouldn't have been too fast to commit my changes. Taking the release level out, makes it impossible for translators to adjust it to comply with the grammatical rules in their language in the strings where it is used. One could e.g. imagine a language (it might even really exist) in which "Mageia 5" can only be translated to an equivalent of "Mageia 5th". As in English, the suffix might need to be changed for other numbers, English would be OK up till "21st" "22nd" and "23rd", for other languages that might be worse. Also "Cauldron", if left untranslated, might mean or resemble something not so nice in another language. If it is or resembles their word for "Headache", the translator needs to be able to translate it to something that conveys the real meaning of "Cauldron" ;-) Anyway, I had only seen for two languages that "Mageia 6 Cauldron" had already been translated to "Mageia 6 Cauldron" before the strings in those po files were reverted to "Mageia 5"... I'll check all translations that I changed, and will add fuzzy's if/where needed. @ ennael Sorry for having pushed the po files too fast. I intend to check the po files before tomorrow.
(In reply to Marja van Waes from comment #14) > > @ ennael > > Sorry for having pushed the po files too fast. I intend to check the po > files before tomorrow. Done and committed to git. Funny, the Czech translation of Mageia 5 was "Mageiu 5", but the original translation of "Mageia 6 Cauldron" was "Mageia 6 Cauldron", so without s/ia/iu/ @ Yuri The date in the pot file was corrected, one string in lt.po fuzzied and cs.po updated
*** Bug 17998 has been marked as a duplicate of this bug. ***
CC: (none) => andrewsfarm
*** Bug 17615 has been marked as a duplicate of this bug. ***
CC: (none) => nicolas.salguero
I just swapped from grub text to grub graphical, rebooted and problem is gone.
Status: NEW => RESOLVEDResolution: (none) => FIXED
Hi, I reopen that bug because, on my up-to-date Cauldron x86_64 VM, the problem still persists: grub graphical displays "Boot Mageia 5" whereas it should display "Amorcer Mageia 6 Cauldron". Best regards, Nico.
Status: RESOLVED => REOPENEDResolution: FIXED => (none)
Hi, With the version 4.5.6.10 of the package, the problem is solved. Best regards, Nico.
Status: REOPENED => RESOLVEDResolution: (none) => FIXED