Bug#400957: lintian: [checks/po-debconf] needs --use-untranslated when invoking msgcmp (getext 0.16)
Damyan Ivanov <dam@modsoftsys.com> writes:
> Package: lintian
> Version: 1.23.26
> Severity: normal
> Tags: patch
> 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/......
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.
Are there any other options?
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: