Bug#969084: buildd.d.o: please don't use a tainted buildenv

[Aurelien Jarno]

On 2020-09-10 14:17, Mattia Rizzolo wrote:
> On Thu, Sep 10, 2020 at 02:14:57PM +0200, Aurelien Jarno wrote:
> > On 2020-09-10 11:58, Holger Levsen wrote:
> > > Hi,
> > > 
> > > On Thu, Sep 10, 2020 at 01:45:31PM +0200, Mattia Rizzolo wrote:
> > > > On Wed, Sep 09, 2020 at 11:01:01AM +0200, Aurelien Jarno wrote:
> > > > > Well I would say that we have a solution but not yet the patch, but
> > > > > anyway I'll plan to work on writing a patch in the next days.
> > > > Oh, great!
> > > > thank you for being so quick!
> > > 
> > > indeed, thank you very much Aurelien!
> > > 
> > > fwiw, I also think it's fine to only have this for new
> > > unstable/bullseye/bookworm/... builds.
> > 
> > policy-rcd-declarative is used for bullseye and sid chroots. We do not
> > have bookworm chroots yet ;-)
> 
> do buildds use the sid chroots for experimental builds?

Yes, as the packages in experimental are not self-contained, so
experimental is basically just an overlay to sid. Said otherwise you
can't debootstrap experimental, just debootstrap sid and pickup
experimental packages.

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien at aurel32.net                 http://www.aurel32.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/reproducible-builds/attachments/20200910/5378d59a/attachment.sig>