Debian Bug report logs - #911979
fails on chown in autopkgtest-qemu backend

Display info messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupre <anarcat@debian.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: fails on chown in autopkgtest-qemu backend

Date: Fri, 26 Oct 2018 15:33:32 -0400

Package: sbuild
Version: 0.77.1-1
Severity: normal

I have tried to use the autopkgtest backend with the qemu server but
it completely failed to launch the build:

gnupg2-2.1.181$ sbuild --chroot-mode=autopkgtest --autopkgtest-virt-server=qemu --autopkgtest-virt-server-opt=/var/lib/libvirt/images/debian9-amd64-autopkgtest.qcow2
dpkg-source: info: using options from gnupg2-2.1.18/debian/source/options: --compression=bzip2 --compression-level=9
dh clean --with=autoreconf --builddirectory=build
   dh_auto_clean -O--builddirectory=build
   dh_autoreconf_clean -O--builddirectory=build
   dh_clean -O--builddirectory=build
dpkg-source: info: using options from gnupg2-2.1.18/debian/source/options: --compression=bzip2 --compression-level=9
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building gnupg2 using existing ./gnupg2_2.1.18.orig.tar.bz2
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: warning: ignoring deletion of file po/sk.gmo, use --include-removal to override
dpkg-source: warning: ignoring deletion of file po/fi.gmo, use --include-removal to override
dpkg-source: warning: ignoring deletion of file po/ca.gmo, use --include-removal to override
dpkg-source: warning: ignoring deletion of file po/cs.gmo, use --include-removal to override
dpkg-source: warning: ignoring deletion of file po/zh_CN.gmo, use --include-removal to override
dpkg-source: warning: ignoring deletion of file po/nb.gmo, use --include-removal to override
dpkg-source: warning: ignoring deletion of file po/da.gmo, use --include-removal to override
dpkg-source: warning: ignoring deletion of file po/zh_TW.gmo, use --include-removal to override
dpkg-source: warning: ignoring deletion of file po/en@quot.gmo, use --include-removal to override
dpkg-source: warning: ignoring deletion of file po/pt.gmo, use --include-removal to override
dpkg-source: warning: ignoring deletion of file po/et.gmo, use --include-removal to override
dpkg-source: warning: ignoring deletion of file po/pl.gmo, use --include-removal to override
dpkg-source: warning: ignoring deletion of file po/en@boldquot.gmo, use --include-removal to override
dpkg-source: warning: ignoring deletion of file po/ro.gmo, use --include-removal to override
dpkg-source: warning: ignoring deletion of file po/es.gmo, use --include-removal to override
dpkg-source: warning: ignoring deletion of file po/eo.gmo, use --include-removal to override
dpkg-source: warning: ignoring deletion of file po/hu.gmo, use --include-removal to override
dpkg-source: warning: ignoring deletion of file po/de.gmo, use --include-removal to override
dpkg-source: warning: ignoring deletion of file po/id.gmo, use --include-removal to override
dpkg-source: warning: ignoring deletion of file po/fr.gmo, use --include-removal to override
dpkg-source: warning: ignoring deletion of file po/stamp-po, use --include-removal to override
dpkg-source: warning: ignoring deletion of file po/el.gmo, use --include-removal to override
dpkg-source: warning: ignoring deletion of file po/tr.gmo, use --include-removal to override
dpkg-source: warning: ignoring deletion of file po/uk.gmo, use --include-removal to override
dpkg-source: warning: ignoring deletion of file po/gl.gmo, use --include-removal to override
dpkg-source: warning: ignoring deletion of file po/it.gmo, use --include-removal to override
dpkg-source: warning: ignoring deletion of file po/ja.gmo, use --include-removal to override
dpkg-source: warning: ignoring deletion of file po/ru.gmo, use --include-removal to override
dpkg-source: warning: ignoring deletion of file po/sv.gmo, use --include-removal to override
dpkg-source: warning: ignoring deletion of file doc/gnupg.info, use --include-removal to override
dpkg-source: warning: ignoring deletion of file doc/gnupg.info-1, use --include-removal to override
dpkg-source: warning: ignoring deletion of file doc/gnupg.info-2, use --include-removal to override
dpkg-source: info: building gnupg2 in gnupg2_2.1.18-8~deb9u3.debian.tar.bz2
dpkg-source: info: building gnupg2 in gnupg2_2.1.18-8~deb9u3.dsc
dpkg-source: info: using options from gnupg2-2.1.18/debian/source/options: --compression=bzip2 --compression-level=9
sbuild (Debian sbuild) 0.77.1 (10 September 2018) on curie.anarc.at

