reopen #976704 Hello Tobias, On Wed, Dec 09, 2020 at 01:30:05PM +0000, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the po4a package: > > #976704: po4a: Missing dependency on libpod-parser-perl > > It has been closed by "Dr. Tobias Quathamer" <to...@debian.org>. > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact "Dr. Tobias Quathamer" > <to...@debian.org> by > replying to this email. > > > -- > 976704: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976704 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems
> Date: Wed, 9 Dec 2020 14:27:00 +0100 > From: "Dr. Tobias Quathamer" <to...@debian.org> > To: Helge Kreutzmann <deb...@helgefjell.de>, 976704-d...@bugs.debian.org, > Martin Quinson <martin.quin...@ens-rennes.fr> > Subject: Re: Bug#976704: po4a: Missing dependency on libpod-parser-perl > > Version: 0.61-1 > > Am 09.12.20 um 08:32 schrieb Helge Kreutzmann: > > 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 deb...@helgefjell.de 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 > > Hi Helge, > > you're right, libpod-parser-perl is required. But it seems to me that > maybe something on your build system had been set up wrongly, because > libpod-parser-perl is listed as "Depends" for the binary package po4a. > Moreover, the package libpod-parser-perl is also listed as > "Build-Depends-Indep" for the source package of po4a. So I would think > that everything has been catered for. > > I don't know why apt would let you remove libpod-parser-perl. If I try > this on my system, I get the correct notification that po4a would be > removed as well: > > $ sudo LC_ALL=C apt remove libpod-parser-perl > Reading package lists... Done > Building dependency tree > Reading state information... Done > The following packages will be REMOVED: > [...] libpod-parser-perl po4a > 0 upgraded, 0 newly installed, 6 to remove and 0 not upgraded. > > I'm therefore closing this bug. I reported this to the apt folks, and got the following answer: <quote> perl Provides libpod-parser-perl. Hence it's not even installed by default if you install po4a (because perl was installed already). </quote> This is most likely what happend to me. So po4a needs to ensure that the package "libpod-parser-perl" is really installed, not the perl version. Or it needs to work with the perl version. For (little) more details see #976980. Greetings Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/
signature.asc
Description: PGP signature