Re: 11.4 planning

2022-06-19 Thread 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



Re: 11.4 planning

2022-06-19 Thread 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

2022-06-19 Thread 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

2022-06-19 Thread 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

2022-06-19 Thread 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

2022-06-19 Thread Andy Simpkins
On 17 June 2022 21:04:02 BST, "Andrew M.A. Cater"  wrote:
>On Fri, Jun 17, 2022 at 08:31:23PM +0100, Adam D. Barratt wrote:
>> 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
>> 
>
>Hi Adam
>
>I'll tag along with whatever the rest of the images team want to do :)
>Always fond of doing this.
>
>With every good wish,
>
>Andy Cater
>> 
>> Thanks,
>> 
>> Adam
>> 
>
>

Hi there.
I am afraid we can't help either weekend.  Isy has her school prom and a 
shooting eventone each weekend meaning she can't be there, and I have 
already committed as taxi...

If release were to go ahead either weekend I could drop in, but wouldn't be 
able to stay the distance.  Sorry

Andy



Bug#1011343: WISHLIST: Offical ALL-IN-ONE images?

2022-06-19 Thread Thomas Schmitt
Hi,

i tested merging of /firmware directories with barely sufficently
complete
  debian-11.0.0-amd64-DLBD-[12].iso.tmp
from aborted jigdo-lite runs.

All files which are reported as being only in CUSTOM(all-in-one) by
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011343#115
are listed by xorriso as present in the emerging ISO, of which i
suppressed the actual production out of storage space reasons.

So if the next diff between self-made CUSTOM(all-in-one) and merged.iso
shows again missing files in /firmware, i have to ask for full listings
of the /firmware trees in DLBD-1, DLBD-2, CUSTOM(all-in-one), and
merged.iso .

---
About my shortcuts with download and ISO non-production:

I waited with aborting jigdo-lite just long enough until the first
downloaded packages caused the inflation of the .template file
to .iso.tmp. The directory tree and the management files are then
already present, whereas the packages' content is mostly waiting for
being filled in.

Further i modified the xorriso run to end by
  -find /firmware -- -rollback_end
so that no ISO emerges but only the content of the planned /firmware
directory is shown before the program ends.

(I would go further. But the production of CUSTOM(all-in-one) via
debian-cd is out of my reach, given the section "ABOUT MIRROR" in message
#115. So the effort to complete the download and to produce a merged.iso
would bring no benefit for now.)


Have a nice day :)

Thomas