+==============================================================================+
| gnupg2 2.1.18-8~deb9u3 (amd64)               Fri, 26 Oct 2018 19:19:15 +0000 |
+==============================================================================+

Package: gnupg2
Version: 2.1.18-8~deb9u3
Source Version: 2.1.18-8~deb9u3
Distribution: stretch
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: full

qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.vmx [bit 5]
chown: invalid user: 'sbuild:sbuild'
E: Failed to set sbuild:sbuild ownership on /build
Failed to set up chroot
E: Error creating chroot session: skipping gnupg2

+------------------------------------------------------------------------------+
| Summary                                                                      |
+------------------------------------------------------------------------------+

Build Architecture: amd64
Build Type: full
Build-Space: 0
Build-Time: 0
Distribution: stretch
Fail-Stage: create-session
Host Architecture: amd64
Install-Time: 0
Job: /home/anarcat/dist/gnupg2_2.1.18-8~deb9u3.dsc
Machine Architecture: amd64
Package: gnupg2
Package-Time: 0
Source-Version: 2.1.18-8~deb9u3
Space: 0
Status: failed
Version: 2.1.18-8~deb9u3
--------------------------------------------------------------------------------
Finished at 2018-10-26T19:19:15Z
Build needed 00:00:00, 0k disk space

I can test that package with autopkgtest fine, for what that's worth,
with:

autopkgtest . -- qemu

So this seems to be a problem specific to sbuild.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental'), (1, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8), LANGUAGE=fr_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages sbuild depends on:
ii  adduser         3.118
ii  libsbuild-perl  0.77.1-1
ii  perl            5.26.2-7+b1

Versions of packages sbuild recommends:
ii  autopkgtest  5.6
ii  debootstrap  1.0.109
ii  schroot      1.6.10-5

Versions of packages sbuild suggests:
ii  deborphan  1.7.30
ii  kmod       25-1
ii  wget       1.19.5-1

-- debconf-show failed

Message #10 received at 911979@bugs.debian.org (full text, mbox, reply):

From: Johannes Schauer <josch@debian.org>

To: 911979@bugs.debian.org

Cc: anarcat@debian.org

Subject: Re: fails on chown in autopkgtest-qemu backend

Date: Fri, 04 Jan 2019 12:50:41 +0100

[Message part 1 (text/plain, inline)]

Hi,

On Fri, 26 Oct 2018 15:33:32 -0400 Antoine Beaupre <anarcat@debian.org> wrote:
> I have tried to use the autopkgtest backend with the qemu server but it
> completely failed to launch the build:
>
> [...]
>
> chown: invalid user: 'sbuild:sbuild'
> E: Failed to set sbuild:sbuild ownership on /build
> Failed to set up chroot
>
> [...]
>
> I can test that package with autopkgtest fine, for what that's worth, with:
>
> autopkgtest . -- qemu
>
> So this seems to be a problem specific to sbuild.

could you try adding the sbuild user and group to your qemu guest?

sbuild-createchroot is doing some customizations after running debootstrap. One
of them is to copy the sbuild user and group from the host into the chroot so
that the user and group work with schoor. Obviously this is not necessary when
using qemu so maybe sbuild should add a new sbuild user and group itself when
it doesn't find them in the chroot already.

Thanks!

cheers, josch

[signature.asc (application/pgp-signature, inline)]

Message #15 received at 911979@bugs.debian.org (full text, mbox, reply):

