Your message dated Thu, 8 Sep 2016 11:41:30 +0000
with message-id <[email protected]>
and subject line Re: Bug#836940: cowbuilder, sbuild: should behave identically
in regard to default gnupg installation
has caused the Debian Bug report #836940,
regarding cowbuilder, sbuild: should behave identically in regard to default
gnupg installation
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.)
--
836940: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: cowbuilder, sbuild
Severity: normal
Hello cowbuilder and sbuild maintainers,
I am assigning this bug report to both of you in order to determine the
best course of action. Please feel free to reassign and change the
severity as appropriate.
The package xmlgraphics-commons started recently failing to build from
source in a clean sbuild environment although it was built successfully
on the buildd network a few months ago. This behavior cannot be observed
in a clean cowbuilder environment though. [1]
The reasoning for the FTBFS is a missing dependency on gnupg which was
always present in default cowbuilder and sbuild environments until
recently. According to [2] this behavioral change was introduced by the
apt maintainers, more accurately in version 1.3~exp1 of apt.
* move gnupg|gnupg2 from apt Depends to Recommends
This is causing build failures in sbuild now, not only for
xmlgraphics-commons but for all packages that relied on gnupg being
installed by default.
Please clarify if
1. This change should be reverted in apt to restore the old behavior
2. or if sbuild should install gnupg by default
3. or if cowbuilder should not install gnupg by default
I think it is important that all maintainers can rely on the same
default chroot environment to test their packages before uploading to
avoid possible build failures.
Thanks for maintaining these important tools and keep up the good work.
Regards,
Markus
[1] https://bugs.debian.org/834744
[2] https://bugs.debian.org/834898#39
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
On Thu, Sep 08, 2016 at 12:01:30AM +0200, Markus Koschany wrote:
> I'm using the latest packages from sid (cowbuilder 0.80, pbuilder
> 0.226). I'm not sure but I believe exporting
> DEBOOTSTRAPOPTS=--variant=buildd solved the issue for me. GnuPG is no
> longer installed by default. I'm using a slightly modified version of
> Ubuntu's .pbuilderrc which I have once copied from
>
> https://wiki.ubuntu.com/PbuilderHowto
>
> I'll check again tomorrow if gnupg will be installed without passing
> this option to pbuilder. It may well be that I did something wrong a few
> hours ago.
At any rate, I think it became quite clear that neither pbuilder nor
sbuild are directly at fault.
This discussion might have highlighted some areas that could be
improved, but in a thread like this is just about impossible to find
them out again. If people feels like it consider opening others,
possibly more specific, bugs (at least for pbuilder, but I'm sure
sbuild's maintainer likes them too).
I'm closing this one, as really both sbuild and pbuilder behaves
identically when it comes to gnupg not being installed by default.
--
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 ---
