Debian Bug report logs - #806654
libtool: FTBFS in stretch when built with "dpkg-buildpackage -A"

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Santiago Vila <sanvila@debian.org>

To: Debian BTS <submit@bugs.debian.org>

Subject: libtool: FTBFS when built with dpkg-buildpackage -A (@include: could not find version.texi)

Date: Sun, 29 Nov 2015 20:25:03 +0000

Package: src:libtool
Version: 2.4.2-1.11
User: sanvila@debian.org
Usertags: binary-indep
Severity: important

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(i.e. only architecture-independent packages), and it failed:

--------------------------------------------------------------------------------
[...]
 debian/rules build-indep
cd doc && makeinfo libtool.texi
libtool.texi:9: @include: could not find version.texi
libtool.texi:27: warning: undefined flag: VERSION
libtool.texi:48: warning: undefined flag: VERSION
libtool.texi:48: warning: undefined flag: UPDATED
libtool.texi:82: warning: undefined flag: VERSION
libtool.texi:553: warning: undefined flag: VERSION
libtool.texi:586: warning: undefined flag: VERSION
libtool.texi:2097: warning: undefined flag: VERSION
debian/rules:153: recipe for target 'build-indep-stamp' failed
make: *** [build-indep-stamp] Error 1
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2
--------------------------------------------------------------------------------

Sorry not to have a fix, as I am reporting many bugs similar to
this one. The common hints are:

* If the only architecture-independent packages are dummy transitional
ones and they were released with jessie, the easy fix is to drop them
now.

* When using "dh", it is allowed to use (independently)
optional targets override_dh_foo-arch and override_dh_foo-indep
(for several values of "foo").


Once that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B" work
properly, the package would be suitable to be uploaded in source-only
form if you wish.

Thanks.

Message #10 received at 806654@bugs.debian.org (full text, mbox, reply):

From: Santiago Vila <sanvila@debian.org>

To: 806654@bugs.debian.org

Subject: libtool: FTBFS when built with dpkg-buildpackage -A (@include: could not find version.texi)

Date: Thu, 14 Jul 2016 22:10:04 +0000

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

Message #15 received at 806654@bugs.debian.org (full text, mbox, reply):

From: Kurt Roeckx <kurt@roeckx.be>

To: Santiago Vila <sanvila@debian.org>, 806654@bugs.debian.org

Subject: Re: Bug#806654: libtool: FTBFS when built with dpkg-buildpackage -A (@include: could not find version.texi)

Date: Mon, 25 Jul 2016 00:18:09 +0200

On Sun, Nov 29, 2015 at 08:25:03PM +0000, Santiago Vila wrote:
> Package: src:libtool
> Version: 2.4.2-1.11
> User: sanvila@debian.org
> Usertags: binary-indep
> Severity: important
> 
> Dear maintainer:
> 
> I tried to build this package with "dpkg-buildpackage -A"
> (i.e. only architecture-independent packages), and it failed:
> 
> --------------------------------------------------------------------------------
> [...]
>  debian/rules build-indep
> cd doc && makeinfo libtool.texi
> libtool.texi:9: @include: could not find version.texi
> libtool.texi:27: warning: undefined flag: VERSION
> libtool.texi:48: warning: undefined flag: VERSION
> libtool.texi:48: warning: undefined flag: UPDATED
> libtool.texi:82: warning: undefined flag: VERSION
> libtool.texi:553: warning: undefined flag: VERSION
> libtool.texi:586: warning: undefined flag: VERSION
> libtool.texi:2097: warning: undefined flag: VERSION
> debian/rules:153: recipe for target 'build-indep-stamp' failed
> make: *** [build-indep-stamp] Error 1
> dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2
> --------------------------------------------------------------------------------

I can't reproduce this.  This might have been fixed in 2.4.6-0.1
with:
  * Build-depend on texinfo needed by bootstrap.

So we should probably just close this.


Kurt

Message #20 received at 806654@bugs.debian.org (full text, mbox, reply):

From: Santiago Vila <sanvila@unex.es>

