Archive signature for sid broken?

Hello developers, is the signature for sid broken? When I do 'apt-get update', it complains about an invalid key, but that key mentions bullseye, not sid. A similar error shows for 'debootstrap sid sid' With kind regards, Roland Clobus --- Get:4 http://deb.debian.org/debian unstable InRelease

Reviving schroot as used by sbuild

Hi, sbuild is our primary tool for constructing a build environment to build Debian packages. It is used on all buildds and for a long time, the backend used with sbuild has always been schroot. More recently, a number of buildds have been moved away from schroot towards --chroot-mode=unshare than

Re: Reviving schroot as used by sbuild

Hi, Quoting Helmut Grohne (2024-06-25 10:16:20) > In this work, limitations with --chroot-mode=unshare became apparent and that > lead to Johannes, Jochen and me sitting down in Berlin pondering ideas on how > to improve the situation. That is a longer story, but eventually Timo Röhling > asked th

Re: Mini-DebConf in Cambridge, UK - October 10-13 2024

On Tue, Jun 25, 2024 at 08:39:51AM +0530, Nilesh Patra wrote: > On Mon, Jun 24, 2024 at 12:32:59PM +0100, Steve McIntyre wrote: > > On Mon, Jun 24, 2024 at 12:18:56PM +0200, somebody *claiming* to be Luna > > Jernberg wrote: > > > > > > > > Just to be 100% clear, that mail didn't come from Luna

Re: Mini-DebConf in Cambridge, UK - October 10-13 2024

Hi, > Perhaps our policies need to evolve to expect (or require?) > cryptographic signatures from DDs in mailing list discussion. We may > eventually reach a point where AI can fabricate those as well, but that > seems to not be possible yet. For that it would need to break the cryptographic key,

Re: Mini-DebConf in Cambridge, UK - October 10-13 2024

On Tue, Jun 25, 2024 at 06:14:54AM -0400, Roberto C. Sánchez wrote: > > The style of writing mail - everything in one line, CCing several lists is > > similar to how Luna writes it too. Freaky. > > > AI can already generate audio and video that convincingly imitate real > people. Why not the same

Re: Mini-DebConf in Cambridge, UK - October 10-13 2024

On 25.06.2024 ÖS 1:54, Andrey Rakhmatullin wrote: On Tue, Jun 25, 2024 at 06:14:54AM -0400, Roberto C. Sánchez wrote: The style of writing mail - everything in one line, CCing several lists is similar to how Luna writes it too. Freaky. AI can already generate audio and video that convincingl

Re: Archive signature for sid broken?

Le mar. 25 juin 2024 à 10:11, Roland Clobus a écrit : > Hello developers, > > is the signature for sid broken? > When I do 'apt-get update', it complains about an invalid key, but that > key mentions bullseye, not sid. > > A similar error shows for 'debootstrap sid sid' > If you use a apt-cacher

Re: Archive signature for sid broken?

Hello Jérémy, On 25/06/2024 13:00, Jérémy Lal wrote: Le mar. 25 juin 2024 à 10:11, Roland Clobus > a écrit : Hello developers, is the signature for sid broken? When I do 'apt-get update', it complains about an invalid key, but that key mentions bullse

Re: Reviving schroot as used by sbuild

On Tue, 25 Jun 2024 at 10:16:20 +0200, Helmut Grohne wrote: > In this work, limitations with --chroot-mode=unshare became apparent and > that lead to Johannes, Jochen and me sitting down in Berlin pondering > ideas on how to improve the situation. That is a longer story, but > eventually Timo Röhli

Re: Reviving schroot as used by sbuild

On Tue, Jun 25, 2024 at 02:02:11PM +0100, Simon McVittie wrote: > Could we use a container framework that is also used outside the Debian > bubble, rather than writing our own from first principles every time, and > ending up with a single-maintainer project being load-bearing for Debian > *again*?

Re: Reviving schroot as used by sbuild

On Tue, Jun 25, 2024 at 02:02:11PM +0100, Simon McVittie wrote: > > In this work, limitations with --chroot-mode=unshare became apparent and > > that lead to Johannes, Jochen and me sitting down in Berlin pondering > > ideas on how to improve the situation. That is a longer story, but > > eventuall

Re: Reviving schroot as used by sbuild

