Bug#400957: lintian: [checks/po-debconf] needs --use-untranslated when invoking msgcmp (getext 0.16)
Package: lintian Version: 1.23.26 Severity: normal Tags: patch Hi, Since gettext 0.16, msgcmp's behaviour regarding untranslated entries has changed. Quote from NEWS: * msgcmp now ignores fuzzy and untranslated messages in the PO file. Previously it considered fuzzy and untranslated messages the same way as translated messages, which was hardly useful. The previous behaviour can be obtained through the options --use-fuzzy --use-untranslated. This affects po-debconf's check, since it compares a newly extracted test.pot with the templates.pot from the package. Since both .pot files contain only untranslated entries, msgcmp complains: $ msgcmp debian/po/test.pot debian/po/templates.pot debian/po/test.pot:22: this message is untranslated debian/po/test.pot:30: this message is untranslated debian/po/test.pot:37: this message is untranslated debian/po/test.pot:45: this message is untranslated debian/po/test.pot:22: warning: this message is not used debian/po/test.pot:30: warning: this message is not used debian/po/test.pot:37: warning: this message is not used debian/po/test.pot:45: warning: this message is not used msgcmp: found 4 fatal errors To avoid this, please change system_env(/usr/bin/msgcmp debfiles/po/test.pot to system_env(/usr/bin/msgcmp --use-untranslated debfiles/.. Thanks, dam -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-2-686 Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.UTF-8 (charmap=UTF-8) Versions of packages lintian depends on: ii binutils 2.17-3The GNU assembler, linker and bina ii diffstat 1.43-2produces graph of changes introduc ii dpkg-dev 1.13.24 package building tools for Debian ii file 4.17-4Determines file type using magic ii gettext0.16.1-1 GNU Internationalization utilities ii intltool-debian0.35.0+20060710.1 Help i18n of RFC822 compliant conf ii libparse-debianchangel 1.0-1 parse Debian changelogs and output ii man-db 2.4.3-5 The on-line manual pager ii perl [libdigest-md5-pe 5.8.8-6.1 Larry Wall's Practical Extraction lintian recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#400957: lintian: [checks/po-debconf] needs --use-untranslated when invoking msgcmp (getext 0.16)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Russ Allbery написа: Damyan Ivanov [EMAIL PROTECTED] writes: system_env(/usr/bin/msgcmp --use-untranslated debfiles/.. I can't do that because no version of msgcmp prior to 0.16 supports that flag and 0.16 is only in experimental. Making that change would require a dependency on 0.16, which would make lintian uninstallable in unstable. gettext 0.16.1 was uploaded to unstable a couple of days ago :) http://packages.qa.debian.org/g/gettext/news/20061127T231703Z.html It seems that lintian indeed needs to depend on gettext = 0.16 after all. Thanks, dam - -- Damyan Ivanov Modular Software Systems [EMAIL PROTECTED] phone +359(2)928-2611, 929-3993 fax +359(2)920-0994 mobile +359(88)856-6067 [EMAIL PROTECTED]/Gaim -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFbgKjHqjlqpcl9jsRAksdAJ4xNgNfEV8NwiLr/I7kLExxRDXchACdEhhv PSmuKrMk4nI0iHhV86sH1m4= =CqS/ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#400957: lintian: [checks/po-debconf] needs --use-untranslated when invoking msgcmp (getext 0.16)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Russ Allbery написа: Damyan Ivanov [EMAIL PROTECTED] writes: Russ Allbery написа: I can't do that because no version of msgcmp prior to 0.16 supports that flag and 0.16 is only in experimental. Making that change would require a dependency on 0.16, which would make lintian uninstallable in unstable. gettext 0.16.1 was uploaded to unstable a couple of days ago :) http://packages.qa.debian.org/g/gettext/news/20061127T231703Z.html It seems that lintian indeed needs to depend on gettext = 0.16 after all. Ah, I see, my packages list was two days out of date, which is why I couldn't install it. This is still really unappealing and quite annoying, since it means that lintian won't work on sarge without a lot of hacking; that makes resurrecting lintian.debian.org before the etch release more difficult. Isn't there some other option? Detecting gettext version in runtime and adding --use-untranslated accordingly? I could provide a patch for this, but it will be a hack (and I am not very used to lintian internals so the patch quality will be unknown. If not, are you absolutely certain that this version of gettext will make it into etch? Who, me? :) Not at all. gettext is currently frozen. http://packages.qa.debian.org/g/gettext.html Perhaps gettext maintainer can say more (CC-ed). However, if gettext doesn't enter testing and you upload lintian version, depending on gettext = 0.16, it will not make it to Etch either (because of getext staying out). There will be a problem for Etch only if gettext enters testing, but lintian doesn't. The other possible problem case is what we have now in unstable. Maybe debian-release may give some ideas how best to solve this? dam, going to bed - -- Damyan Ivanov Modular Software Systems [EMAIL PROTECTED] phone +359(2)928-2611, 929-3993 fax +359(2)920-0994 mobile +359(88)856-6067 [EMAIL PROTECTED]/Gaim -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFbguiHqjlqpcl9jsRAugcAKCn3u8s3e3addJLvDcBF3czkb3ZeQCaArCj J6GUF+U/NEsa409YeaZamiU= =vHnx -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#400957: lintian: [checks/po-debconf] needs --use-untranslated when invoking msgcmp (getext 0.16)
Damyan Ivanov [EMAIL PROTECTED] writes: Russ Allbery написа: I can't do that because no version of msgcmp prior to 0.16 supports that flag and 0.16 is only in experimental. Making that change would require a dependency on 0.16, which would make lintian uninstallable in unstable. gettext 0.16.1 was uploaded to unstable a couple of days ago :) http://packages.qa.debian.org/g/gettext/news/20061127T231703Z.html It seems that lintian indeed needs to depend on gettext = 0.16 after all. Ah, I see, my packages list was two days out of date, which is why I couldn't install it. This is still really unappealing and quite annoying, since it means that lintian won't work on sarge without a lot of hacking; that makes resurrecting lintian.debian.org before the etch release more difficult. Isn't there some other option? If not, are you absolutely certain that this version of gettext will make it into etch? -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
Bug#400957: lintian: [checks/po-debconf] needs --use-untranslated when invoking msgcmp (getext 0.16)
On Thu, 30 Nov 2006, Damyan Ivanov wrote: Who, me? :) Not at all. gettext is currently frozen. http://packages.qa.debian.org/g/gettext.html Perhaps gettext maintainer can say more (CC-ed). Yes, gettext is frozen, but I hope the release managers let it propagate to etch in the near future, for several reasons: *) It fixes an important bug (#400187). *) It would allow automake 1.10 to be in etch too (automake 1.10 do not work with gettext 0.15). *) According to the author, the change from 0.15 to 0.16 should be smooth (expect, maybe, the new msgcmp behaviour). (/me going to bed too :-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#400957: lintian: [checks/po-debconf] needs --use-untranslated when invoking msgcmp (getext 0.16)
Santiago Vila [EMAIL PROTECTED] writes: On Thu, 30 Nov 2006, Damyan Ivanov wrote: Who, me? :) Not at all. gettext is currently frozen. http://packages.qa.debian.org/g/gettext.html Perhaps gettext maintainer can say more (CC-ed). Yes, gettext is frozen, but I hope the release managers let it propagate to etch in the near future, for several reasons: *) It fixes an important bug (#400187). *) It would allow automake 1.10 to be in etch too (automake 1.10 do not work with gettext 0.15). That would be nice. *) According to the author, the change from 0.15 to 0.16 should be smooth (expect, maybe, the new msgcmp behaviour). That the msgcmp change is annoying for lintian is, I think, an artifact of the fact that lintian is doing something weird and not really the fault of gettext. Okay, I'll ponder how best to fix lintian. Thanks for the information! -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
