Re: Reviving schroot as used by sbuild

On 25.06.24 15:02, Simon McVittie wrote: I have to ask: 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*? I had hoped

Re: Reviving schroot as used by sbuild

Hi Simon, Thanks for having taken the time to do another extensive writeup. Much appreciated. On Wed, Jun 26, 2024 at 06:11:09PM +0100, Simon McVittie wrote: > On Tue, 25 Jun 2024 at 18:55:45 +0200, Helmut Grohne wrote: > > The main difference to how everyone else does this is that in a typical >

BIMI verified email logo for @debian.org addresses

Hi, [BIMI], or Brand Indicators for Message Identification, is a specification to let supporting email clients show a brand's logo next to verified email domains. It would be great to have the Debian logo shown next to @debian.org addresses. An email service provider implements it by implementing

Re: Reviving schroot as used by sbuild

On Thu, Jun 27, 2024 at 7:45 AM Helmut Grohne wrote: > Please allow for another podman question (and more people than Simon > know the answer). Every time I run a podman container (e.g. when I run > autopkgtest) my ~/.local/share/containers grows. I think autopkgtest > manages to clean up in the

Re: BIMI verified email logo for @debian.org addresses

On Thu, Jun 27, 2024 at 07:29:45PM +0800, Blair Noctis wrote: > Hi, > > [BIMI], or Brand Indicators for Message Identification, is a specification to > let supporting email clients show a brand's logo next to verified email > domains. > It would be great to have the Debian logo shown next to @deb

Re: BIMI verified email logo for @debian.org addresses

On Thu, 27 Jun 2024 17:19:11 +0500, Andrey Rakhmatullin wrote: > On Thu, Jun 27, 2024 at 07:29:45PM +0800, Blair Noctis wrote: > > [BIMI], or Brand Indicators for Message Identification, is a specification > > to > > let supporting email clients show a brand's logo next to verified email > > dom

Re: Reviving schroot as used by sbuild

On Thu, 27 Jun 2024 at 11:46:51 +0200, Helmut Grohne wrote: > I am concerned about behavioural differences due to the reimplementation > from first principles aspect though. Jochen and Aurelien will know more > here, but I think we had a fair number of ftbfs due to such differences. > None of them

Re: BIMI verified email logo for @debian.org addresses

* gregor herrmann [2024-06-27 14:50]: Hanno also gave a talk at the MiniDebConf in Berlin earlier this year: https://berlin2024.mini.debconf.org/talks/17-breaking-dkim-and-bimi-with-the-2008-debian-openssl-bug/ Video at https://meetings-archive.debian.net/pub/debian-meetings/2024/MiniDebConf-Be

Re: Reviving schroot as used by sbuild

Hi, Quoting Simon McVittie (2024-06-27 15:59:01) > On Thu, 27 Jun 2024 at 11:46:51 +0200, Helmut Grohne wrote: > > I don't quite understand the need for a Dockerfile here. I suspect that > > this is the obvious way that works reliably, but my impression was that > > using podman import would be ea

Re: Reviving schroot as used by sbuild

On Thu, 27 Jun 2024 at 17:26:20 +0200, Johannes Schauer Marin Rodrigues wrote: > But, if everybody is so excited about this, where are the sbuild contributors > implementing this? I'm sorry, consider it added it to my list. As usual, there's no guarantee that I will get there within my lifetime, b

Re: Reviving schroot as used by sbuild

On Wed, 26 Jun 2024 at 18:05:15 -0400, Reinhard Tartler wrote: > I imagine that one could whip up some kind of wrapper > that is building a container either from a tarball created via mmboostrap or > similar > using buildah, have it install all necessary build dependencies, and then use > podman to

Re: Reviving schroot as used by sbuild

Simon, Quoting Simon McVittie (2024-06-27 19:16:54) > On Thu, 27 Jun 2024 at 17:26:20 +0200, Johannes Schauer Marin Rodrigues wrote: > > But, if everybody is so excited about this, where are the sbuild > > contributors > > implementing this? > > I'm sorry, consider it added it to my list. As usu

Builds that pass locally but fail on sbuild? (Re: Reviving schroot as used by sbuild)

Hi Simon! > There are lots of options for doing this, some of which are listed in > . > > All of these have the same problem as cowbuilder, pbuilder, and any > other solution that is not sbuild + schroot: it isn't (currently) what > the

Bug#1074405: ITP: fibocom-pc-services -- Services to support WWAN modules manufactured by Fibocom Wireless Inc.

Package: wnpp Severity: wishlist Owner: Kai-Chuan Hsieh X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: fibocom-pc-services Version : 1.0.10 Upstream Author : zhaoziqi * URL : https://github.com/fibocom-pc/linux_apps_opensource * License : GPL, MIT