Re: Upcoming D-I Bookworm RC 4 and pseudo-RC 5

[Emanuele Rocca]

Hi,

On 2023-06-03 08:07, Cyril Brulebois wrote:
> Since there was good progress on the arm64 console thing (#1036952), and
> considering the current results of the investigation as to where vt102
> comes from, and why arm64 isn't quite the deciding factor (a busybox
> limitation instead), I'd be happy to consider getting an updated
> rootskel for migration before pseudo-RC 5 and 12.0.0. Such an upload
> would need to happen quickly though… (ema bcc'd, as possible uploader,
> no obligations though!).

I see that Samuel took care of the rootskel upload. Thanks!

  ema

Re: Upcoming D-I Bookworm RC 4 and pseudo-RC 5

[Samuel Thibault]

Cyril Brulebois, le sam. 03 juin 2023 20:07:05 +0200, a ecrit:
> Unless specifically requested, I don't plan on including the first two
> before Bookworm because we don't need it for release architectures. I
> /think/ hurd-i386 gets somewhat released from unstable, so that
> shouldn't matter…

Yes.

> not sure about ports architectures.

Ports don't have a testing either.

Samuel

Re: Upcoming D-I Bookworm RC 4 and pseudo-RC 5

[Cyril Brulebois]

Hi Holger,

Holger Wansing  (2023-06-03):
> Cyril Brulebois  wrote (Sat, 3 Jun 2023 20:07:05 +0200):
> > At the moment I've spotted three uploads:
> >  - apt-setup (1:0.183), for ports architectures.
> >  - preseed (1.118), for Hurd, even if the changelog is not quite verbose
> >about that part…
> >  - vte2.91 (0.70.5-1): new upstream (bugfix) release with no particular
> >bugfixes identified.
> 
> I have just uploaded grub-installer 1.194, which completes Croatian and
> Ukranian translation.
> Feel free to include it in bookworm, if possible.

Git looks good, hints in place (but I'll check once more when the
package becomes visible and diff-able on respighi), thanks!


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


signature.asc
Description: PGP signature

Re: Upcoming D-I Bookworm RC 4 and pseudo-RC 5

[Holger Wansing]

Hi,

Cyril Brulebois  wrote (Sat, 3 Jun 2023 20:07:05 +0200):
> At the moment I've spotted three uploads:
>  - apt-setup (1:0.183), for ports architectures.
>  - preseed (1.118), for Hurd, even if the changelog is not quite verbose
>about that part…
>  - vte2.91 (0.70.5-1): new upstream (bugfix) release with no particular
>bugfixes identified.

I have just uploaded grub-installer 1.194, which completes Croatian and
Ukranian translation.
Feel free to include it in bookworm, if possible.


Holger

-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Re: Upcoming D-I Bookworm RC 4 and pseudo-RC 5

[Cyril Brulebois]

Hi,

Here's a quick update about my current plans regarding the installer and
regarding debian-cd dry runs.

(Trimming recipients; also, I'm using 12.0.0 below as I'm referring to
the version identifier on the debian-cd side, but that's hopefully
synonymous with Debian 12.0, i.e.  the initial Bookworm release.)

Cyril Brulebois  (2023-05-24):
> I might pick a last minute tasksel change as well (for lxqt); I think
> it would help, could break, but that would be trivially revertable
> (and there would be room to do so, see below).

I did that, didn't hear bad things about it, be it from users or
maintainers.

> Checked with Salvatore: still no upload planned before the release.

I've asked Salvatore to update me on this one, but I haven't heard of
any changes in that area at the moment.

> I think I'll go for this one, aiming for May 25 or May 26 unless some
> issues pop up.

Details disagreed so that ended up being May 27 instead, but close
enough.

> We know we have at least the apt vs. adduser issue that's going to get
> resolved, and I'd prefer not to wait for it, and also not to rush the
> update into testing…

That migrated after the release, and will be part of pseudo-RC 5 and
more importantly 12.0.0.

> Also, we might have other packages that directly (because they produce
> udebs) or indirectly (because they're installed on every system, like
> apt) affect the installer or the installation process… migrate to
> testing later on.

Last packages that migrated (that I know of) are openssl (CVE fixes) and
libselinux (+b6 to minimize ESO). I'd be happy to be kept explicitly in
the loop for any further updates to udeb-producing packages (it appears
unblock-udeb does the job, including for binNMUs…), or things that the
release team would identify as being part of a standard installation, so
that we keep as many eyes open as possible…

> Let's consider a last debian-installer(-netboot-images) upload once
> Bookworm is definitely frozen, maybe a few days before the release to
> minimize the chances of having to consider a last-minute critical
> bugfix. Once it's in testing, we could even build images like we would
> for “D-I Bookworm RC 5”, just to be on the extra safe side. Those could
> be fetched by testers, but wouldn't be signed or announced (keeping them
> in the “usual dot directory”, deleting them a few days later). That
> would give us some extra peace of mind for the actual 12.0.0 images
> build that will happen on release day.