To: Kurt Roeckx <kurt@roeckx.be>

Cc: 806654@bugs.debian.org, control@bugs.debian.org

Subject: Re: Bug#806654: libtool: FTBFS when built with dpkg-buildpackage -A (@include: could not find version.texi)

Date: Mon, 25 Jul 2016 00:39:27 +0100

[Message part 1 (text/plain, inline)]

retitle 806654 libtool: FTBFS in stretch when built with "dpkg-buildpackage -A"
thanks

On Mon, Jul 25, 2016 at 12:18:09AM +0200, Kurt Roeckx wrote:

> > libtool.texi:553: warning: undefined flag: VERSION
> > libtool.texi:586: warning: undefined flag: VERSION
> > libtool.texi:2097: warning: undefined flag: VERSION
> > debian/rules:153: recipe for target 'build-indep-stamp' failed
> > make: *** [build-indep-stamp] Error 1
> > dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2
> > --------------------------------------------------------------------------------
> 
> I can't reproduce this.  This might have been fixed in 2.4.6-0.1
> with:
>   * Build-depend on texinfo needed by bootstrap.

The error is now quite different, but it still fails for me every time I try:

Status: attempted   libtool_2.4.6-0.1_amd64-20160213-1207
Status: attempted   libtool_2.4.6-0.1_amd64-20160302-1319
Status: attempted   libtool_2.4.6-0.1_amd64-20160321-2228
Status: attempted   libtool_2.4.6-0.1_amd64-20160505-1253
Status: attempted   libtool_2.4.6-0.1_amd64-20160526-1139
Status: attempted   libtool_2.4.6-0.1_amd64-20160621-1424
Status: attempted   libtool_2.4.6-0.1_amd64-20160725-0113

I attach the last build log.

I also attach a small collection of testsuite.log files I could rescue
before compilation ended and sbuild removed everything.

Hope this helps.

[libtool_2.4.6-0.1_amd64-20160725-0113.gz (application/gzip, attachment)]

[57.tgz (application/x-gtar-compressed, attachment)]

Message #27 received at 806654@bugs.debian.org (full text, mbox, reply):

From: Santiago Vila <sanvila@unex.es>

To: Kurt Roeckx <kurt@roeckx.be>, Matthias Klose <doko@debian.org>

Cc: 806654@bugs.debian.org

Subject: Re: Bug#806654: libtool: FTBFS when built with dpkg-buildpackage -A

Date: Mon, 25 Jul 2016 16:47:12 +0200 (CEST)

[Message part 1 (text/plain, inline)]

[ Cc:ing Matthias, as he did the last NMUs for this package ]

On Mon, 25 Jul 2016, Kurt Roeckx wrote:

> I can't reproduce this. [...]

Indeed, the error you quoted does not happen anymore, but the package
still would not autobuild in the "Arch: all" autobuilder.

Please note that this bug is about "dpkg-buildpackge -A" not working.

I think the error is somewhere in debian/rules. Let's take a look:


build: build-arch build-indep

build-arch: build-stamp
build-stamp: config-stamp
        [ standard package build ]

So far, so good.

build-indep: build-indep-stamp
build-indep-stamp:
#       This generated HTML page goes into libtool-doc.
	cd doc && $(MAKEINFO) libtool.texi
	cd doc && $(MAKEINFO) --html --no-split libtool.texi
	touch build-indep-stamp

So far, so good.

Based on this, it's clear that there is an *intent* to split the build
between build-arch and build-indep.

The binary-* targets, however, seem to "spoil" this intent:

install: build
        [ rules to install things in debian/tmp ]

binary-indep: build-indep install
        [ rules to create arch-independent packages ]

binary-arch: build-arch install
        [ rules to create arch-dependent packages ]

See the problem?

Target "binary-indep" depends on "install", "install" depends on
"build". Target "build" builds everything, so the "split"
does not really work because trying to create only arch-independent packages
ends up building everything.

