Your message dated Thu, 2 Feb 2017 20:35:21 +0100
with message-id <[email protected]>
and subject line Re: Bug#853886: pbuilder: Does not parse DEBBUILDOPTS to
determine build type
has caused the Debian Bug report #853886,
regarding pbuilder: Does not parse DEBBUILDOPTS to determine build type
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
853886: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853886
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: cowbuilder
Version: 0.84
Severity: important
Hi,
after the recent cowbuilder update my gbp build script started to fail
for binary-indep-only (-A) and source-only builds (-S), complaining
about a missing *_amd64.changes file (see log below).
I assume the recent changes in cowbuilder cause this, but I'm not
totally sure about that. I also failed to find information what the
arch in the .changes file must be. I assume it's the host arch.
Otherwise I'd say git-pbuilder is looking for the wrong file.
Personally I see this as rc bug, but that's your call.
Thanks for taking care of cowbuilder!
Greets
jre
$ gbp buildpackage --git-pbuilder --git-arch=amd64 --git-dist=sid
--git-upstream-tag="wine-%(version)s" -S
gbp:info: Building with (cowbuilder) for sid:amd64
Building with cowbuilder for distribution sid, architecture amd64
+ pdebuild --buildresult ../ --pbuilder cowbuilder --debbuildopts '
'\''-S'\''' -- --architecture amd64 --basepath /home//base-sid-amd64.cow
I: using cowbuilder as pbuilder
[...]
make[1]: Leaving directory '/build/wine-development-2.0'
dpkg-source -b wine-development-2.0
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building wine-development using existing
./wine-development_2.0.orig.tar.xz
dpkg-source: info: building wine-development in
wine-development_2.0-3.debian.tar.xz
dpkg-source: info: building wine-development in wine-development_2.0-3.dsc
dpkg-genbuildinfo --build=source
dpkg-genchanges --build=source >../wine-development_2.0-3_source.changes
dpkg-genchanges: info: not including original source code in upload
dpkg-source --after-build wine-development-2.0
dpkg-buildpackage: info: binary and diff upload (original source NOT
included)
I: copying local configuration
E: Missing changes file:
/home/build/cow.29103/build/wine-development_2.0-3_amd64.changes
I: unmounting /home/ccache filesystem
I: unmounting dev/pts filesystem
I: unmounting dev/shm filesystem
I: unmounting proc filesystem
I: unmounting sys filesystem
I: Cleaning COW directory
I: forking: rm -rf /home/build/cow.29103
gbp:error: 'git-pbuilder -S' failed: it exited with 1
-- Manually added:
ii git-buildpackage 0.8.12.1
-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable-debug'), (500,
'testing-debug'), (500, 'unstable'), (100, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages cowbuilder depends on:
ii cowdancer 0.84
ii libc6 2.24-9
ii libncurses5 6.0+20161126-1
ii libtinfo5 6.0+20161126-1
ii pbuilder 0.228.3
cowbuilder recommends no packages.
cowbuilder suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Thu, Feb 02, 2017 at 08:12:02PM +0100, Jens Reyer wrote:
> For -S I'd have a use case (gbp tagging, and separate source build with
> the same tool after testing the binaries), but I see how this breaks the
> logic. I do this now in a "--binary-indep --source-only-changes" run,
> which is nearly as fast as the -S previously.
FYI, --source-only-changes can also be set in pbuilderrc, that way
you'll always get a _source.changes for every kind of build you perform.
Anyway, if your aim is to use `gbp buildpackage` always and ever, I
think (I'm not much a `gbp buildpackage` user myself, I use it only with
--git-tag-only…) you can call it with something like
--git-pbuilder debuild -S
There you won't use pbuilder at all (which is very much pointless for
source builds) and get the _source.chages only in the .. directory.
> Now --binary-indep gives me exactly the same as -A in the past, so there
> is a clean way to get the needed functionality. Since -S is not
> supported, I think it's less confusing to also not support -A.
I understa this view too.
> Maybe you could be even more explicit about the changes in NEWS. I'll
> revisit the wiki page in the next days/weeks.
Actually -S and -B and -A was never supported. pbuilder(8) always said:
--binary-arch
Use this option rather than using --debbuildopts -B.
--binary-indep
Use this option rather than using --debbuildopts -A.
since forever. (then again, --binary-indep is quite recent too, to be
fair, it's new in the stretch version…)
And the change that made -A not work anymore is coupled by
1) a dpkg change in 1.18.8 (Jul 2016) that named indep changes _all
2) https://anonscm.debian.org/git/pbuilder/pbuilder.git/commit/?id=64683d1
So there is no real change that willingly made -A not working anymore,
nor any changelog/news entry talking about that
> So yes, I'm fine with that by now.
Ok, closing this then, thank you!
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
--- End Message ---