From: Johannes Schauer <josch@debian.org>

To: 911979@bugs.debian.org

Cc: anarcat@debian.org

Subject: Re: fails on chown in autopkgtest-qemu backend

Date: Fri, 04 Jan 2019 22:20:52 +0100

[Message part 1 (text/plain, inline)]

Control: tag -1 + pending

Hi again,

On Fri, 04 Jan 2019 12:50:41 +0100 Johannes Schauer <josch@debian.org> wrote:
> On Fri, 26 Oct 2018 15:33:32 -0400 Antoine Beaupre <anarcat@debian.org> wrote:
> > I have tried to use the autopkgtest backend with the qemu server but it
> > completely failed to launch the build:
> >
> > [...]
> >
> > chown: invalid user: 'sbuild:sbuild'
> > E: Failed to set sbuild:sbuild ownership on /build
> > Failed to set up chroot
> >
> > [...]
> >
> > I can test that package with autopkgtest fine, for what that's worth, with:
> >
> > autopkgtest . -- qemu
> >
> > So this seems to be a problem specific to sbuild.
> 
> could you try adding the sbuild user and group to your qemu guest?
> 
> sbuild-createchroot is doing some customizations after running debootstrap. One
> of them is to copy the sbuild user and group from the host into the chroot so
> that the user and group work with schoor. Obviously this is not necessary when
> using qemu so maybe sbuild should add a new sbuild user and group itself when
> it doesn't find them in the chroot already.

okay, I was able to reproduce this problem myself and am hoping that I ran into
the same issue as you did. What I used to test was this sbuild invocation:

   $ sbuild --chroot-mode=autopkgtest --autopkgtest-virt-server=qemu \
   > --autopkgtest-virt-server-opts=/srv/qemu/unstable-amd64-autopkgtest.qcow2

And then I got the output you quoted in your first mail:

  +==============================================================================+
  | pkg-minimal 1.0 (amd64)                      Fri, 04 Jan 2019 20:37:45 +0000 |
  +==============================================================================+
  
  Package: pkg-minimal
  Version: 1.0
  Source Version: 1.0
  Distribution: unstable
  Machine Architecture: amd64
  Host Architecture: amd64
  Build Architecture: amd64
  Build Type: binary
  
  qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.vmx [bit 5]
  chown: invalid user: 'sbuild:sbuild'
  E: Failed to set sbuild:sbuild ownership on /build
  Failed to set up chroot
  E: Error creating chroot session: skipping pkg-minimal

I fixed the problem by changing sbuild such that it now creates the sbuild user
and the BUILD_USER inside the chroot if they don't exist yet. This job is
usually done by sbuild-createchroot but since you are using qemu I guess that
you didn't use sbuild-createchroot to create the base image?

Thanks!

cheers, josch

[signature.asc (application/pgp-signature, inline)]

Message #24 received at 911979@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@debian.org>

To: Johannes Schauer <josch@debian.org>, 911979@bugs.debian.org

Subject: Re: fails on chown in autopkgtest-qemu backend

Date: Fri, 04 Jan 2019 16:32:56 -0500

On 2019-01-04 22:20:52, Johannes Schauer wrote:

[...]

> I fixed the problem by changing sbuild such that it now creates the sbuild user
> and the BUILD_USER inside the chroot if they don't exist yet. This job is
> usually done by sbuild-createchroot but since you are using qemu I guess that
> you didn't use sbuild-createchroot to create the base image?

That's correct: I used autopkgtest to create the base image. :)

Thanks for the fix!

A.

-- 
Ce que les siècles des grands abatoirs nous aura appris
Devrait être inscrit au fond de toutes les écoles;
Voici l'homme: le destructeur des mondes est arrivé.
                        - [no one is innocent]

Message #29 received at 911979@bugs.debian.org (full text, mbox, reply):

From: Johannes Schauer <josch@debian.org>

To: 911979@bugs.debian.org, Antoine Beaupré <anarcat@debian.org>

