Bug#930856: autopkgtest-build-qemu: captures something from host

[Dmitry Bogatov]

control: close -1

[2019-06-30 10:13] Bastian Blank 
>
> part   text/plain 687
> On Sat, Jun 29, 2019 at 04:44:32PM +0200, Bastian Blank wrote:
> > On Sat, Jun 29, 2019 at 02:25:55PM +, Dmitry Bogatov wrote:
> > > Note that APT tries to use Devuan keyring to validate Debian release and
> > > fail. How does `debootstrap' decides, which keyring to use?
> > "dpkg -s debootstrap"?  How did that keyring get on the system in the
> > first place?
>
> Devuan includes a patched version of debootstrap.  See
> https://pkginfo.devuan.org/stage/ascii/ascii/debootstrap_1.0.89+devuan2.1.html

That was the cause. My mistake, I forgot to check version of
debootstrap.

Sorry for noise.
-- 
Note, that I send and fetch email in batch, once in a few days.
Please, mention in body of your reply when you add or remove recepients.

Bug#930856: autopkgtest-build-qemu: captures something from host

[Bastian Blank]

On Sat, Jun 29, 2019 at 04:44:32PM +0200, Bastian Blank wrote:
> On Sat, Jun 29, 2019 at 02:25:55PM +, Dmitry Bogatov wrote:
> > Note that APT tries to use Devuan keyring to validate Debian release and
> > fail. How does `debootstrap' decides, which keyring to use?
> "dpkg -s debootstrap"?  How did that keyring get on the system in the
> first place?

Devuan includes a patched version of debootstrap.  See
https://pkginfo.devuan.org/stage/ascii/ascii/debootstrap_1.0.89+devuan2.1.html

Please show that you use an unpatched version on a system without a
Devuan key.

Bastian

-- 
Vulcans believe peace should not depend on force.
-- Amanda, "Journey to Babel", stardate 3842.3

Bug#930856: autopkgtest-build-qemu: captures something from host

[Cyril Brulebois]

Hi,

Dmitry Bogatov  (2019-06-29):
> [ After futher investigation, this command fails with same error directly,
>  without autopkgtest, so reassigning ]
> 
> control: reassing -1 debootstrap
> control: retitle -1 debootstrap uses wrong keyring
> 
> Dear maintainer of debootstrap, I can't create chroot due following error:
> 
>   # debootstrap --variant - unstable /tmp/foo.dir http://deb.debian.org
>   I: Checking Release signature
>   E: Release signed by unknown key (key id 04EE7237B7D453EC)
>  The specified keyring /usr/share/keyrings/devuan-archive-keyring.gpg may 
> be incorrect or out of date.
>  You can find the latest Debian release key at 
> https://ftp-master.debian.org/keys.html
> 
> Note that APT tries to use Devuan keyring to validate Debian release and
> fail. How does `debootstrap' decides, which keyring to use?

What debootstrap version is that? And what distribution is it?

In a sid chroot I'm getting this:

(sid-amd64-devel)kibi@armor:/tmp$ sudo debootstrap --variant - unstable 
/tmp/foo.dir http://deb.debian.org
I: Target architecture can be executed
I: Retrieving InRelease 
I: Retrieving Release 
E: Failed getting release file http://deb.debian.org/dists/unstable/Release

which is sensible because there's a missing /debian directory.

With that fixed:

(sid-amd64-devel)kibi@armor:/tmp$ sudo debootstrap --variant - unstable 
/tmp/foo.dir http://deb.debian.org/debian
I: Target architecture can be executed
I: Retrieving InRelease 
I: Checking Release signature
I: Valid Release signature (key id 16E90B3FDF65EDE3AA7F323C04EE7237B7D453EC)
I: Retrieving Packages 
I: Validating Packages 
I: Resolving dependencies of required packages...
[…]

> I am aware about --keyring option, original bug was about
> `autopkgtest-build-qemu', which invokes debootstrap through several
> layers and does not allow passing additional arguments to `debootstrap'.

There's no devuan-archive-keyring.gpg in Debian anyway, so I'd suggest
filing this issue with your actual vendor.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#930856: autopkgtest-build-qemu: captures something from host

[Bastian Blank]

On Sat, Jun 29, 2019 at 02:25:55PM +, Dmitry Bogatov wrote:
> Note that APT tries to use Devuan keyring to validate Debian release and
> fail. How does `debootstrap' decides, which keyring to use?

"dpkg -s debootstrap"?  How did that keyring get on the system in the
first place?

Bastian

-- 
Violence in reality is quite different from theory.
-- Spock, "The Cloud Minders", stardate 5818.4

Bug#930856: autopkgtest-build-qemu: captures something from host

[Dmitry Bogatov]

[ After futher investigation, this command fails with same error directly,
 without autopkgtest, so reassigning ]

control: reassing -1 debootstrap
control: retitle -1 debootstrap uses wrong keyring

Dear maintainer of debootstrap, I can't create chroot due following error:

  # debootstrap --variant - unstable /tmp/foo.dir http://deb.debian.org
  I: Checking Release signature
  E: Release signed by unknown key (key id 04EE7237B7D453EC)
 The specified keyring /usr/share/keyrings/devuan-archive-keyring.gpg may 
be incorrect or out of date.
 You can find the latest Debian release key at 
https://ftp-master.debian.org/keys.html

Note that APT tries to use Devuan keyring to validate Debian release and
fail. How does `debootstrap' decides, which keyring to use?

I am aware about --keyring option, original bug was about
`autopkgtest-build-qemu', which invokes debootstrap through several
layers and does not allow passing additional arguments to `debootstrap'.
-- 
Note, that I send and fetch email in batch, once in a few days.
Please, mention in body of your reply when you add or remove recepients.

Bug#930856: autopkgtest-build-qemu: captures something from host

[Dmitry Bogatov]

Package: autopkgtest
Version: 5.10
Severity: normal

Dear Maintainer,

I fail to create qemu image:

(ins).. sudo autopkgtest-build-qemu unstable debian-unstable
Load spec file /tmp/tmp.MVjau2ZRda
Exec: ['qemu-img', 'create', '-f', 'raw', 'debian-unstable.raw', '20G']
Exec: ['parted', '-s', 'debian-unstable.raw', 'mklabel', 'msdos']
Exec: ['parted', '-m', 'debian-unstable.raw', 'print']
Exec: ['parted', '-s', 'debian-unstable.raw', 'mkpart', 'primary', 
'ext2', '0%', '100%']
Exec: ['kpartx', '-asv', 'debian-unstable.raw']
remembering /dev/mapper/loop0p1 as root
Exec: ['/sbin/mkfs', '-t', 'ext4', '/dev/mapper/loop0p1']
Exec: ['mount', '/dev/mapper/loop0p1', '/tmp/tmpybhuhyix']
Exec: ['debootstrap', '--variant', '-', 'unstable', '/tmp/tmpybhuhyix', 
'http://deb.debian.org/debian']
ERROR: Command failed: debootstrap --variant - unstable 
/tmp/tmpybhuhyix http://deb.debian.org/debian
b"W: Cannot check Release signature; keyring file not available 
/usr/share/keyrings/devuan-archive-keyring.gpg\nI
: Retrieving InRelease \nI: Retrieving Packages \nI: Validating 
Packages \nI: Resolving dependencies of required 
packages...\nI: Resolving dependencies of base packages...\nI: Checking 
component main on http://deb.debian.org/d
ebian...\nE: Couldn't find these debs: devuan-keyring devuan-baseconf\n"
b''
Something went wrong, cleaning up!
Exec: ['umount', '/tmp/tmpybhuhyix']
Exec: ['kpartx', '-dsv', 'debian-unstable.raw']

The host system actually uses Devuan repostiories and actually have
"devuan-keyring" package installed (alongside with "debian-keyring"),
but why debootstrap tries to validate Debian release with Devuan
keyring and how could I override this?
-- 
Note, that I send and fetch email in batch, once in a few days.


pgplOCZ5xx8Dd.pgp
Description: PGP signature