Bug#841786: git-buildpackage: strange moment of installing build dependencies

[Geert Stappers]

Package: git-buildpackage
Version: 0.8.5

Dear people close to git-buildpackage,


Here an report about `gbp buildpackage` behaving strange.

I think that it is good that mention that I'm new to git-buildpackage.


I got gbp working on one system.
Showing the first part ofit for reference.
-----8<----8<-----8<------
stappers@nero:~/src/pkg-radvd
$ gbp buildpackage
gbp:info: radvd_2.15.orig.tar.gz does not exist, creating from 'upstream/2.15'
Building with cowbuilder for distribution sid
W: /home/stappers/.pbuilderrc does not exist
I: using cowbuilder as pbuilder
dpkg-checkbuilddeps: Unmet build dependencies: bison libdaemon-dev check
W: Unmet build-dependency in source
dpkg-buildpackage: source package radvd
dpkg-buildpackage: source version 1:2.15-1.1
dpkg-buildpackage: source distribution UNRELEASED
dpkg-buildpackage: source changed by Geert Stappers <stap...@debian.org>
dpkg-source --before-build pkg-radvd
dpkg-source: info: applying kfreebsd.patch
dpkg-checkbuilddeps: Unmet build dependencies: bison libdaemon-dev check
dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting
dpkg-buildpackage: warning: (Use -d flag to override.)
dpkg-buildpackage: warning: this is currently a non-fatal warning with -S, but will probably become fatal in the future
fakeroot debian/rules clean
dh clean --with autoreconf
dh_testdir
debian/rules override_dh_auto_clean
make[1]: Entering directory '/home/stappers/src/pkg-radvd'
rm -f gram.c gram.h scanner.c
rm -f privsep.c
make[1]: Leaving directory '/home/stappers/src/pkg-radvd'
dh_autoreconf_clean
dh_clean
dpkg-source -b pkg-radvd
dpkg-source: info: using source format `3.0 (quilt)'
dpkg-source: info: building radvd using existing ./radvd_2.15.orig.tar.gz
dpkg-source: info: building radvd in radvd_2.15-1.1.debian.tar.xz
dpkg-source: info: building radvd in radvd_2.15-1.1.dsc
dpkg-genchanges -S >../radvd_2.15-1.1_source.changes
dpkg-genchanges: including full source code in upload
dpkg-source --after-build pkg-radvd
dpkg-source: info: unapplying kfreebsd.patch
dpkg-buildpackage: full upload (original source is included)
-> Copying COW directory
forking: rm -rf /var/cache/pbuilder/build//cow.27747
forking: cp -al /var/cache/pbuilder/base.cow /var/cache/pbuilder/build//cow.27747
I: unlink for ilistfile /var/cache/pbuilder/build//cow.27747/.ilist failed, it didn't exist?
forking: chroot /var/cache/pbuilder/build//cow.27747 cowdancer-ilistcreate /.ilist find . -xdev -path ./home -prune -o \( \( -type l -o -type f \) -a -links +1 -print0 \) | xargs -0 stat --format '%d %i '
-> Invoking pbuilder
forking: pbuilder build --debbuildopts --debbuildopts --buildplace /var/cache/pbuilder/build//cow.27747 --buildresult /home/stappers/src --debbuildopts --no-targz --internal-chrootexec chroot /var/cache/pbuilder/build//cow.27747 cow-shell /home/stappers/src/radvd_2.15-1.1.dsc
W: /home/stappers/.pbuilderrc does not exist
I: Running in no-targz mode
I: using fakeroot in build.
I: Current time: Sun Oct 23 13:10:05 CEST 2016
I: pbuilder-time-stamp: 1477221005
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: policy-rc.d already exists
I: Obtaining the cached apt archive contents
I: Installing the build-deps
-> Attempting to satisfy build-dependencies
-> Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team <pbuilde...@lists.alioth.debian.org>
Description: Dummy package to satisfy dependencies with aptitude - created by pbuilder
This package was created automatically by pbuilder to satisfy the
build-dependencies of the package being currently built.
Depends: dh-autoreconf, debhelper (>= 9), flex, bison, pkg-config, libdaemon-dev, check
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in '/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 11639 files and directories currently installed.)
Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ...
Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ...
dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring anyway as you requested:
pbuilder-satisfydepends-dummy depends on dh-autoreconf; however:
Package dh-autoreconf is not installed.
pbuilder-satisfydepends-dummy depends on debhelper (>= 9); however:
Package debhelper is not installed.
pbuilder-satisfydepends-dummy depends on flex; however:
Package flex is not installed.
-----8<----8<-----8<------

This what happens on another system.
-----8<----8<-----8<------
stappers@dussel:~/src/pkg-radvd
$ gbp buildpackage
gbp:info: Creating radvd_2.15.orig.tar.gz from 'upstream/2.15'
Building with cowbuilder for distribution sid
W: /home/stappers/.pbuilderrc does not exist
I: using cowbuilder as pbuilder
dpkg-checkbuilddeps: Unmet build dependencies: dh-autoreconf debhelper (>= 9) flex bison libdaemon-dev check
W: Unmet build-dependency in source
dpkg-buildpackage: source package radvd
dpkg-buildpackage: source version 1:2.15-1.1
dpkg-buildpackage: source distribution UNRELEASED
dpkg-buildpackage: source changed by Geert Stappers <stap...@debian.org>
dpkg-source --before-build pkg-radvd
dpkg-checkbuilddeps: Unmet build dependencies: dh-autoreconf debhelper (>= 9) flex bison libdaemon-dev check
dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting
dpkg-buildpackage: warning: (Use -d flag to override.)
dpkg-buildpackage: warning: this is currently a non-fatal warning with -S, but will probably become fatal in the future
fakeroot debian/rules clean
dh clean --with autoreconf
make: dh: Command not found
debian/rules:8: recipe for target 'clean' failed
make: *** [clean] Error 127
dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2
gbp:error: 'git-pbuilder' failed: it exited with 2
stappers@dussel:~/src/pkg-radvd
$
-----8<----8<-----8<------

It fails on missing build dependency debhelper.
I think that is strange.

Expected behaviour would/should be installing build dependencies.


More information about the systems 'nero' and 'dussel' in a next message.


Groeten
Geert Stappers
--
Leven en laten leven

[Geert Stappers]

On Sun, Oct 23, 2016 at 03:56:02PM +0200, Geert Stappers wrote:
>
> Here an report about `gbp buildpackage` behaving strange.
>

> -----8<----8<-----8<------
> stappers@nero:~/src/pkg-radvd
> $ gbp buildpackage

...

...

> I: Installing the build-deps
> -> Attempting to satisfy build-dependencies
> -> Creating pbuilder-satisfydepends-dummy package
> Package: pbuilder-satisfydepends-dummy

> -----8<----8<-----8<------
>
> This what happens on another system.
> -----8<----8<-----8<------
> stappers@dussel:~/src/pkg-radvd
> $ gbp buildpackage

...

> dpkg-source --before-build pkg-radvd
> dpkg-checkbuilddeps: Unmet build dependencies: dh-autoreconf debhelper (>= 9) flex bison libdaemon-dev check
> dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting
> dpkg-buildpackage: warning: (Use -d flag to override.)
> dpkg-buildpackage: warning: this is currently a non-fatal warning with -S, but will probably become fatal in the future
> fakeroot debian/rules clean
> dh clean --with autoreconf
> make: dh: Command not found
> debian/rules:8: recipe for target 'clean' failed
> make: *** [clean] Error 127
> dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2
> gbp:error: 'git-pbuilder' failed: it exited with 2
> stappers@dussel:~/src/pkg-radvd
> $
> -----8<----8<-----8<------
>
> It fails on missing build dependency debhelper.
> I think that is strange.
>
> Expected behaviour would/should be installing build dependencies.
>
>
> More information about the systems 'nero' and 'dussel' in a next message.

At system nero

-----8<----8<-----8<------
stappers@nero:~/src/pkg-radvd

$ arch
x86_64
stappers@nero:~/src/pkg-radvd
$ dpkg -l debhelper
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-============-============-=================================
ii debhelper 9.20140613 all helper programs for debian/rules
stappers@nero:~/src/pkg-radvd

$
-----8<----8<-----8<------

At system dussel

-----8<----8<-----8<------
stappers@dussel:~/src/pkg-radvd

$ arch
armv7l
stappers@dussel:~/src/pkg-radvd
$ dpkg -l debhelper
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-============-============-=================================
un debhelper <none> <none> (no description available)

stappers@dussel:~/src/pkg-radvd
$
-----8<----8<-----8<------

Oops, that is more then difference in architecture.

[Guido Günther]

Hi,

On Sun, Oct 23, 2016 at 03:56:02PM +0200, Geert Stappers wrote:

Does it abort here or run? I assume the build continues so it's rather
harmless. Anyways: at this point gbp already handed over to pbuilder so
if s.th. fails try to reproduce without gbp (--git-verbose will give
more details on how gbp invokes the other commands).

Same here: gbp already handed over to pbuilder. AFAIK there's
--use-pdebuild-internal to change that behaviour but I've not used it.
You can try running with -nc so it wohn't invoke clean outside of the
chroot.

Shall we reassign to pbuilder?

Cheers,
-- Guido

[Geert Stappers]

On Sun, Oct 23, 2016 at 04:57:20PM +0200, Guido Günther wrote:
> On Sun, Oct 23, 2016 at 03:56:02PM +0200, Geert Stappers wrote:
> > Here an report about `gbp buildpackage` behaving strange.
> >
> > I think that it is good that mention that I'm new to git-buildpackage.
> >
> > I got gbp working on one system.

> > Showing the first part of it for reference.

> > -----8<----8<-----8<------
> > stappers@nero:~/src/pkg-radvd
> > $ gbp buildpackage
> > gbp:info: radvd_2.15.orig.tar.gz does not exist, creating from 'upstream/2.15'
> > Building with cowbuilder for distribution sid

...
> > Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ...
> > dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring anyway as you requested:
> > pbuilder-satisfydepends-dummy depends on dh-autoreconf; however:
> > Package dh-autoreconf is not installed.
> > pbuilder-satisfydepends-dummy depends on debhelper (>= 9); however:
> > Package debhelper is not installed.
> > pbuilder-satisfydepends-dummy depends on flex; however:
> > Package flex is not installed.
>
> Does it abort here or run?

It runs fine ( on that system ).

> I assume the build continues so it's rather harmless.

Yes. True. I could / should have express more clearly
that I was showing only the _first part_ of a working build.

> > -----8<----8<-----8<------
> >
> > This what happens on another system.
> > -----8<----8<-----8<------
> > stappers@dussel:~/src/pkg-radvd
> > $ gbp buildpackage

> > Building with cowbuilder for distribution sid

"cowbuilder"

> > W: /home/stappers/.pbuilderrc does not exist
> > I: using cowbuilder as pbuilder
> > dpkg-checkbuilddeps: Unmet build dependencies: dh-autoreconf debhelper (>= 9) flex bison libdaemon-dev check
> > W: Unmet build-dependency in source

...

> > dpkg-source --before-build pkg-radvd
> > dpkg-checkbuilddeps: Unmet build dependencies: dh-autoreconf debhelper (>= 9) flex bison libdaemon-dev check
> > dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting
> > dpkg-buildpackage: warning: (Use -d flag to override.)
> > dpkg-buildpackage: warning: this is currently a non-fatal warning with -S, but will probably become fatal in the future
> > fakeroot debian/rules clean
> > dh clean --with autoreconf
> > make: dh: Command not found
> > debian/rules:8: recipe for target 'clean' failed
> > make: *** [clean] Error 127
> > dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2
> > gbp:error: 'git-pbuilder' failed: it exited with 2
> > stappers@dussel:~/src/pkg-radvd
> > $
> > -----8<----8<-----8<------
> >
> > It fails on missing build dependency debhelper.
> > I think that is strange.
>
> Same here: gbp already handed over to pbuilder. AFAIK there's
> --use-pdebuild-internal to change that behaviour but I've not used it.
> You can try running with -nc so it wohn't invoke clean outside of the
> chroot.
>
> Shall we reassign to pbuilder?

Answer follows.

This report (reported to bug tracking system) is to tell:

Hey, this is strange, I have build dependencies defined,
but upon build I got error on missing build dependency.

Meanwhile I know / learned that some build dependencies are
needed _outside_ the {p,cow}builder.

What I did was `gbp buildpackage`. And I got I working on one system.
On another system it failed. Both times I assumed, in fact expected,
that "gbp" was doing the magic.

> Shall we reassign to pbuilder?

Leave it here and mark it as "wouldnotfix"
The idea is being part of git-buildpackage documentation.

I think more people will do `gbp buildpackage` on a fresh system
with expectation that git-buildbuildpackage, gbp, has done te proper setup.

Before I reported my exprience, I did visit https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=git-buildpackage
with a webbrowser. Did a text search on the page ( "control-F" ) on 'depen'
but got no hit. People now coming to the (bug)report overview page
will find a BR with title:

git-buildpackage: strange moment of installing build dependencies



Summary: I don't think it makes NO sense re-assign to pbuilder. ( or cowbuilder)

> Cheers,
> -- Guido

[Guido Günther]

control: tags -1 +wontfix

O.k!
Cheers,
-- Guido

[Geert Stappers]

Todays 'gbp buildpackage Unmet build dependencies' websearch
did bring me to this bugreport :-/

Yes, `gbp buildpackage --options` did report unmet build dependencies
to me. Again in early stage during build. I have the feeling that
the check on build depends is done before entering the "cowbuilder"
environment.

Installing the build depends on the actual host, so not in
the "cowbuilder" / "pbuilder" environ, got me a succesfull build.

Now updating this bugreport. Hi Guido, thanks for having it open
and marked "wontfix". It allowed an updates like this.


Cheers