Subject: Re: fails on chown in autopkgtest-qemu backend

Date: Fri, 04 Jan 2019 22:39:36 +0100

[Message part 1 (text/plain, inline)]

Quoting Antoine Beaupré (2019-01-04 22:32:56)
> > I fixed the problem by changing sbuild such that it now creates the sbuild
> > user and the BUILD_USER inside the chroot if they don't exist yet. This job
> > is usually done by sbuild-createchroot but since you are using qemu I guess
> > that you didn't use sbuild-createchroot to create the base image?
> 
> That's correct: I used autopkgtest to create the base image. :)

Since when can you use autopkgtest to create the base image? And how?

The last time I talked with the autopkgtest maintainers about a feature like
this, they were vehemently against adding any such functionality [1].

Thanks!

cheers, josch

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886332#20

[signature.asc (application/pgp-signature, inline)]

Message #32 received at 911979-submitter@bugs.debian.org (full text, mbox, reply):

From: Johannes 'josch' Schauer <josch@debian.org>

To: 911979-submitter@bugs.debian.org

Subject: Bug #911979 in sbuild marked as pending

Date: Sat, 05 Jan 2019 00:20:35 +0000

Control: tag -1 pending

Hello,

Bug #911979 in sbuild reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/debian/sbuild/commit/b22d91749e38c64136e21ea9db557493120c3b0a

------------------------------------------------------------------------
lib/Sbuild/ChrootSetup.pm: add sbuild and BUILD_USER if they didn't exist yet (closes: #911979)
------------------------------------------------------------------------

