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

Re: Bug#660245: liblog4ada: FTBFS when not building docs: pdflatex: Command not found



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Le 17/02/2012 21:44, Aaron M. Ucko a écrit :
> xavier grave <xavier.grave@ipno.in2p3.fr> writes:
> 
>> Thanks you for reporting this bug, I have build this package with
>> pbuilder. Can you give me pointers to the minimal environment building
>> only architecture-dependent binary packages please ? I'm not familiar
>> with the autobuilders.
> 
> The autobuilders run sbuild, but pbuilder also supports just building
> (and installing build dependencies for) architecture-dependent packages:
> 
>   pdebuild -- --binary-arch
> 
>   pbuilder --build --binary-arch liblog4ada_*.dsc
> 
> Thanks for checking!

Here are my checks :

I reproduce the problem with :
debuild -- --binary-arch

under a sid environment (without pdflatex from texlive-latex-base ):
a fakeroot debian/rules binary-arch
builds fine and a fakeroot debian/rules binary-indep fails without the
texlive-latex-base package.

My package seems to follow Debian policy [1], and pdflatex is only
called when building -doc package. May be I'm wrong on this point ?

The problem seems very related to bug #521918 to me. Do you think I
should open a bug against pdebuild ? Quite strange the bug #452567 seems
to be the exact opposite of the problem my package have.

Since texlive-latex-base and texlive suite is a quite big suite to
install I'd like your advice before doing any packaging modification
that can lead in a longer build as in #452567 (merging
Build-Depends-Indep in Build-Depends).

Thanks again for your quick answer to my pdebuild related question.

xavier
[1]
http://www.debian.org/doc/debian-policy/ch-relationships.html#s-sourcebinarydeps
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJPQjCSAAoJEG3iFwasTcfaMVYQALwL54zZggLPWRrCdkUDWyeW
QeeTDgmdnc7YZE7EMsv0RjZkfKOVr2ALoByKdNu49Za0rWFdbEOcwUu/HsiWjDX4
w4ODPWvgYKb7PmTWxvJ8ALRmR37FJjMlLqIBXzXotnlNta0w4bB+2aRsbP7FtSk7
uMVulGoc22C6Razh65tg6kZPMmgNgU9SRviETiNJZAs89nu3w6dgOROqDJET7uId
7hn9S/AGUId2DxCZnqAbkqfn4NX5a3Ay+Oqud1ZJdP6273EeTtHEluxRS8QUoqL4
buiIqTvn6RdU8sbL4+DwARXfS3rRr/+ltUoidXj1QaABXTnt/QSCGCEvbK1jWQNe
Q7WidPkhteyfYPbYPgDtpi9225Op2NywuRvv0Xed9osr3Ff7znrN8AKNfh6YdqQ6
zo2cQUPChqnyvt05mm+U/gqvNSQuxbNuOgTyEqhLyk0SJL4MSQVL7tU7NrFcmD61
Z4Vao2il2kitTfYig1ZxIpjLqzGnysFtmqjfJMNtjdJ1KayACh3hEVAEi7ZE0bsx
NJm0EuJSMY+81GxlnbmOS/ANtxsg95PE1BSR7tZxEkZYdun//puY5VrygHP9OGiK
PMrbk912xFDDNv9OmYF8nzGbMjGu/1K7laHk9eW+9QIYxEMotR0zlXrQ5vaDRkzl
yP0iTIy5rh/3lEuz59Pq
=rjKe
-----END PGP SIGNATURE-----


Reply to: