Hello Martin,
On Tue, Dec 08, 2020 at 11:18:12PM +0100, Martin Quinson wrote:
> it seems to me that this is an upstream bug that you will never encounter 
> when using the Debian package (neither source nor binary). Do you agree?

I'm using the Debian package, not the something from other sources. My
intend is to rebuild other packages or upstream packages, but not
installing them, as I'm only interested in up-to-date de.po files.

The first time I hit this problem was when I tried to rebuild the
upstream sources of dpkg.

> ----- Le 7 Déc 20, à 9:24, Helge Kreutzmann [email protected] a écrit :

…

> > After installing libpod-parser-perl, the build suceedes.

…

And once libpod-parser-perl from Debian is installed the build suceeds. So 
to me it appears as if libpod-parser-perl is required to operate po4a at 
least with packages like dpkg and po4a.

Thus I think this is a Debian bug, not an upstream one (or a bug in
both, if libpod-parser-perl is not meant to be used, which I cannot
judge).

Greetings

          Helge

-- 
      Dr. Helge Kreutzmann                     [email protected]
           Dipl.-Phys.                   http://www.helgefjell.de/debian.php
        64bit GNU powered                     gpg signed mail preferred
           Help keep free software "libre": http://www.ffii.de/

Attachment: signature.asc
Description: PGP signature

Reply via email to