Your message dated Mon, 7 Dec 2015 16:07:40 +0100
with message-id <5665a0bc.6010...@physik.fu-berlin.de>
and subject line Re: [Pkg-samba-maint] Bug#807331: Bug#807331: samba: Fails to
build from source when not being able to download docbook.xsl
has caused the Debian Bug report #807331,
regarding samba: Fails to build from source when not being able to download
docbook.xsl
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
807331: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807331
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: samba
Version: 2:4.1.21+dfsg-2
Severity: serious
Justification: fails to build from source (sometimes)
Hello!
The samba package fails to build from source when it can't download the external
stylesheet docbook.xsl which is downloaded from sourceforge.net:
Checking for stylesheet
http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl : not
found
and consequently won't build the manpages which then results in:
#Remove unused vfstest manpage as there is no more vfstest apparently
rm /<<BUILDDIR>>/samba-4.1.21+dfsg/debian/tmp/usr/share/man/man1/vfstest.1
rm: cannot remove
'/<<BUILDDIR>>/samba-4.1.21+dfsg/debian/tmp/usr/share/man/man1/vfstest.1': No
such file or directory
debian/rules:93: recipe for target 'override_dh_install' failed
make[1]: *** [override_dh_install] Error 1
make[1]: Leaving directory '/<<BUILDDIR>>/samba-4.1.21+dfsg'
debian/rules:69: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
I'm not sure why exactly the download of the stylesheet fails. It fails on the
sparc64 and x32 buildds and on my personal sbuild amd64 chroot, all of them
are up-to-date. Since I can download the stylesheet from the very same machine
I am using for amd64 builds:
glaubitz@z6:~> wget
http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl
--2015-12-07 14:51:42--
http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl
Resolving docbook.sourceforge.net (docbook.sourceforge.net)... 216.34.181.96
Connecting to docbook.sourceforge.net
(docbook.sourceforge.net)|216.34.181.96|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 15230 (15K) [application/xslt+xml]
Saving to: ‘docbook.xsl’
docbook.xsl
100%[==================================================================>]
14.87K 64.5KB/s in 0.2s
2015-12-07 14:51:50 (64.5 KB/s) - ‘docbook.xsl’ saved [15230/15230]
glaubitz@z6:~>
it must be some extra sbuild/schroot configuration or additional package that
the samba build
scripts rely on to be able to download the stylesheet. However, I think it's
generally
bad when a package in Debian can no longer be build from source just because a
file on
a third party server is missing or corrupted. That being said, I think it's
also a
potential security problem when the buildds blindly download files from third
party
servers.
Cheers,
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.org
`. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
--- End Message ---
--- Begin Message ---
On 12/07/2015 03:38 PM, Jelmer Vernooij wrote:
>> That could explain the problem on sparc64 and x32, but it doesn't
>> segfault on my amd64 machine, yet the download fails. I can run xsltproc
>> with the URL in my sbuild chroot and it is able to download and parse
>> the file. However, when I sbuild samba, it still fails. I can't really
>> wrap my head around what happens here.
> Do you have /dev/shm available in your sbuild chroot, per that bug?
Ok, this *does* fix the problem actually. I have to bind-mount dev
into my chroot and set the permissions to 777. Veeeery strange that
xsltproc does not fail when I chroot into my sbuild environment and
call it directly, but it fails when the samba Python scripts call it.
In any case, thanks a lot for helping me to pin-point the issue. This
is indeed a bug in xsltproc then and we can therefore close this bug
again!
I will make the necessary modifications to all buildds in question!
Thanks,
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.org
`. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
--- End Message ---
