On Thu, 2016-12-15 at 16:30 +0100, Guido Günther wrote: [...] > I'm not sure how you're invoking gbp but in my tests it passes on -tc > correctly:
Sorry, it's:
gbp buildpackage --git-ignore-new --git-debian-branch=master -tc
> $ gbp buildpackage --git-verbose -tc --git-no-pbuilder --git-builder=debuild
> gbp:debug: ['git', 'rev-parse', '--show-cdup']
> gbp:debug: ['git', 'rev-parse', '--is-bare-repository']
> gbp:debug: /bin/true [] []
> gbp:debug: ['git', 'status', '--porcelain']
> gbp:debug: ['git', 'symbolic-ref', 'HEAD']
> gbp:debug: ['git', 'show-ref', 'refs/heads/master']
> gbp:debug: ['git', 'rev-parse', '--quiet', '--verify', 'HEAD']
> gbp:debug: debuild ['-tc'] []
> dpkg-architecture: error: unknown GNU system type c, you must specify Debian
> architecture, too
> debuild: error: dpkg-architecture -tc -f gave error exit status 255
> gbp:error: 'debuild -tc' failed: it exited with 255
>
> But then debuild seems to have problems:
>
> $ debuild -tc
> dpkg-architecture: error: unknown GNU system type c, you must specify Debian
> architecture, too
> debuild: error: dpkg-architecture -tc -f gave error exit status 255
>
> Are you using debuild?
I didn't specifically request use of debuild, but apparently it's being
used by default.
Ben.
--
Ben Hutchings
It is easier to change the specification to fit the program than vice
versa.
signature.asc
Description: This is a digitally signed message part