(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/911979

Message #37 received at 911979@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@debian.org>

To: Johannes Schauer <josch@debian.org>, 911979@bugs.debian.org

Subject: Re: fails on chown in autopkgtest-qemu backend

Date: Sat, 05 Jan 2019 12:34:16 -0500

On 2019-01-04 22:39:36, Johannes Schauer wrote:
> Quoting Antoine Beaupré (2019-01-04 22:32:56)
>> > I fixed the problem by changing sbuild such that it now creates the sbuild
>> > user and the BUILD_USER inside the chroot if they don't exist yet. This job
>> > is usually done by sbuild-createchroot but since you are using qemu I guess
>> > that you didn't use sbuild-createchroot to create the base image?
>> 
>> That's correct: I used autopkgtest to create the base image. :)
>
> Since when can you use autopkgtest to create the base image? And how?

With autopkgtest-build-qemu(1):

       autopkgtest-build-qemu creates virtual machine images suitable
       for use with autopkgtest's QEMU runner autopkgtest-virt-qemu(1).

       Under the hood, it uses vmdb2(1) to create the images.

For example, I used:

    sudo autopkgtest-build-qemu unstable debian-sid-amd64-autopkgtest.qcow2

> The last time I talked with the autopkgtest maintainers about a feature like
> this, they were vehemently against adding any such functionality [1].

Maybe we're not talking about the same thing here...? It looks like
mpitt was saying that autopkgtest shouldn't be touching the image
*during* the test, but doesn't fundamentally object to *creating* images
*before* the test...

A.

-- 
Thousands of candles can be lit from a single candle
And the life of the candle will not be shortened.
Happiness never decreases by being shared.
                         - Buddha

Message #38 received at 909847-close@bugs.debian.org (full text, mbox, reply):

From: Johannes 'josch' Schauer <josch@debian.org>

To: 909847-close@bugs.debian.org

Subject: Bug#909847: fixed in sbuild 0.78.0-1

Date: Wed, 09 Jan 2019 05:19:32 +0000

Source: sbuild
Source-Version: 0.78.0-1

We believe that the bug you reported is fixed in the latest version of
sbuild, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 909847@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Johannes 'josch' Schauer <josch@debian.org> (supplier of updated sbuild package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Wed, 09 Jan 2019 05:53:49 +0100
Source: sbuild
Binary: libsbuild-perl sbuild sbuild-debian-developer-setup buildd
Architecture: source
Version: 0.78.0-1
Distribution: unstable
Urgency: medium
Maintainer: sbuild maintainers <sbuild@packages.debian.org>
Changed-By: Johannes 'josch' Schauer <josch@debian.org>
Description:
 buildd     - Daemon for automatically building Debian binary packages from Deb
 libsbuild-perl - Library for building Debian binary packages from Debian sources
 sbuild     - Tool for building Debian binary packages from Debian sources
 sbuild-debian-developer-setup - Convenience script to set up an sbuild environment for Debian Dev
Closes: 887264 904968 905345 905346 905347 905513 909378 909847 911399 911979 916009 916924
Changes:
 sbuild (0.78.0-1) unstable; urgency=medium
 .
   * New upstream release.
   * remove debian/patches (have been applied upstream)
   * Add libc-dev and libstdc++-dev when cross compiling (closes: #905346)
   * default to --no-arch-all for cross builds (closes: #905347)
   * Set build profiles cross and nocheck by default when cross building
     (closes: #905345)
   * bin/sbuild-createchroot: allow an empty lost+found directory in the target
     directory (closes: #909378)
   * add --no-source-only-changes option (closes: #904968)
   * sbuild-createchroot: Do not check for empty directory if --setup-only
     option is used (closes: #916009)
   * do not check debian/tests/control when running autopkgtest (closes:
     #916924)
   * add sbuild and BUILD_USER if they didn't exist yet (closes: #911979)
   * let --append-to-version imply --no-arch-all like it's the case for
     --make-binNMU (closes: #911399)
   * allow chroots with nothing more but Essenital:yes packages, apt and their
     hard dependencies and create missing users and groups as needed
     (closes: #909847)
   * run wrap-and-sort
   * let sbuild Suggests e2fsprogs for /usr/share/sbuild/create-chroot (closes:
     #887264)
   * remove /var/log/sbuild-update-all.log if sbuild-debian-developer-setup
     gets purged (closes: #905513)
   * bump debhelper compat to 11
   * debian/control: bump Standards-Version to 4.3.0 (no changes)
Checksums-Sha1:
 9c78f76a4f22aeb87b9382b7831e32cd6701bdc3 2455 sbuild_0.78.0-1.dsc
 6bb97a2f1c01ce6a8e828ed7c8edca94d5ea41fb 200556 sbuild_0.78.0.orig.tar.xz
 389b77e041a448646e7e67337e17bd60aa81d258 51000 sbuild_0.78.0-1.debian.tar.xz
 94822dc44f83deb36257bae2244c2654c825eed9 6346 sbuild_0.78.0-1_amd64.buildinfo
Checksums-Sha256:
 a10a467e2a282e991ed6c2bcb66b1f83c639afa4d674727b39debec43a618710 2455 sbuild_0.78.0-1.dsc
 2847de05b8c226f132da230d9068ca3d0d850f280d6c5e17a014fe8124ba466c 200556 sbuild_0.78.0.orig.tar.xz
 41289346371fe44e06a8b2bfb4ea5ac9f1046a5073b0c78d13d04cebf829c65e 51000 sbuild_0.78.0-1.debian.tar.xz
 8a6063f4dcee8ca07e7bc875bcf9a3386501a405f335f8bf34e87818ed0f7ead 6346 sbuild_0.78.0-1_amd64.buildinfo
Files:
 ee55cf349331f10238f24cb51538556e 2455 devel optional sbuild_0.78.0-1.dsc
 d227ee6adea5e8fa0660d97e8203b2f4 200556 devel optional sbuild_0.78.0.orig.tar.xz
 9f1ee90fa7d35c768aeeb24d23303630 51000 devel optional sbuild_0.78.0-1.debian.tar.xz
 110cdbbff84c9f9472e12a84d2010a92 6346 devel optional sbuild_0.78.0-1_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEElFhU6KL81LF4wVq58sulx4+9g+EFAlw1ftEACgkQ8sulx4+9
g+EcBBAAnPn1KSLxqCvWwhRi+7SGmqk3g1TsoQ4PeYuLRUUowrzyNdALy836RiSF
lkGNBR/wKfou5XaEzq1stnRJ0cp2YWP/O59akOWvDjvQj9VzuuvTZpQ52WEsiUq2
7WgVHfP0bPTcTiBSrv29KplQOUctjNmcqPHXbiQhAzcP4+bNIRdu3m24YS0rufvi
GPdfPU5aUjmm7Im7Dj3F5Tdyh3TPTp2bNuoCHZihFmta9zx16ORoLLrCeZB8ovt8
RV/hgjN80y1B7/D/ENFPgjn8lcqBLekHZaIC2N3kNf9hHKEUowjQZ1+fxaGGAGb+
GkndOxAY9v3ns/MQ5wDfsVcjG2F3z6qCVGt8boEk29vi20wChsVUiW3P4fJmFQpo
Mq/gHwLoqCFYa5c4rJsmUruMvQ8zhIWbAGJf4GjW4EUXl8Hgal6A7Gc7dndhfd2s
A2JKTZlR1bN3CM95A4TaxepFIAXUdj3h0tgYIc3RpgI9eb9YmkBWOkZ3guOPIkhu
M372UiCaUT3aW5ugotuk9Rpm1BEyqpngdSB9htn+La+go46uAj0P7lxYr1iKj26r
7+J8+NgTGbRl+U+SFa9W/Tp2KAAFv6ucTKND0wDuAnvul9wrPm1qnfdaH8AzRdGx
Mt07Il/iZjHxXKjxzft4piUefjofaKBqkqQRsbt+W+rPM/ovx9g=
=3U/5
-----END PGP SIGNATURE-----

Message #43 received at 911979-close@bugs.debian.org (full text, mbox, reply):

From: Johannes 'josch' Schauer <josch@debian.org>

To: 911979-close@bugs.debian.org

Subject: Bug#911979: fixed in sbuild 0.78.0-1

Date: Wed, 09 Jan 2019 05:19:32 +0000

Source: sbuild
Source-Version: 0.78.0-1

We believe that the bug you reported is fixed in the latest version of
sbuild, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 911979@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Johannes 'josch' Schauer <josch@debian.org> (supplier of updated sbuild package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Wed, 09 Jan 2019 05:53:49 +0100
Source: sbuild
Binary: libsbuild-perl sbuild sbuild-debian-developer-setup buildd
Architecture: source
Version: 0.78.0-1
Distribution: unstable
Urgency: medium
Maintainer: sbuild maintainers <sbuild@packages.debian.org>
Changed-By: Johannes 'josch' Schauer <josch@debian.org>
Description:
 buildd     - Daemon for automatically building Debian binary packages from Deb
 libsbuild-perl - Library for building Debian binary packages from Debian sources
 sbuild     - Tool for building Debian binary packages from Debian sources
 sbuild-debian-developer-setup - Convenience script to set up an sbuild environment for Debian Dev
Closes: 887264 904968 905345 905346 905347 905513 909378 909847 911399 911979 916009 916924
Changes:
 sbuild (0.78.0-1) unstable; urgency=medium
 .
   * New upstream release.
   * remove debian/patches (have been applied upstream)
   * Add libc-dev and libstdc++-dev when cross compiling (closes: #905346)
   * default to --no-arch-all for cross builds (closes: #905347)
   * Set build profiles cross and nocheck by default when cross building
     (closes: #905345)
   * bin/sbuild-createchroot: allow an empty lost+found directory in the target
     directory (closes: #909378)
   * add --no-source-only-changes option (closes: #904968)
   * sbuild-createchroot: Do not check for empty directory if --setup-only
     option is used (closes: #916009)
   * do not check debian/tests/control when running autopkgtest (closes:
     #916924)
   * add sbuild and BUILD_USER if they didn't exist yet (closes: #911979)
   * let --append-to-version imply --no-arch-all like it's the case for
     --make-binNMU (closes: #911399)
   * allow chroots with nothing more but Essenital:yes packages, apt and their
     hard dependencies and create missing users and groups as needed
     (closes: #909847)
   * run wrap-and-sort
   * let sbuild Suggests e2fsprogs for /usr/share/sbuild/create-chroot (closes:
     #887264)
   * remove /var/log/sbuild-update-all.log if sbuild-debian-developer-setup
     gets purged (closes: #905513)
   * bump debhelper compat to 11
   * debian/control: bump Standards-Version to 4.3.0 (no changes)
Checksums-Sha1:
 9c78f76a4f22aeb87b9382b7831e32cd6701bdc3 2455 sbuild_0.78.0-1.dsc
 6bb97a2f1c01ce6a8e828ed7c8edca94d5ea41fb 200556 sbuild_0.78.0.orig.tar.xz
 389b77e041a448646e7e67337e17bd60aa81d258 51000 sbuild_0.78.0-1.debian.tar.xz
 94822dc44f83deb36257bae2244c2654c825eed9 6346 sbuild_0.78.0-1_amd64.buildinfo
Checksums-Sha256:
 a10a467e2a282e991ed6c2bcb66b1f83c639afa4d674727b39debec43a618710 2455 sbuild_0.78.0-1.dsc
 2847de05b8c226f132da230d9068ca3d0d850f280d6c5e17a014fe8124ba466c 200556 sbuild_0.78.0.orig.tar.xz
 41289346371fe44e06a8b2bfb4ea5ac9f1046a5073b0c78d13d04cebf829c65e 51000 sbuild_0.78.0-1.debian.tar.xz
 8a6063f4dcee8ca07e7bc875bcf9a3386501a405f335f8bf34e87818ed0f7ead 6346 sbuild_0.78.0-1_amd64.buildinfo
Files:
 ee55cf349331f10238f24cb51538556e 2455 devel optional sbuild_0.78.0-1.dsc
 d227ee6adea5e8fa0660d97e8203b2f4 200556 devel optional sbuild_0.78.0.orig.tar.xz
 9f1ee90fa7d35c768aeeb24d23303630 51000 devel optional sbuild_0.78.0-1.debian.tar.xz
 110cdbbff84c9f9472e12a84d2010a92 6346 devel optional sbuild_0.78.0-1_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEElFhU6KL81LF4wVq58sulx4+9g+EFAlw1ftEACgkQ8sulx4+9
g+EcBBAAnPn1KSLxqCvWwhRi+7SGmqk3g1TsoQ4PeYuLRUUowrzyNdALy836RiSF
lkGNBR/wKfou5XaEzq1stnRJ0cp2YWP/O59akOWvDjvQj9VzuuvTZpQ52WEsiUq2
7WgVHfP0bPTcTiBSrv29KplQOUctjNmcqPHXbiQhAzcP4+bNIRdu3m24YS0rufvi
GPdfPU5aUjmm7Im7Dj3F5Tdyh3TPTp2bNuoCHZihFmta9zx16ORoLLrCeZB8ovt8
RV/hgjN80y1B7/D/ENFPgjn8lcqBLekHZaIC2N3kNf9hHKEUowjQZ1+fxaGGAGb+
GkndOxAY9v3ns/MQ5wDfsVcjG2F3z6qCVGt8boEk29vi20wChsVUiW3P4fJmFQpo
Mq/gHwLoqCFYa5c4rJsmUruMvQ8zhIWbAGJf4GjW4EUXl8Hgal6A7Gc7dndhfd2s
A2JKTZlR1bN3CM95A4TaxepFIAXUdj3h0tgYIc3RpgI9eb9YmkBWOkZ3guOPIkhu
M372UiCaUT3aW5ugotuk9Rpm1BEyqpngdSB9htn+La+go46uAj0P7lxYr1iKj26r
7+J8+NgTGbRl+U+SFa9W/Tp2KAAFv6ucTKND0wDuAnvul9wrPm1qnfdaH8AzRdGx
Mt07Il/iZjHxXKjxzft4piUefjofaKBqkqQRsbt+W+rPM/ovx9g=
=3U/5
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.