On Tue, Jun 25, 2024 at 02:02:11PM +0100, Simon McVittie wrote: > On Tue, 25 Jun 2024 at 10:16:20 +0200, Helmut Grohne wrote: > > In this work, limitations with --chroot-mode=unshare became apparent and > > that lead to Johannes, Jochen and me sitting down in Berlin pondering > > ideas on how to im

Re: Reviving schroot as used by sbuild

Simon McVittie writes: > Persisting a container root filesystem between multiple operations comes > with some serious correctness issues if there are "hooks" that can modify > it destructively on each operation: see > and . As a res

Re: Reviving schroot as used by sbuild

Hi! On Tue, 2024-06-25 at 09:32:21 -0700, Russ Allbery wrote: > Simon McVittie writes: > > Persisting a container root filesystem between multiple operations comes > > with some serious correctness issues if there are "hooks" that can modify > > it destructively on each operation: see

Re: Reviving schroot as used by sbuild

On Tue, 25 Jun 2024 at 09:32:21 -0700, Russ Allbery wrote: > Simon McVittie writes: > > I think the > > only model that should be used in new systems is to have some concept of > > a session (like schroot type=file, but unlike schroot type=directory) > > I'm not entirely sure that I'm following t

Re: Reviving schroot as used by sbuild

Hi Simon, On Tue, Jun 25, 2024 at 02:02:11PM +0100, Simon McVittie wrote: > Could we use a container framework that is also used outside the Debian > bubble, rather than writing our own from first principles every time, and > ending up with a single-maintainer project being load-bearing for Debian

Re: Reviving schroot as used by sbuild

On Jun 25, Guillem Jover wrote: > I manage my chroots with schroot (but not via sbuild, for dog fooding > purposes :), and use type=directory and union-type=overlay so that I > get a fast and persistent base, independent of the underlying filesystem, > with fresh instances per session. (You can a

Re: Reviving schroot as used by sbuild

Guillem Jover writes: > I manage my chroots with schroot (but not via sbuild, for dog fooding > purposes :), and use type=directory and union-type=overlay so that I get > a fast and persistent base, independent of the underlying filesystem, > with fresh instances per session. (You can access the

Re: Reviving schroot as used by sbuild

On Tue, Jun 25, 2024 at 10:24:12AM -0700, Russ Allbery wrote: > Guillem Jover writes: > > > I manage my chroots with schroot (but not via sbuild, for dog fooding > > purposes :), and use type=directory and union-type=overlay so that I get > > a fast and persistent base, independent of the underly

Re: Reviving schroot as used by sbuild

PICCA Frederic-Emmanuel writes: >> Ah, thank you, I didn't realize that existed. That sounds like a nice >> generalization of the file system snapshot approach. > I think that this how the > sbuild-debian-developer-setup > script, setup chroots Yeah, I think all that my contribution to this

Re: Reviving schroot as used by sbuild

> Ah, thank you, I didn't realize that existed. That sounds like a nice > generalization of the file system snapshot approach. I think that this how the sbuild-debian-developer-setup script, setup chroots Fred

Re: Reviving schroot as used by sbuild

On Tue, Jun 25, 2024 at 7:13 AM Helmut Grohne wrote: > > Hi, > > sbuild is our primary tool for constructing a build environment to build > Debian packages. It is used on all buildds and for a long time, the > backend used with sbuild has always been schroot. More recently, a > number of buildds h

autopkgtest + podman user experience (Was: Re: Reviving schroot as used by sbuild)

On 25/06/24 18:55, Helmut Grohne wrote: For systemd-as-pid-1 specifically, `autopkgtest-build-podman --init=systemd` and `autopkgtest-virt-podman --init` demonstrate how this can be done, and last time I tried, it was possible to run them unprivileged (other than needing access to the setuid newu

Re: Reviving schroot as used by sbuild

Hi On 25-06-2024 6:55 p.m., Helmut Grohne wrote: This is very cool. Running autopkgtests in system containers without being root (or incus-admin) very much is what I'd like to do. And it's much better if I don't have to write my own container framework for doing it. I couldn't get it to work loc

Re: autopkgtest + podman user experience (Was: Re: Reviving schroot as used by sbuild)

Hi. On 25-06-2024 8:18 p.m., Gioele Barabucci wrote: I'd like to take this chance to suggest, instead of writing more documentation, changing the autopkgtest packaging so that it is split into various per-backend packages, each of which provides a ready-to-go pre-configured environment. See