(I also fear that the build-indep target is executed as a normal user,
then the binary-indep target is executed as root, which makes the whole
build process to be executed by root. This might have something to do
with the fact that it fails, but I'm not sure).


I tried to fix this by dropping "install" as a dependency for
binary-indep. I found a problem with the symlinks so I decided
to use dh_link and debian/libtool.links instead.
(See patch in the first attach).

This didn't work because some files disappear. (See debdiff in the
second attach). Those files are in debian/libtool.install but we can't
use dh_install because the files simply do not exist.


At this point, I can only suggest two possible fixes:

1. Make "libtool" package to be "Arch: any".

2. Build the package the traditional way:

build-arch: build
build-indep: build
build:
[ Build everything ]


Thanks.

[libtool.patch.txt (text/plain, attachment)]

[debdiff.txt (text/plain, attachment)]

Message #32 received at 806654@bugs.debian.org (full text, mbox, reply):

From: Kurt Roeckx <kurt@roeckx.be>

To: Santiago Vila <sanvila@unex.es>

Cc: 806654@bugs.debian.org, control@bugs.debian.org

Subject: Re: Bug#806654: libtool: FTBFS when built with dpkg-buildpackage -A (@include: could not find version.texi)

Date: Mon, 25 Jul 2016 18:19:35 +0200

On Mon, Jul 25, 2016 at 12:39:27AM +0100, Santiago Vila wrote:
> retitle 806654 libtool: FTBFS in stretch when built with "dpkg-buildpackage -A"
> thanks
> 
> On Mon, Jul 25, 2016 at 12:18:09AM +0200, Kurt Roeckx wrote:
> 
> > > libtool.texi:553: warning: undefined flag: VERSION
> > > libtool.texi:586: warning: undefined flag: VERSION
> > > libtool.texi:2097: warning: undefined flag: VERSION
> > > debian/rules:153: recipe for target 'build-indep-stamp' failed
> > > make: *** [build-indep-stamp] Error 1
> > > dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2
> > > --------------------------------------------------------------------------------
> > 
> > I can't reproduce this.  This might have been fixed in 2.4.6-0.1
> > with:
> >   * Build-depend on texinfo needed by bootstrap.
> 
> The error is now quite different, but it still fails for me every time I try:

The error you get is a testsuite failure.  It outputs this to
stderr:
ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.

And then the testsuite fails because it wasn't expecting any
output on stderr.

Anyway, this seems like a setup problem, not a problem with the
package, and cleary unrelated to using -A.


Kurt

Message #37 received at 806654@bugs.debian.org (full text, mbox, reply):

From: Kurt Roeckx <kurt@roeckx.be>

To: Santiago Vila <sanvila@unex.es>

Cc: Matthias Klose <doko@debian.org>, 806654@bugs.debian.org

Subject: Re: Bug#806654: libtool: FTBFS when built with dpkg-buildpackage -A

Date: Mon, 25 Jul 2016 18:30:34 +0200

On Mon, Jul 25, 2016 at 04:47:12PM +0200, Santiago Vila wrote:
> [ Cc:ing Matthias, as he did the last NMUs for this package ]
> 
> On Mon, 25 Jul 2016, Kurt Roeckx wrote:
> 
> > I can't reproduce this. [...]
> 
> Indeed, the error you quoted does not happen anymore, but the package
> still would not autobuild in the "Arch: all" autobuilder.
> 
> Please note that this bug is about "dpkg-buildpackge -A" not working.
> 
> I think the error is somewhere in debian/rules. Let's take a look:
> 
> 
> build: build-arch build-indep
> 
> build-arch: build-stamp
> build-stamp: config-stamp
>         [ standard package build ]
> 
> So far, so good.
> 
> build-indep: build-indep-stamp
> build-indep-stamp:
> #       This generated HTML page goes into libtool-doc.
> 	cd doc && $(MAKEINFO) libtool.texi
> 	cd doc && $(MAKEINFO) --html --no-split libtool.texi
> 	touch build-indep-stamp
> 
> So far, so good.
> 
> Based on this, it's clear that there is an *intent* to split the build
> between build-arch and build-indep.
> 
> The binary-* targets, however, seem to "spoil" this intent:
> 
> install: build
>         [ rules to install things in debian/tmp ]
> 
> binary-indep: build-indep install
>         [ rules to create arch-independent packages ]
> 
> binary-arch: build-arch install
>         [ rules to create arch-dependent packages ]
> 
> See the problem?
> 
> Target "binary-indep" depends on "install", "install" depends on
> "build". Target "build" builds everything, so the "split"
> does not really work because trying to create only arch-independent packages
> ends up building everything.

I actually fixed all this yesterday, started writing all of this,
and then decided to remove it and just say that the thing
mentioned in this bug seems to have been fixed and works for me.

Anyway, there has been a bunch on NMUs (like 12) in which they
changed "libtool" from an arch any to an arch all package, and
have the libtool-bin package as the binary arch package.

But everything that was in the build-arch target is something I
actually want to run all the time now, including the test suite.
So I moved everything to a build target and have build-indep and
build-arch depend on it.

> This didn't work because some files disappear. (See debdiff in the
> second attach). Those files are in debian/libtool.install but we can't
> use dh_install because the files simply do not exist.

I was still working on this yesterday evening.  The bootstrap
thing generates a ChangeLog file based on git, which ends up empty
...

So there are things I'm working on, I just think the reason this
bug was opened is already fixed.



Kurt

Message #42 received at 806654@bugs.debian.org (full text, mbox, reply):

From: Santiago Vila <sanvila@unex.es>

To: Kurt Roeckx <kurt@roeckx.be>

Cc: 806654@bugs.debian.org

Subject: Re: Bug#806654: libtool: FTBFS when built with dpkg-buildpackage -A

Date: Mon, 25 Jul 2016 19:36:55 +0200 (CEST)

On Mon, 25 Jul 2016, Kurt Roeckx wrote:

> The error you get is a testsuite failure.  It outputs this to
> stderr:
> ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
> 
> And then the testsuite fails because it wasn't expecting any
> output on stderr.
> 
> Anyway, this seems like a setup problem, not a problem with the
> package, and cleary unrelated to using -A.

Well, it only happens when using -A, so it's clearly related.

I already explained the reason: Because of the way debian/rules is
written, the test suite runs as root when built with "dpkg-buildpackage -A".

Then it fails because there is some sort of conflict with fakeroot.

But this is a bug in debian/rules for running the test suite as root,
not a setup problem.

If you do not believe that the test suite runs as root when built
with "dpkg-buildpackage -A", try this simple patch:

--- a/debian/rules
+++ b/debian/rules
@@ -132,6 +132,8 @@ build-stamp: config-stamp
 
 ifeq ($(make_check), yes)
 #	Now make sure it works
+	echo I am `whoami`
+	false
 	-$(MAKE) check || touch tests-failed
 	-cat test-suite.log
 	-cat tests/testsuite.log

and then try "dpkg-buildpackage -A".

You will see "I am root".

Message #47 received at 806654@bugs.debian.org (full text, mbox, reply):

From: Santiago Vila <sanvila@unex.es>

To: Kurt Roeckx <kurt@roeckx.be>

Cc: Matthias Klose <doko@debian.org>, 806654@bugs.debian.org

Subject: Re: Bug#806654: libtool: FTBFS when built with dpkg-buildpackage -A

Date: Mon, 25 Jul 2016 20:01:29 +0200 (CEST)

On Mon, 25 Jul 2016, Kurt Roeckx wrote:

> the thing
> mentioned in this bug seems to have been fixed and works for me.
> [...]
> I just think the reason this bug was opened is already fixed.

This bug was opened because "dpkg-buildpackage -A" does not work.

It did not work before, and it still does not work (but for a
different reason).

If you really feel this "different reason" is enough to close this
report and open a new one, I will gladly open a new one if it makes
you to feel better.

But IMHO, this would not be practical, because my intent was always to
report an effect (failing "dpkg-buildpackage -A"), not a cause.

Thanks.

Message #52 received at 806654@bugs.debian.org (full text, mbox, reply):

From: Kurt Roeckx <kurt@roeckx.be>

To: Santiago Vila <sanvila@unex.es>

Cc: 806654@bugs.debian.org

Subject: Re: Bug#806654: libtool: FTBFS when built with dpkg-buildpackage -A

Date: Mon, 25 Jul 2016 20:31:02 +0200

On Mon, Jul 25, 2016 at 07:36:55PM +0200, Santiago Vila wrote:
> On Mon, 25 Jul 2016, Kurt Roeckx wrote:
> 
> > The error you get is a testsuite failure.  It outputs this to
> > stderr:
> > ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
> > 
> > And then the testsuite fails because it wasn't expecting any
> > output on stderr.
> > 
> > Anyway, this seems like a setup problem, not a problem with the
> > package, and cleary unrelated to using -A.
> 
> Well, it only happens when using -A, so it's clearly related.
> 
> I already explained the reason: Because of the way debian/rules is
> written, the test suite runs as root when built with "dpkg-buildpackage -A".

So that should have been fixed i the upload I did earlier today.


Kurt

Message #59 received at 806654@bugs.debian.org (full text, mbox, reply):

From: Kurt Roeckx <kurt@roeckx.be>

To: Santiago Vila <sanvila@unex.es>

Cc: 806654@bugs.debian.org

Subject: Re: Bug#806654: libtool: FTBFS when built with dpkg-buildpackage -A

Date: Mon, 1 Aug 2016 23:43:16 +0200

On Mon, Jul 25, 2016 at 08:31:02PM +0200, Kurt Roeckx wrote:
> On Mon, Jul 25, 2016 at 07:36:55PM +0200, Santiago Vila wrote:
> > On Mon, 25 Jul 2016, Kurt Roeckx wrote:
> > 
> > > The error you get is a testsuite failure.  It outputs this to
> > > stderr:
> > > ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
> > > 
> > > And then the testsuite fails because it wasn't expecting any
> > > output on stderr.
> > > 
> > > Anyway, this seems like a setup problem, not a problem with the
> > > package, and cleary unrelated to using -A.
> > 
> > Well, it only happens when using -A, so it's clearly related.
> > 
> > I already explained the reason: Because of the way debian/rules is
> > written, the test suite runs as root when built with "dpkg-buildpackage -A".
> 
> So that should have been fixed i the upload I did earlier today.

Can you still reproduce the problem?  I see you marked it as RC
now, but the buildds actually build it succesful.


Kurt

Message #64 received at 806654@bugs.debian.org (full text, mbox, reply):

From: Santiago Vila <sanvila@unex.es>

To: Kurt Roeckx <kurt@roeckx.be>

Cc: 806654@bugs.debian.org

Subject: Re: Bug#806654: libtool: FTBFS when built with dpkg-buildpackage -A

Date: Tue, 2 Aug 2016 01:04:31 +0200 (CEST)

On Mon, 1 Aug 2016, Kurt Roeckx wrote:

> Can you still reproduce the problem?  I see you marked it as RC
> now, but the buildds actually build it succesful.

I raised to serious because I raised to serious all the bugs that were
still open.

Sorry if I answer your question by making another one:

Are you still unable to reproduce the problem with the previous version?

See, I don't want to see this bug closed if I'm the only one able to
reproduce it with the previous version, because in such case there
would still be a problem somewhere (even if it's in another unrelated
package) and we could not consider the bug solved.

So: Could you please try "dpkg-buildpackage -A" on both the previous
version and the current one (in your own computer) and compare the
results?

Thanks.

Message #71 received at 806654@bugs.debian.org (full text, mbox, reply):

From: Kurt Roeckx <kurt@roeckx.be>

To: Santiago Vila <sanvila@unex.es>, 806654@bugs.debian.org

Subject: Re: Bug#806654: libtool: FTBFS when built with dpkg-buildpackage -A

Date: Sat, 6 Aug 2016 17:57:20 +0200

