Hello László, Am Sun, Sep 01, 2024 at 08:10:22PM +0200 schrieb László Böszörményi (GCS): > On Sun, Sep 1, 2024 at 6:33 PM Helge Kreutzmann <deb...@helgefjell.de> wrote: > > If anything is unclear, I'm happy to resolve this. > I started the update back then. Soon I got stuck, the current state > is online [1]. The pod can't be processed and in the next few days I > don't have time to look at it.
Yes, this build failure is expected:
"/usr/bin/perl" -MExtUtils::MY -e 'MY->fixin(shift)' --
blib/script/apt-src
make[1]: *** No rule to make target 'man/apt-src.es.pod', needed by
'manifypods'. Stop.
make[1]: Leaving directory '/tmp/astest/apt-src-0.25.4'
(This is after I faked more strings in de.po).
The build system "as is" does not deal with incomplete translations,
see the Makefile line 421:
manifypods : pure_all config \
man/apt-src.de.pod \
man/apt-src.es.pod \
man/apt-src.fr.pod \
man/apt-src.nl.pod \
man/apt-src.pod \
man/apt-src.pt.pod
$(NOECHO) $(POD2MAN) --section=$(MAN1EXT) --perm_rw=$(PERM_RW) -u \
man/apt-src.de.pod man/apt-src.de.1 \
man/apt-src.es.pod man/apt-src.es.1 \
man/apt-src.fr.pod man/apt-src.fr.1 \
man/apt-src.nl.pod man/apt-src.nl.1 \
man/apt-src.pod man/apt-src.1 \
man/apt-src.pt.pod man/apt-src.pt.1
Once I get your go, I will request all translations to be updated
again, and given that apt-src.1 is rather static, this problem should
not occur in practice. It only happens now, as I updated apt-src.1 but
not the translations.
So my proposal is to ignore this problem. For testing, you can fake
entries in the de.po, es.po, fr.po and nl.po. As said earlier, once
you approve the patch, the translations will return to 100%. If some
new translations should arrive, it will be 100% and you will need to
update this piece of the Makefile.
Of course, this can be done dynamic. But given the static nature of
this package, I don't think it is worth the effort, but if you are
interested, its documented in po4a(1).
So my proposal is to first get this package back in shape and testing.
Making the Makefile dynamic would be the next step, which you can work
on after I "left" taking care and with properly i18n in testing.
Would that be fine for your?
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
