Paul Gevers wrote: > I have started to go through reports against the release-notes, to be > ready when we release.
That's good. I've done my own initial trial-run upgrade and found absolutely nothing to report. > diff --git a/en/issues.dbk b/en/issues.dbk > index 20122d3e..706266bf 100644 > --- a/en/issues.dbk > +++ b/en/issues.dbk > @@ -219,6 +219,20 @@ information mentioned in <xref linkend="morereading"/>. > </para> > </section> > > + <section id="glibc-and-linux" arch="i386;amd64"> > + <!-- stretch to buster--> > + <title>glibc requires linux kernel 3.2 or higher</title> That should definitely be "Linux" with a capital L; and at the start of a title I'd also expect to see "Glibc". <title>Glibc requires Linux kernel 3.2 or higher</title> > + <para> > + Starting with <systemitem role="source">glibc</systemitem> 2.26, Linux > + kernel 3.2 or later is required. The <systemitem > + role="package">libc6</systemitem> preinst has a check and aborts the > + installation if it is not the case to avoid completely breaking the > + system. That said it will leave the upgrade unfinished. Please update > the > + kernel before starting the system upgrade if the system still runs a > + kernel before 3.2. The wording could be better. I would suggest Starting with <systemitem role="source">glibc</systemitem> 2.26, Linux kernel 3.2 or later is required. The preinst for <systemitem role="package">libc6</systemitem> performs a check, and if this fails then to avoid completely breaking the system it will abort the package installation, which will leave the upgrade unfinished. If the system is running a kernel older than 3.2, please update it before starting the distribution upgrade. -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package