[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#858934: apt FTBFS with po4a 0.50-1



Control: reassign -1 po4a 0.50-1

Hi,

On Tue, Mar 28, 2017 at 10:05:52PM +0200, Helmut Grohne wrote:
> Since today apt fails to build from source in unstable on amd64. The
> typical failure looks like:
> 
> | cd "/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/doc" && po4a --previous --no-backups --package-name='apt-doc' --package-version='1.4~rc2' --msgid-bugs-address='APT\ Development\ Team\ <deity
> | Invalid po file po/es.po:
> | msgfmt: error while opening "po/es.po" for reading: No such file or directory

The full command is:

cd /path/to/apt/build/doc && po4a --previous --no-backups --package-name='apt-doc' --package-version='1.4~rc2' --msgid-bugs-address='APT\ Development\ Team\ <deity@lists.debian.org>' --translate-only de/guide.de.dbk --srcdir /path/to/apt/doc --destdir /path/to/apt/build/doc /path/to/apt/doc/po4a.conf

As you can see we switch into a build directory and instruct po4a to
pick up all files it needs with --srcdir from the source. That used to
work, but it seems to no longer work in the new version – I can fix the
build with a simple symlink:

ln -s /path/to/apt/doc/po /path/to/apt/build/doc/po

As I don't see what the apt buildsystem could be doing wrong in po4a
call and because it worked before I am reassign to po4a to fix that
regression – especially as we are in freeze.

If there is something wrong with the call on the other hand it would be
nice if we could get some details on what to do instead and how to
achieve compatibility with "old" and "new" po4a.


Thanks Martin for picking up po4a development btw even if the timing is
a bit unfortunate for (accidental?) uploads to unstable…


Best regards

David Kalnischkies

Attachment: signature.asc
Description: PGP signature


Reply to: