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

Bug#906412: svn-buildpackage: FTBFS in buster/sid (po4a-build: Command not found)



On Fri, 17 Aug 2018 11:21:39 +0000 Santiago Vila <sanvila@debian.org> wrote:
> I tried to build this package in buster but it failed:
> 
> --------------------------------------------------------------------------------
> [...]
>  debian/rules build-indep
> dh build-indep
> dh: Compatibility levels before 9 are deprecated (level 7 in use)
>    dh_update_autotools_config -i
>    dh_auto_configure -i
> dh_auto_configure: Compatibility levels before 9 are deprecated (level 7 in use)
>    dh_auto_build -i
> dh_auto_build: Compatibility levels before 9 are deprecated (level 7 in use)
> 	make -j1
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> po4a-build 
> make[1]: po4a-build: Command not found
> make[1]: *** [Makefile:10: docbuild] Error 127
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
> dh_auto_build: make -j1 returned exit code 2
> make: *** [debian/rules:4: build-indep] Error 2
> dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2
> --------------------------------------------------------------------------------
> 
> The build was made with "dpkg-buildpackage -A" in my autobuilder.
> Most probably, it also fails here in reproducible builds:
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/svn-buildpackage.html
> 
> where you can get a full build log if you need it.
> 
> If this is really a bug in one of the build-depends, please use reassign and affects,
> so that this is still visible in the BTS web page for this package.

Upstream version 0.54 of po4a removed po4a-build:

https://github.com/mquinson/po4a/releases

There are two packages in Debian that seem to FTBFS because of that. In
addition to this bug, there is also the following bug against multistrap:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906386

Since it is unclear to me what the correct replacement for po4a-build is, I
contacted upstream about it:

https://github.com/mquinson/po4a/issues/144

Since this bug is also still unfixed, I thought that this information might be
helpful for you as well. :)

Just in case, I also CC-ed the po4a maintainers.

Thanks!

cheers, josch

Attachment: signature.asc
Description: signature


Reply to: