control: tags -1 +wontfix
On Sun, Oct 23, 2016 at 06:05:52PM +0200, Geert Stappers wrote:
> 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.
O.k!
Cheers,
-- Guido
