Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#843137: sbuild: fails to deal with sid chroots (missing gpg)
19 views
Skip to first unread message
Cyril Brulebois
Nov 4, 2016, 5:10:02 AM11/4/16
to
Package: sbuild
Version: 0.65.2-1
Severity: serious
Justification: fails to work in the most trivial case
Hi,
a brand new unstable chroot isn't usable for a build with default (as
far as I can remember) sbuild configuration. Full log follows:
| kibi@wodi:/scratch/build$ sbuild -c unstable-amd64-sbuild -d unstable compiz_0.9.13.0+16.10.20160818.2-1.dsc
| sbuild (Debian sbuild) 0.65.2 (24 Mar 2015) on wodi
|
| ╔══════════════════════════════════════════════════════════════════════════════╗
| ║ compiz 1:0.9.13.0+16.10.20160818.2-1 (amd64) 04 Nov 2016 01:35 ║
| ╚══════════════════════════════════════════════════════════════════════════════╝
|
| Package: compiz
| Version: 1:0.9.13.0+16.10.20160818.2-1
| Source Version: 1:0.9.13.0+16.10.20160818.2-1
| Distribution: unstable
| Machine Architecture: amd64
| Host Architecture: amd64
| Build Architecture: amd64
|
| I: NOTICE: Log filtering will replace 'build/compiz-IZ1iK5/compiz-0.9.13.0+16.10.20160818.2' with '«PKGBUILDDIR»'
| I: NOTICE: Log filtering will replace 'build/compiz-IZ1iK5' with '«BUILDDIR»'
| I: NOTICE: Log filtering will replace 'var/lib/schroot/mount/unstable-amd64-sbuild-3f3d7a5e-fd4d-49c7-9d21-537562658e0c' with '«CHROOT»'
|
| ┌──────────────────────────────────────────────────────────────────────────────┐
| │ Update chroot │
| └──────────────────────────────────────────────────────────────────────────────┘
|
| Hit:1 http://localhost/debian unstable InRelease
| Reading package lists...
| W: No sandbox user '_apt' on the system, can not drop privileges
| Reading package lists...
| Building dependency tree...
| Calculating upgrade...
| 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
|
| ┌──────────────────────────────────────────────────────────────────────────────┐
| │ Fetch source files │
| └──────────────────────────────────────────────────────────────────────────────┘
|
|
| Local sources
| ─────────────
|
| compiz_0.9.13.0+16.10.20160818.2-1.dsc exists in .; copying to chroot
|
| Check architectures
| ───────────────────
|
|
| Check dependencies
| ──────────────────
|
| Merged Build-Depends: build-essential, fakeroot
| Filtered Build-Depends: build-essential, fakeroot
| dpkg-deb: building package 'sbuild-build-depends-core-dummy' in '/«BUILDDIR»/resolver-ANKNBn/apt_archive/sbuild-build-depends-core-dummy.deb'.
| E: Failed to execute “gpg”: No such file or directory
| Failed to sign dummy archive Release file.
|
| ┌──────────────────────────────────────────────────────────────────────────────┐
| │ Cleanup │
| └──────────────────────────────────────────────────────────────────────────────┘
|
| Purging /«BUILDDIR»
| Reading package lists...
| Building dependency tree...
| 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
| Reading package lists...
| Building dependency tree...
| 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
| E: Core build dependencies not satisfied; skipping
|
| ┌──────────────────────────────────────────────────────────────────────────────┐
| │ Summary │
| └──────────────────────────────────────────────────────────────────────────────┘
|
| Build Architecture: amd64
| Build-Space: 0
| Build-Time: 0
| Distribution: unstable
| Fail-Stage: install-deps
| Host Architecture: amd64
| Install-Time: 0
| Job: compiz_0.9.13.0+16.10.20160818.2-1.dsc
| Machine Architecture: amd64
| Package: compiz
| Package-Time: 0
| Source-Version: 1:0.9.13.0+16.10.20160818.2-1
| Space: 0
| Status: failed
| Version: 1:0.9.13.0+16.10.20160818.2-1
| ────────────────────────────────────────────────────────────────────────────────
| Finished at 20161104-0135
| Build needed 00:00:00, 0k disc space
| E: Core build dependencies not satisfied; skipping
Thanks for your time.
KiBi.
Version: 0.65.2-1
Severity: serious
Justification: fails to work in the most trivial case
Hi,
a brand new unstable chroot isn't usable for a build with default (as
far as I can remember) sbuild configuration. Full log follows:
| kibi@wodi:/scratch/build$ sbuild -c unstable-amd64-sbuild -d unstable compiz_0.9.13.0+16.10.20160818.2-1.dsc
| sbuild (Debian sbuild) 0.65.2 (24 Mar 2015) on wodi
|
| ╔══════════════════════════════════════════════════════════════════════════════╗
| ║ compiz 1:0.9.13.0+16.10.20160818.2-1 (amd64) 04 Nov 2016 01:35 ║
| ╚══════════════════════════════════════════════════════════════════════════════╝
|
| Package: compiz
| Version: 1:0.9.13.0+16.10.20160818.2-1
| Source Version: 1:0.9.13.0+16.10.20160818.2-1
| Distribution: unstable
| Machine Architecture: amd64
| Host Architecture: amd64
| Build Architecture: amd64
|
| I: NOTICE: Log filtering will replace 'build/compiz-IZ1iK5/compiz-0.9.13.0+16.10.20160818.2' with '«PKGBUILDDIR»'
| I: NOTICE: Log filtering will replace 'build/compiz-IZ1iK5' with '«BUILDDIR»'
| I: NOTICE: Log filtering will replace 'var/lib/schroot/mount/unstable-amd64-sbuild-3f3d7a5e-fd4d-49c7-9d21-537562658e0c' with '«CHROOT»'
|
| ┌──────────────────────────────────────────────────────────────────────────────┐
| │ Update chroot │
| └──────────────────────────────────────────────────────────────────────────────┘
|
| Hit:1 http://localhost/debian unstable InRelease
| Reading package lists...
| W: No sandbox user '_apt' on the system, can not drop privileges
| Reading package lists...
| Building dependency tree...
| Calculating upgrade...
| 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
|
| ┌──────────────────────────────────────────────────────────────────────────────┐
| │ Fetch source files │
| └──────────────────────────────────────────────────────────────────────────────┘
|
|
| Local sources
| ─────────────
|
| compiz_0.9.13.0+16.10.20160818.2-1.dsc exists in .; copying to chroot
|
| Check architectures
| ───────────────────
|
|
| Check dependencies
| ──────────────────
|
| Merged Build-Depends: build-essential, fakeroot
| Filtered Build-Depends: build-essential, fakeroot
| dpkg-deb: building package 'sbuild-build-depends-core-dummy' in '/«BUILDDIR»/resolver-ANKNBn/apt_archive/sbuild-build-depends-core-dummy.deb'.
| E: Failed to execute “gpg”: No such file or directory
| Failed to sign dummy archive Release file.
|
| ┌──────────────────────────────────────────────────────────────────────────────┐
| │ Cleanup │
| └──────────────────────────────────────────────────────────────────────────────┘
|
| Purging /«BUILDDIR»
| Reading package lists...
| Building dependency tree...
| 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
| Reading package lists...
| Building dependency tree...
| 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
| E: Core build dependencies not satisfied; skipping
|
| ┌──────────────────────────────────────────────────────────────────────────────┐
| │ Summary │
| └──────────────────────────────────────────────────────────────────────────────┘
|
| Build Architecture: amd64
| Build-Space: 0
| Build-Time: 0
| Distribution: unstable
| Fail-Stage: install-deps
| Host Architecture: amd64
| Install-Time: 0
| Job: compiz_0.9.13.0+16.10.20160818.2-1.dsc
| Machine Architecture: amd64
| Package: compiz
| Package-Time: 0
| Source-Version: 1:0.9.13.0+16.10.20160818.2-1
| Space: 0
| Status: failed
| Version: 1:0.9.13.0+16.10.20160818.2-1
| ────────────────────────────────────────────────────────────────────────────────
| Finished at 20161104-0135
| Build needed 00:00:00, 0k disc space
| E: Core build dependencies not satisfied; skipping
Thanks for your time.
KiBi.
Debian Bug Tracking System
Nov 4, 2016, 6:10:02 AM11/4/16
to
Processing control commands:
> fixed -1 0.67.0
Bug #843137 [sbuild] sbuild: fails to deal with sid chroots (missing gpg)
There is no source info for the package 'sbuild' at version '0.67.0' with architecture ''
Unable to make a source version for version '0.67.0'
Marked as fixed in versions 0.67.0.
--
843137: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843137
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
> fixed -1 0.67.0
Bug #843137 [sbuild] sbuild: fails to deal with sid chroots (missing gpg)
There is no source info for the package 'sbuild' at version '0.67.0' with architecture ''
Unable to make a source version for version '0.67.0'
Marked as fixed in versions 0.67.0.
--
843137: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843137
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Raphael Hertzog
Nov 4, 2016, 6:10:03 AM11/4/16
to
Hi Cyril,
On Fri, 04 Nov 2016, Cyril Brulebois wrote:
> a brand new unstable chroot isn't usable for a build with default (as
> far as I can remember) sbuild configuration. Full log follows:
It's not a "default" sbuild configuration, it's one where you created
a signing key. Get rid of /var/lib/sbuild/apt-keys and it should work (at
least on a recent sbuild, I saw you reported it on an old version, not
sure if that version already has the fallback mentioned below).
When a key is present there, sbuild wants to use it to sign the internal
repository and then your chroot needs to have gpg installed (and unstable
chroot no longer have it since apt dropped the dependency).
That said, it would be nice if sbuild was smarter, it could check gpg's
availability before deciding to sign the repository and then fallback to
using the "[trusted=yes]" sources.list attribute instead.
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/
On Fri, 04 Nov 2016, Cyril Brulebois wrote:
> a brand new unstable chroot isn't usable for a build with default (as
> far as I can remember) sbuild configuration. Full log follows:
a signing key. Get rid of /var/lib/sbuild/apt-keys and it should work (at
least on a recent sbuild, I saw you reported it on an old version, not
sure if that version already has the fallback mentioned below).
When a key is present there, sbuild wants to use it to sign the internal
repository and then your chroot needs to have gpg installed (and unstable
chroot no longer have it since apt dropped the dependency).
That said, it would be nice if sbuild was smarter, it could check gpg's
availability before deciding to sign the repository and then fallback to
using the "[trusted=yes]" sources.list attribute instead.
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/
Johannes Schauer
Nov 4, 2016, 2:20:01 PM11/4/16
to
Hi,
Quoting Raphael Hertzog (2016-11-04 16:01:21)
> On Fri, 04 Nov 2016, Johannes Schauer wrote:
> > 2. the amount of effort required to cope with the changed situation in stretch
> > (especially with respect to gpg) is huge. The existing patches are several
> > hundred lines long. Help would indeed be appreciated to backport these
> > patches. I fought with the gnupg situation for months to get it right and
> > make things both forward and backward compatible. Lots of work is needed to
> > do this right and test everything for a stable update. Unfortunately, this
> > is time I currently don't have. I would be available though for guidance
> > for anybody who's willing to give this a go.
>
> An easy fix might be to modifiy sbuild-createchroot to install gpg and to
> document this requirement?
as I pointed in other mails in this bug report, if you *do* sign the internal
dummy repository, then you run into loads of other problems because of changes
in gnupg2. You could of course turn off signing but then you loose support for
building in chroots with Squeeze (where apt is too old). But then, even if you
decide that squeeze is too old and we don't want to support it anymore in the
current stable, you will run into issues because gnupg is for example needed to
import apt keys or for external repositories and then you are back at the
gnupg2 incompatibilities and at making sure to kill the gnupg agent or
otherwise your schroot session cannot end. See the bugreports and commits I
listed for a good overview of all the problems.
Thanks!
cheers, josch
Quoting Raphael Hertzog (2016-11-04 16:01:21)
> On Fri, 04 Nov 2016, Johannes Schauer wrote:
> > 2. the amount of effort required to cope with the changed situation in stretch
> > (especially with respect to gpg) is huge. The existing patches are several
> > hundred lines long. Help would indeed be appreciated to backport these
> > patches. I fought with the gnupg situation for months to get it right and
> > make things both forward and backward compatible. Lots of work is needed to
> > do this right and test everything for a stable update. Unfortunately, this
> > is time I currently don't have. I would be available though for guidance
> > for anybody who's willing to give this a go.
>
> An easy fix might be to modifiy sbuild-createchroot to install gpg and to
> document this requirement?
as I pointed in other mails in this bug report, if you *do* sign the internal
dummy repository, then you run into loads of other problems because of changes
in gnupg2. You could of course turn off signing but then you loose support for
building in chroots with Squeeze (where apt is too old). But then, even if you
decide that squeeze is too old and we don't want to support it anymore in the
current stable, you will run into issues because gnupg is for example needed to
import apt keys or for external repositories and then you are back at the
gnupg2 incompatibilities and at making sure to kill the gnupg agent or
otherwise your schroot session cannot end. See the bugreports and commits I
listed for a good overview of all the problems.
Thanks!
cheers, josch
0 new messages