Re: Samba FTBFS - no idea why
On 04/12/15 12:23, John Paul Adrian Glaubitz wrote:
> On 12/04/2015 12:53 PM, Mark Cave-Ayland wrote:
>> It was a few years back I ran into this, but from memory the fallback
>> downloads weren't cached so all the stylesheets were downloaded for
>> every build which took a significant amount of time
>
> But as I said, downloading the stylesheet with wget does work. So
> the file is there on the server:
>
>> http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl
Yes but depending upon server loads/time of day etc. then I would see
random connection failures/hangs presumably because due to load and
network issues - as you are no doubt already aware, it only takes a
single failure to stop the build :(
Taking a look at the links you posted:
Good:
https://buildd.debian.org/status/fetch.php?pkg=samba&arch=sparc64&ver=2%3A4.1.20%2Bdfsg-1&stamp=1443023396
Bad:
https://buildd.debian.org/status/fetch.php?pkg=samba&arch=sparc64&ver=2%3A4.1.21%2Bdfsg-1&stamp=1447611288
Search both of these for "'configure' finished successfully" and for the
failed build you see this:
'configure' finished successfully (13m9.177s)
A local copy of the docbook.xsl wasn't found on your system consider
installing package like docbook-xsl
A local copy of the docbook.xsl wasn't found on your system consider
installing package like docbook-xsl
A local copy of the docbook.xsl wasn't found on your system consider
installing package like docbook-xsl
It looks like the build script is installing the docbook-xsl package
into the chroot but configure isn't finding the stylesheets for the bad
build which explains the behaviour you see. I do remember having to
patch stylesheet paths in configure for some packages a while back but
that was a couple of years ago... I'd go back and check whether the
stylesheet parts of docbook-xsl have been split into a separate package
which requires a new dependency or whether the paths to the stylesheets
in the package themselves are different between the two builds and
whether they match those in Samba's configure script.
On the plus side, for the good build it seems docbook is being invoked
with the --nonet option so that should prevent random pauses during the
build once everything is up and working correctly.
ATB,
Mark.
Reply to: