Hi Vladimir, Quoting Vladimir Petko (2024-11-14 00:07:13) > Dear Maintainer, > > Fakechroot in Ubuntu is affected by[1] due to FORTFY_SOURCE enabled[2]. > The autopkgtests fails due to the public key not known[3]: > 85s Get:1 http://deb.debian.org/debian unstable InRelease [202 kB] > 85s Err:1 http://deb.debian.org/debian unstable InRelease > 85s The following signatures couldn't be verified because the public key is > not available: NO_PUBKEY 0E98404D386FA1D9 NO_PUBKEY 6ED0E7B82643E131 > 85s Reading package lists... > 85s W: GPG error: http://deb.debian.org/debian unstable InRelease: The > following signatures couldn't be verified because the public key is not > available: NO_PUBKEY 0E98404D386FA1D9 NO_PUBKEY 6ED0E7B82643E131 > 85s E: The repository 'http://deb.debian.org/debian unstable InRelease' is > not > signed. > 85s E: apt-get update --error-on=any -oAPT::Status-Fd=<$fd> -oDpkg::Use- > Pty=false failed > 85s W: hooklistener errored out: E: received eof on socket > > In Ubuntu, the attached patch was applied to achieve the following: > > * d/p/0001-properly-pass-buffer.patch: apply proposed patch > to resolve the buffer overflow (LP: #2087810). > * d/t/{control, mmdebstrap}: fix autopkgtest - use > debian-archive-keyring for mmdebstrap keyring arguments. > > > Thanks for considering the patch.
thank you for working to minimize the difference between Ubuntu and Debian.
>From a first glance your patch looks okay, thank you!
What I'm wondering about and what I'd like you to check for me is, if
mmdebstrap really needs the --keyring argument to create Debian unstable
chroots in Ubuntu even though the debian-archive-keyring was installed. Does
that really fail? If yes, could you give me the output of the following from a
Ubuntu system that has debian-archive-keyring installed:
mmdebstrap --variant=apt --verbose unstable /dev/null
Thanks!
cheers, josch
signature.asc
Description: signature
