[Bug 489139] New: build-compare: ignore POT-Creation-Date from mo files
https://bugzilla.novell.com/show_bug.cgi?id=489139 Summary: build-compare: ignore POT-Creation-Date from mo files Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: vuntz@novell.com QAContact: qa@suse.de Found By: --- atk in GNOME:Factory is always different because of POT-Creation-Date that gets updated in some mo file. If this is the only difference, it can be safely ignored. .. comparing built packages with the former built /usr/lib/build/rpm-check.sh compare /.build.oldpackages/atk-1.26.0-13.3.src.rpm /usr/src/packages/SRPMS/atk-1.26.0-13.4.src.rpm compare /.build.oldpackages/atk-1.26.0-13.3.i586.rpm /usr/src/packages/RPMS/i586/atk-1.26.0-13.4.i586.rpm compare /.build.oldpackages/atk-debuginfo-1.26.0-13.3.i586.rpm /usr/src/packages/RPMS/i586/atk-debuginfo-1.26.0-13.4.i586.rpm compare /.build.oldpackages/atk-debugsource-1.26.0-13.3.i586.rpm /usr/src/packages/RPMS/i586/atk-debugsource-1.26.0-13.4.i586.rpm compare /.build.oldpackages/atk-devel-1.26.0-13.3.i586.rpm /usr/src/packages/RPMS/i586/atk-devel-1.26.0-13.4.i586.rpm compare /.build.oldpackages/atk-doc-1.26.0-13.3.i586.rpm /usr/src/packages/RPMS/i586/atk-doc-1.26.0-13.4.i586.rpm compare /.build.oldpackages/atk-lang-1.26.0-13.3.i586.rpm /usr/src/packages/RPMS/i586/atk-lang-1.26.0-13.4.i586.rpm /usr/share/locale/or/LC_MESSAGES/atk10.mo differs ( GNU message catalog (little endian), revision 0, 127 messages) --- /tmp/tmp.mYt3edvhn5 2009-03-26 12:10:53.000000000 +0000 +++ /tmp/tmp.AEOBk0hJO4 2009-03-26 12:10:53.000000000 +0000 @@ -326,7 +326,7 @@ 00001450 6f 72 74 2d 4d 73 67 69 64 2d 42 75 67 73 2d 54 |ort-Msgid-Bugs-T| 00001460 6f 3a 20 0a 50 4f 54 2d 43 72 65 61 74 69 6f 6e |o: .POT-Creation| 00001470 2d 44 61 74 65 3a 20 32 30 30 39 2d 30 33 2d 32 |-Date: 2009-03-2| -00001480 31 20 31 30 3a 31 32 2b 30 30 30 30 0a 50 4f 2d |1 10:12+0000.PO-| +00001480 36 20 31 32 3a 30 39 2b 30 30 30 30 0a 50 4f 2d |6 12:09+0000.PO-| 00001490 52 65 76 69 73 69 6f 6e 2d 44 61 74 65 3a 20 32 |Revision-Date: 2| 000014a0 30 30 39 2d 30 31 2d 32 38 20 31 35 3a 31 39 2b |009-01-28 15:19+| 000014b0 30 35 33 30 0a 4c 61 73 74 2d 54 72 61 6e 73 6c |0530.Last-Transl| .. build is finished -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=489139 User vuntz@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=489139#c1 Vincent Untz <vuntz@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sbrabec@novell.com --- Comment #1 from Vincent Untz <vuntz@novell.com> 2009-03-26 06:28:10 MST --- I see this in gnome-panel too, and I would expect many other packages to have this. Wondering if it could be happening because of the usage of translation-update-upstream. Stanislav? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=489139 User sbrabec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=489139#c2 --- Comment #2 from Stanislav Brabec <sbrabec@novell.com> 2009-03-26 06:46:58 MST --- It's caused by translation-update-upstream. Maybe also gnome-patch-translation has the same behavior. It's not easy to get it rid with a standard gettext: We need to generate pot file. But I guess it is possible to get the old pot-creation-date and merge it to the new po file. As a quick solution, I'll reset translation-update-upstream data (they are outdated anyway). As a long time solution, using stable po file timestamps is required. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=489139 Stanislav Brabec <sbrabec@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low Status|NEW |ASSIGNED AssignedTo|bnc-team-screening@forge.pr |sbrabec@novell.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=489139 Vincent Untz <vuntz@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|build-compare: ignore |translation-update-upstream |POT-Creation-Date from mo |changes POT-Creation-Date |files |in mo files (and breaks | |build-compare) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=489139 User bruno@clisp.org added comment https://bugzilla.novell.com/show_bug.cgi?id=489139#c3 Bruno Haible <bruno@clisp.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bruno@clisp.org --- Comment #3 from Bruno Haible <bruno@clisp.org> 2009-03-26 17:45:32 MST ---
It's not easy to get it rid with a standard gettext
Why? It's a built-in feature of "msgmerge --update" that it will not touch po files if the only change between the present and the new .po file would be a difference in POT-Creation-Date. If you don't use "msgmerge --update" for merging the .po files, that would explain it... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=489139 User sbrabec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=489139#c4 --- Comment #4 from Stanislav Brabec <sbrabec@novell.com> 2009-03-27 05:15:59 MST --- I am using: msgcat --use-first $PO_PATH $PO -o $PO.new msgmerge --no-fuzzy-matching --compendium=$PO_PATH -o $PO $PO.new $POT Because pot files are not distributed in the source by default, I have to generate it. There are more changes than only .pot creation date. It merges possible newer strings from upstream. If translation-update-upstream did not change since last rebuild, string changes are exactly te same. Note: Use of msgmerge --update without generating of pot file makes non-trivial assumption, that upstream called make po-update before release. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=489139 User bruno@clisp.org added comment https://bugzilla.novell.com/show_bug.cgi?id=489139#c5 --- Comment #5 from Bruno Haible <bruno@clisp.org> 2009-03-27 05:52:16 MST ---
I am using:
msgcat --use-first $PO_PATH $PO -o $PO.new msgmerge --no-fuzzy-matching --compendium=$PO_PATH -o $PO $PO.new $POT
The use of msgcat is fishy: It means that the compendium overrides the contents of the PO file. What happens if you use: msgmerge --no-fuzzy-matching --compendium=$PO_PATH --update $PO $POT -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=489139 User vuntz@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=489139#c6 --- Comment #6 from Vincent Untz <vuntz@novell.com> 2009-03-27 06:11:32 MST --- (In reply to comment #5)
The use of msgcat is fishy: It means that the compendium overrides the contents of the PO file.
But I think that it's what is wanted. The idea is that we have in the compendium the translation from svn, which is supposedly better than the one in the tarball. (this is true for stable branches in GNOME, for example) So the issue is that we call intltool-update --pot unconditionally, which will cause the POT-Creation-Date change. I guess we can compare the old and new po file and see if that's the only change, and ignore it if that's the case? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=489139 User sbrabec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=489139#c7 --- Comment #7 from Stanislav Brabec <sbrabec@novell.com> 2009-03-27 06:22:58 MST --- Yes, overwriting of existing upstream strings by strings changed in later upstream versions is an intended behavior. As far as I remember my experiments, msgmerge have had an ugly problem: If there already exists a translation, it is never updated from compendium, even if the old one is an invalid fuzzy string. That is why I used msgcat. I would need something like --force-compendium. To save update size, only changes and updates are part of the updated po file. But the real problem causing behavior reported in this bug: Tool does not trust that upstream re-generated po file against the latest pot file. That is why it generates its own pot file (each time, as it is not a part of the package). This behavior is easy to work-around. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com