debootstrap: don't symlink /proc when in docker

[Eicke Herbertz]

Hi,

I recently created a merge request[1] on salsa.debian.org, cleaning up 
the /proc handling in docker after a patch in 1.0.104 changed timestamps 
when building reproducible Debian images (also, debootstrap currently 
works around it's own workarounds).


I'm just writing this mail because I'm unsure if that's the correct way 
of contributing to debootstrap or if it's better "initiated" via mail.
Please don't feel compelled by this, I'm not impatient, just unsure if I 
hit the correct path of communication at all.


Kind regards,
Eicke Herbertz

[1] https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/70

Re: 11.4 planning

[Mark Hymers]

On Fri, 17, Jun, 2022 at 08:31:23PM +0100, Adam D. Barratt spoke thus..
> Hi,
> 
> We're (again) running behind in getting the next point release for
> bullseye sorted, and I know we're about to run into the Deb{Camp,Conf}
> period. I think the possible dates that make sense are:
> 
> - July 2nd (means freezing next weekend, but so be it)
> - July 9th

I can do the 2nd but not the 9th.

Mark

-- 
Mark Hymers 

Re: 11.4 planning

[Cyril Brulebois]

Adam D. Barratt  (2022-06-17):
> - July 2nd (means freezing next weekend, but so be it)
> - July 9th

Both would be fine d-i wise.


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


signature.asc
Description: PGP signature

Re: 11.4 planning

[Steve McIntyre]

Hey Adam!

On Fri, Jun 17, 2022 at 08:31:23PM +0100, Adam Barratt wrote:
>
>We're (again) running behind in getting the next point release for
>bullseye sorted, and I know we're about to run into the Deb{Camp,Conf}
>period. I think the possible dates that make sense are:
>
>- July 2nd (means freezing next weekend, but so be it)
>- July 9th
>
>I think there's already a couple of things pending on KiBi's review
>list; I'll try and flag up any others as soon as I can.

Argh. I've got a few pertinent issues here:

 * I'm *really* busy over the next few weeks (work and debconf) which
   make things awkward for me to fit stuff in. :-/

 * IIRC this should also be another buster point release, possibly the
   last before it's dropped / passed over to LTS? Or are we thinking
   another one in August for Buster? Checking last year's dates, we
   released on Aug 14 so I'm thinking maybe we could/should push back
   that last point release into August. In that case, I'd be happier
   to do a bullseye-only point release in July. Neither of the dates
   you suggest are ideal for me (see above!), but under time pressure
   it's easier to cope with a single release rather than two.

 * We have some secure-boot related updates that have not yet filtered
   through for buster and bullseye. We're working on stuff for bullseye
   now, but buster may take a little bit longer yet. I'd prefer the
   9th if possible.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"The whole problem with the world is that fools and fanatics are
 always so certain of themselves, and wiser people so full of doubts."
   -- Bertrand Russell

Re: 11.4 planning

[Ansgar]

Hi,

On Fri, 2022-06-17 at 20:31 +0100, Adam D. Barratt wrote:
> - July 2nd (means freezing next weekend, but so be it)
> - July 9th

Both would work for me.

Ansgar

Re: 11.4 planning

[Adam D. Barratt]

Hi Steve,

On Sun, 2022-06-19 at 18:04 +0100, Steve McIntyre wrote:
> Hey Adam!
> 
> On Fri, Jun 17, 2022 at 08:31:23PM +0100, Adam Barratt wrote:
> > We're (again) running behind in getting the next point release for
> > bullseye sorted, and I know we're about to run into the
> > Deb{Camp,Conf}
> > period. I think the possible dates that make sense are:
> > 
> > - July 2nd (means freezing next weekend, but so be it)
> > - July 9th
> > 
> > I think there's already a couple of things pending on KiBi's review
> > list; I'll try and flag up any others as soon as I can.
> 
> Argh. I've got a few pertinent issues here:
> 
>  * I'm *really* busy over the next few weeks (work and debconf) which
>make things awkward for me to fit stuff in. :-/
> 

ACK. Debconf, and people being away for it again this year, rather
snuck up on me. TBH, June rather snuck up on me. :-(

>  * IIRC this should also be another buster point release, possibly
> the
>last before it's dropped / passed over to LTS? Or are we thinking
>another one in August for Buster? Checking last year's dates, we
>released on Aug 14 so I'm thinking maybe we could/should push back
>that last point release into August. In that case, I'd be happier
>to do a bullseye-only point release in July. Neither of the dates
>you suggest are ideal for me (see above!), but under time pressure
>it's easier to cope with a single release rather than two.
> 

stretch's LTS finishes at the end of June, and there's been some
initial discussion about how/when to handle the switchover for buster,
but it's not been concluded yet.

I'm not sure I have the bandwidth to be organising two point releases
over the next couple of weeks either, if I'm completely honest.

>  * We have some secure-boot related updates that have not yet
> filtered
>through for buster and bullseye. We're working on stuff for
> bullseye
>now, but buster may take a little bit longer yet. I'd prefer the
>9th if possible.
> 

ACK, thanks for the note / reminder.

Regards,

Adam