I plan to work on that mid-week, sometime on Wednesday (ideally, unless
we know more packages need migrating…) or Thursday (as a fallback). I'll
check with other debian-cd members, but I might even try and see how a
full build would work, so that we have some kind of advance knowledge
regarding the following week-end.

At the moment I've spotted three uploads:
 - apt-setup (1:0.183), for ports architectures.
 - preseed (1.118), for Hurd, even if the changelog is not quite verbose
   about that part…
 - vte2.91 (0.70.5-1): new upstream (bugfix) release with no particular
   bugfixes identified.

Unless specifically requested, I don't plan on including the first two
before Bookworm because we don't need it for release architectures. I
/think/ hurd-i386 gets somewhat released from unstable, so that
shouldn't matter… not sure about ports architectures. Those /could/ be
considered but truth be told, my default setting is: only change what is
absolutely required before Bookworm. vte2.19 seems quite vague, and
ignoring it entirely should be fine.

Since there was good progress on the arm64 console thing (#1036952), and
considering the current results of the investigation as to where vt102
comes from, and why arm64 isn't quite the deciding factor (a busybox
limitation instead), I'd be happy to consider getting an updated
rootskel for migration before pseudo-RC 5 and 12.0.0. Such an upload
would need to happen quickly though… (ema bcc'd, as possible uploader,
no obligations though!).


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


signature.asc
Description: PGP signature

Upcoming D-I Bookworm RC 4 and pseudo-RC 5

[Cyril Brulebois]

Hi all,

Cyril Brulebois  (2023-05-21):
> Dates that have been announced[1] so far:
>  - 2023-05-24: full freeze

[x] ← You are here!

>  - 2023-05-28: last moment to file unblock requests
>  - 2023-06-03: bookworm totally frozen
>(per “last week prior to the release”)
> 
>  1. https://lists.debian.org/debian-devel-announce/2023/04/msg7.html
> 
> On the d-i side, we'll have a round of translation updates, along
> with some last tweaks, before RC 4.

We should be all done in a few hours.

I might pick a last minute tasksel change as well (for lxqt); I think it
would help, could break, but that would be trivially revertable (and
there would be room to do so, see below).

> As far as I understand, at least at the moment, we aren't expecting a
> new linux upload before the release. But if the need arises, we should
> be able to deal with it.

Checked with Salvatore: still no upload planned before the release.

> I'm not sure what the best timeline would be for RC 4. Let's consider
> two options:
>  - [Soon]  Example: May 25.
>  - [Later] Window: May 28 - June 3.

No preferences have been expressed by the release team during today's
meeting.

> In the first case, we would have a little more time to sort incoming
> installation reports, and to react if needed. We might need a final
> upload of debian-installer(-netboot-images).

I think I'll go for this one, aiming for May 25 or May 26 unless some
issues pop up.

We know we have at least the apt vs. adduser issue that's going to get
resolved, and I'd prefer not to wait for it, and also not to rush the
update into testing…

Also, we might have other packages that directly (because they produce
udebs) or indirectly (because they're installed on every system, like
apt) affect the installer or the installation process… migrate to
testing later on.

Let's consider a last debian-installer(-netboot-images) upload once
Bookworm is definitely frozen, maybe a few days before the release to
minimize the chances of having to consider a last-minute critical
bugfix. Once it's in testing, we could even build images like we would
for “D-I Bookworm RC 5”, just to be on the extra safe side. Those could
be fetched by testers, but wouldn't be signed or announced (keeping them
in the “usual dot directory”, deleting them a few days later). That
would give us some extra peace of mind for the actual 12.0.0 images
build that will happen on release day.

It looks to me this would combine the best of two worlds:
 - Not wait too much before RC 4, leaving us some more days to deal with
   incoming reports;
 - Minimize risks of merging final changes in Bookworm, by having this
   “canary” RC 5 release.


Notes:
 - This would be different from what we did for Bullseye, where we had
   an RC 3 built using debian-installer 20210731, which was then reused
   as is for the 11.0.0 images build.
 - This would be different from what we did for Buster, where we had
   an RC 3 built using debian-installer 20190702, which was then reused
   as is for the 10.0.0 images build.
 - Given each D-I release is “lighter” than a full release build (be it
   for an initial release or a point release), it seems to me going for
   RC 4 plus pseudo-RC 5 is cheap enough to buy us peace of mind than
   delaying RC 4 until we think (but still aren't sure) nothing is going
   to change in Bookworm.
 - Release early, release often! (even if late in the release cycle…)
 - I'm doing most of the work anyway…


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


signature.asc
Description: PGP signature