On Tue, Aug 02, 2016 at 01:04:31AM +0200, Santiago Vila wrote:
> On Mon, 1 Aug 2016, Kurt Roeckx wrote:
> 
> > Can you still reproduce the problem?  I see you marked it as RC
> > now, but the buildds actually build it succesful.
> 
> I raised to serious because I raised to serious all the bugs that were
> still open.
> 
> Sorry if I answer your question by making another one:
> 
> Are you still unable to reproduce the problem with the previous version?

I can reproduce your original issue about version.texi not being
found in the 2.4.2-1.11 version when you try to build it using -A.

That is, I can reproduce your original issue, not the one you
reported afterwards.

Like you said yourself, this issue was fixed already in 2.4.6-0.1
and you can't reproduce that anymore.

2.4.6-0.1 builds fine for me using -A.  2.4.6-1 even builds
fine on the buildds.  But you didn't try -1 yet afaik.  This might
solve the problem with your setup, or not.


Kurt

Message #76 received at 806654@bugs.debian.org (full text, mbox, reply):

From: Santiago Vila <sanvila@unex.es>

To: Kurt Roeckx <kurt@roeckx.be>

Cc: 806654@bugs.debian.org

Subject: Re: Bug#806654: libtool: FTBFS when built with dpkg-buildpackage -A

Date: Sat, 6 Aug 2016 19:11:50 +0200

On Sat, Aug 06, 2016 at 05:57:20PM +0200, Kurt Roeckx wrote:

> 2.4.6-0.1 builds fine for me using -A.

Please provide a build log for any of your successful
"dpkg-buildpackage -A" builds of libtool 2.4.6-0.1 in stretch.

Thanks.

Message #81 received at 806654-done@bugs.debian.org (full text, mbox, reply):

From: Kurt Roeckx <kurt@roeckx.be>

To: Santiago Vila <sanvila@unex.es>

Cc: 806654-done@bugs.debian.org

Subject: Re: Bug#806654: libtool: FTBFS when built with dpkg-buildpackage -A

Date: Sat, 6 Aug 2016 20:49:24 +0200

Version: 2.4.6-1

On Sat, Aug 06, 2016 at 07:11:50PM +0200, Santiago Vila wrote:
> On Sat, Aug 06, 2016 at 05:57:20PM +0200, Kurt Roeckx wrote:
> 
> > 2.4.6-0.1 builds fine for me using -A.
> 
> Please provide a build log for any of your successful
> "dpkg-buildpackage -A" builds of libtool 2.4.6-0.1 in stretch.

That was stupid of me.  Not wanting to wait for the test suite, it
takes a long time, I skipped the test suite.  And of course the
problem you reported was that that test suite gave errors.

So I could reproduce it with 2.4.6-0.1 but not with 2.4.6-1.



Kurt

Message #86 received at 806654@bugs.debian.org (full text, mbox, reply):

From: Santiago Vila <sanvila@unex.es>

To: Kurt Roeckx <kurt@roeckx.be>

Cc: 806654@bugs.debian.org

Subject: Re: Bug#806654: libtool: FTBFS when built with dpkg-buildpackage -A

Date: Sat, 6 Aug 2016 20:55:14 +0200

On Sat, Aug 06, 2016 at 08:49:24PM +0200, Kurt Roeckx wrote:
> Version: 2.4.6-1
> 
> On Sat, Aug 06, 2016 at 07:11:50PM +0200, Santiago Vila wrote:
> > On Sat, Aug 06, 2016 at 05:57:20PM +0200, Kurt Roeckx wrote:
> > 
> > > 2.4.6-0.1 builds fine for me using -A.
> > 
> > Please provide a build log for any of your successful
> > "dpkg-buildpackage -A" builds of libtool 2.4.6-0.1 in stretch.
> 
> That was stupid of me.  Not wanting to wait for the test suite, it
> takes a long time, I skipped the test suite.  And of course the
> problem you reported was that that test suite gave errors.
> 
> So I could reproduce it with 2.4.6-0.1 but not with 2.4.6-1.

Finally. Thank you.

Send a report that this bug log contains spam.