Bug#1091682: bookworm-pu: package debootstrap/1.0.128+nmu2+deb12u2

[Luca Boccassi]

Package: release.debian.org
Severity: normal
Tags: bookworm
User: ***@packages.debian.org
Usertags: pu

Dear Release Team,

We would like to remove the legacy usr-is-merged/usrmerge packages from
testing/unstable, but debootstrap in bookworm still pulls usr-is-merged
in manually and fails if it cannot be found. As you know, it is no
longer necessary in testing/unstable as the work is done in base-files.

I have uploaded debootstrap/1.0.128+nmu2+deb12u2 to bookworm-p-u with
this change backported from unstable. debdiff attached.

Thanks!

[Helmut Grohne]

Dear release team,

Post by Luca Boccassi
We would like to remove the legacy usr-is-merged/usrmerge packages from
testing/unstable, but debootstrap in bookworm still pulls usr-is-merged
in manually and fails if it cannot be found. As you know, it is no
longer necessary in testing/unstable as the work is done in base-files.
I have uploaded debootstrap/1.0.128+nmu2+deb12u2 to bookworm-p-u with
this change backported from unstable. debdiff attached.

Please allow me to second the request. At this time, I am not sure
whether we will manage to remove usrmerge in the trixie cycle. Even if
we are not, it would be very useful if bookworm's debootstrap were to be
able to bootstrap forky and this is change is required there.

I see a small risk of the change in matching having unintended effects
on derivatives that disguise themselves as Debian and have not yet
picked up the merge via base-files. I therefore recommend waiting with
accepting this change until it has survived in trixie for at least two
weeks. Not sure we notice as the failure path should be installing
usrmerge via init-system-helpers.

Helmut

[Luca Boccassi]

Post by Helmut Grohne
Dear release team,

Post by Luca Boccassi
We would like to remove the legacy usr-is-merged/usrmerge packages from
testing/unstable, but debootstrap in bookworm still pulls usr-is-merged
in manually and fails if it cannot be found. As you know, it is no
longer necessary in testing/unstable as the work is done in base-files.
I have uploaded debootstrap/1.0.128+nmu2+deb12u2 to bookworm-p-u with
this change backported from unstable. debdiff attached.

Please allow me to second the request. At this time, I am not sure
whether we will manage to remove usrmerge in the trixie cycle. Even if
we are not, it would be very useful if bookworm's debootstrap were to be
able to bootstrap forky and this is change is required there.
I see a small risk of the change in matching having unintended effects
on derivatives that disguise themselves as Debian and have not yet
picked up the merge via base-files.

I don't think we should guide what we do for our stable point releases
based on hypothetical derivatives. If you import our sources, you need
to be on point with what we do, this is not news.
The p-u freeze for the next point release is next weekend, and I would
strongly prefer not to miss the boat, as the next one might clash with
Trixie (we don't know yet).

Post by Helmut Grohne
Not sure we notice as the failure path should be installing
usrmerge via init-system-helpers.

init-system-helpers no longer depends on usrmerge

[Adam D Barratt]

package release.debian.org
tags 1091682 = bookworm pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm.

Thanks for your contribution!

Upload details
==============

Package: debootstrap
Version: 1.0.128+nmu2+deb12u2

Explanation: do not pull in usr-is-merged in trixie/sid

[Debian Bug Tracking System]

Your message dated Sat, 11 Jan 2025 11:03:08 +0000
with message-id <E1tWZGm-009jXp-***@coccia.debian.org>
and subject line Close 1091682
has caused the Debian Bug report #1091682,
regarding bookworm-pu: package debootstrap/1.0.128+nmu2+deb12u2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)