Hi Colin, On Tue, Jan 09, 2024 at 01:32:11PM +0000, Colin Watson wrote: > On Mon, Jan 08, 2024 at 03:01:11PM -0800, Steve Langasek wrote: > > On Fri, Jan 05, 2024 at 09:17:52PM +0100, Paul Gevers wrote: > > > On 05-01-2024 17:36, Rene Engelhard wrote: > > > > Also a problem is that experimental also might already contain totally > > > > unrelated updates like new upstream versions...
> > > I share this worry. Have you thought about how to handle the cases where
> > > you
> > > don't have experimental to upload to? How big is this problem?
<snip>
> In the current situation, though, not having experimental available
> means that there's no opportunity for dumat to weigh in regarding
> usrmerge interactions, which seems problematic given Helmut's
> preliminary analysis.
I guess this is a reply to the bits of context I retained above rather than
directly a reply to my most immediate preceding message. In a separate
subthread, I laid out what I thought the process should be for handling the
transition of packages in that situation; but you are raising a separate
point.
Which parallels what Helmut had to say:
> Whenever you face files in aliased locations (other than systemd units),
> please go via experimental to let dumat judge your upload. Check the
> bookworm package for files in aliased locations, not the unstable one.
I have also had other out-of-band conversations with Helmut about the
overlapping issues between usrmerge and time_t, so this was generally
speaking on my radar although I didn't address it in my proposed transition
plan.
I think it is unrealistic to ask experimental to be otherwise quiesced of
transitions to ensure that we can stage all of the affected libraries in
experimental, and I also think that making false transitions for packages
that are ALREADY in experimental because of transitions would be
counterproductive. ("False" because if the library package has a different
soname between unstable and experimental, then renaming the runtime library
package in the *experimental* version is unnecessary because there's nothing
"in the wild" depending on that package name but with the old ABI for which
upgrade compatibility is of concern.)
My preferred path forward here would be, as Helmut suggests, to check which
libraries are in the intersection of (packages in experimental for which we
won't stage time_t uploads) and (packages that exist in bookworm and need
transitioning of aliased paths), and ensure that these packages are handled
carefully according to Helmut's own guidance. My optimistic expectation is
that the intersection will be null, or nearly; but in any case I will bring
data.
And my proposal for checking that set, since we're only talking about
runtime library packages, is to check whether any of the contents of these
packages in bookworm match ^/lib - as a runtime library package NOT matching
this pattern, but matching a pattern for one of the other aliased
directories, would be something ... special.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: PGP signature
