Le dim. 14 févr. 2021 à 17:33, Leopold Palomo-Avellaneda <[email protected]> a écrit :
> Hi Mechtilde, > > > El 14/2/21 a les 14:41, Mechtilde Stehmann ha escrit: > > Hello Leopold, > > hello all, > > > > does it also build at buildd after a source only upload. > > ok > > > At the official build machines it is n't allowed to install a package > > which isn't called in debian/control beside the essential build packages. > > yes, you are right. > > > You have to call *all needed* packages for building in debian/control. > > Otherwise it can't be build at the official build machines. > > Yes, it's true. But, this is not the case. It call all the dependencies > to build the package. But it fails *before* you call pbuilder in a clean > env. > > > This should be ensured by pbuilder. You have to be able to build in a > > clean pbuilder chroot. > > I have a pbuilder installation to build packages. I'm using pbuilder, > and I built a lot of backports to myself. The server where I run > pbuilder is a Debian stable with several packages installed, nothing > important. Without sphinx-common, when I try to build paperwork, from > salsa I got: > > $ pdebuild > W: /root/.pbuilderrc does not exist > dpkg-checkbuilddeps: error: Unmet build dependencies: python3-sphinx > python3-sphinxcontrib.plantuml sphinx-doc > W: Unmet build-dependency in source > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: applying > 0001-Search-for-data-files-in-system-folders.patch > dpkg-source: info: applying > 0002-Show-all-page-at-once-until-python3-getkey-gets-pack.patch > dpkg-source: info: applying > 0003-Disable-potentially-dangerous-plugins.patch > dh clean --with python3,sphinxdoc --buildsystem=pybuild > dh: error: unable to load addon sphinxdoc: Can't locate > Debian/Debhelper/Sequence/sphinxdoc.pm in @INC (you may need to install > the Debian::Debhelper::Sequence::sphinxdoc module) (@INC contains: > /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.28.1 > /usr/local/share/perl/5.28.1 /usr/lib/x86_64-linux-gnu/perl5/5.28 > /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.28 > /usr/share/perl/5.28 /usr/local/lib/site_perl > /usr/lib/x86_64-linux-gnu/perl-base) at (eval 15) line 1. > BEGIN failed--compilation aborted at (eval 15) line 1. > > make: *** [debian/rules:38: clean] Error 25 > > Before, pbuilder is call. However, if I install sphinx-common and run > again pbuilder paperwork is built. > > Another thing is if you really need to call: > > dh $@ --with python3,sphinxdoc --buildsystem=pybuild > > with sphinxdoc. > > In any case, salsa C-I is passed and doesn't fail, and AFAIK they use a > similar env as build machines. Please, DD, push this package. It would > be a pity that we don't have this version in Bullseye. > > Best regards, > > Leopold > > > > Kind regards > > > > Mechtilde > > > > Am 14.02.21 um 14:15 schrieb Leopold Palomo-Avellaneda: > >> Mechtilde, > >> > >> > >> El 14/2/21 a les 14:04, Mechtilde Stehmann ha escrit: > >> > >> [...] > >> > >>> dh clean --with python3,sphinxdoc --buildsystem=pybuild > >>> dh: error: unable to load addon sphinxdoc: Can't locate > >>> Debian/Debhelper/Sequence/sphinxdoc.pm in @INC (you may need to > install > >>> the Debian::Debhelper::Sequence::sphinxdoc module) (@INC contains: > >>> /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.32.1 > >>> /usr/local/share/perl/5.32.1 /usr/lib/x86_64-linux-gnu/perl5/5.32 > >>> /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base > >>> /usr/lib/x86_64-linux-gnu/perl/5.32 /usr/share/perl/5.32 > >>> /usr/local/lib/site_perl) at (eval 14) line 1. > >>> BEGIN failed--compilation aborted at (eval 14) line 1. > >> > >> [...] > >> > >> > >> IMHO the problem that you have here is that you have not installed in > >> the box where you run pbuilder or gbp the package sphinx-common. > >> > >> That package contains the file > >> sphinx-common: /usr/share/perl5/Debian/Debhelper/Sequence/sphinxdoc.pm > >> > >> that needs Debhelper to prepare the package to be built. > >> > >> I have backported paperwork without any problem. > >> > >> Best regards, > >> > >> Leopold > Hello, i'll go ahead. However there is a high chance it won't migrate to testing, due to soft freeze policy as Thomas pointed out. Let's see. Jérémy
