Re: merged-usr

2022-09-13 Thread Adam Borowski
> > > Once the buildds have the debootstrap changes deployed, then we will
> > > upload init-system-helpers with the usrmerge | usr-is-merged
> > > dependency.  A notification about the transition will be sent to the
> > > debian-devel mailing list when that upload happens.
> 
> > Small update:
> > 
> > The debootstrap changes are all uploaded to stable-p-u and oldstable-
> > p-u and accepted for the next point releases. The point releases have
> > also been scheduled for September the 10th.
> 
> > So as soon the buildds have been updated to those point releases after
> > the 10th, I will proceed with uploading init-system-helpers with the new
> > dependency.
>
> Big update: with the new point releases done, it's a matter of hours/days
> until the buildds get the new debootstrap, so we are almost ready.

# debootstrap --variant=buildd unstable foo ...
# chroot foo dpkg -l usr-is-merged|grep ^ii
ii  usr-is-merged  30   all  Transitional package to assert a 
merged-/usr system

# debootstrap --no-merged-usr unstable foo ...
# chroot foo dpkg -l usr-is-merged|grep ^ii
ii  usr-is-merged  30   all  Transitional package to assert a 
merged-/usr system

... so your broken dependency won't cause breakage yet  :þ

On the other hand: WTH?


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Bestest pickup line:
⢿⡄⠘⠷⠚⠋⠀ "Cutie, your name must be Suicide, cuz I think of you every day."
⠈⠳⣄



Re: merged-usr

2022-09-13 Thread Simon McVittie
On Tue, 13 Sep 2022 at 12:57:28 +0200, Adam Borowski wrote:
> # debootstrap --no-merged-usr unstable foo ...
> # chroot foo dpkg -l usr-is-merged|grep ^ii
> ii  usr-is-merged  30   all  Transitional package to assert a 
> merged-/usr system
...
> On the other hand: WTH?

I assume your "WTH" was at a non-merged-/usr chroot having the usr-is-merged
metapackage?

As I pointed out when I was asked to review the debootstrap change[1],
this is actually correct, but it's not at all obvious that it's correct.
The usr-is-merged metapackage is arguably misnamed: its actual semantics
are that the system is on the "new" side of the merged-/usr transition
(either the /usr-like directories have been merged into /usr, or that
merge has deliberately been avoided in a way that will become unsupported
with the release of bookworm, either of which makes it unnecessary to
install the usrmerge package and its non-trivial dependencies).

But that's quite a lot to express in a package name, renaming it would
require another trip through NEW, and in the only scenario that is
intended to be supported beyond bookworm release day, its name is
accurate; so its current name seems close enough to the truth.

smcv

[1] 
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/71/#note_324399