Debian pauses /usr merge file moves
This moratorium lasts until we vote to repeal it. We expect to do that during the trixie development cycle, and sooner rather than later. We will continue to facilitate efforts to resolve the remaining issues that stand in the way of safely repealing the moratorium.
Trixie is the codename for Debian 13, the upcoming major release cycle.
Note: this item originally ran with a headline saying that the
/usr merge had been paused, which is evidently not accurate.
Posted May 17, 2023 13:42 UTC (Wed)
by bluca (subscriber, #118303)
[Link] (1 responses)
Posted May 17, 2023 18:18 UTC (Wed)
by smcv (subscriber, #53363)
[Link]
On a merged-/usr system (which will include all Debian 12 and Debian 13 systems, both new installations and upgrades), both /bin/cat and /usr/bin/cat exist, but dpkg is only aware of one of those paths (/bin/cat in this case); in dpkg jargon, the other is said to be an alias. The specific action that should not proceed until further notice is: swapping the path that dpkg considers to be canonical, for example from /bin/cat to /usr/bin/cat.
Posted May 17, 2023 13:52 UTC (Wed)
by rweikusat2 (subscriber, #117920)
[Link] (8 responses)
Posted May 17, 2023 14:02 UTC (Wed)
by bluca (subscriber, #118303)
[Link] (1 responses)
Posted May 17, 2023 18:11 UTC (Wed)
by rweikusat2 (subscriber, #117920)
[Link]
:-)
Posted May 17, 2023 14:10 UTC (Wed)
by kilobyte (subscriber, #108024)
[Link]
Posted May 17, 2023 20:49 UTC (Wed)
by mjg59 (subscriber, #23239)
[Link] (4 responses)
Posted May 17, 2023 22:36 UTC (Wed)
by jhe (subscriber, #164815)
[Link] (3 responses)
Posted May 18, 2023 0:49 UTC (Thu)
by mjg59 (subscriber, #23239)
[Link] (2 responses)
Posted May 18, 2023 11:31 UTC (Thu)
by jhe (subscriber, #164815)
[Link] (1 responses)
Posted May 18, 2023 17:35 UTC (Thu)
by mjg59 (subscriber, #23239)
[Link]
Posted May 17, 2023 14:16 UTC (Wed)
by pdewacht (subscriber, #47633)
[Link] (3 responses)
Posted May 17, 2023 14:30 UTC (Wed)
by bluca (subscriber, #118303)
[Link]
Posted May 17, 2023 17:42 UTC (Wed)
by amacater (subscriber, #790)
[Link] (1 responses)
TL;DR - If you do a new install, you shouldn't need to worry. Debian 12 is shaping up well.
[Full disclosure: I'm a Debian developer but have no viewpoint on how easy/difficult the necessary work for the full merged /usr transition is going to be.]
Posted May 17, 2023 18:11 UTC (Wed)
by smcv (subscriber, #53363)
[Link]
The change that the technical committee is asking Debian contributors to avoid for now is mostly only visible/relevant to Debian contributors, and is to do with changing which of the two possible paths (for example /bin/foo or /usr/bin/foo) is considered to be the canonical path by dpkg. On end-user systems, the compatibility symlinks mean that both /bin/foo and /usr/bin/foo exist; that is not new, and is not changing.
Posted May 17, 2023 16:40 UTC (Wed)
by nickodell (subscriber, #125165)
[Link] (7 responses)
Posted May 17, 2023 16:50 UTC (Wed)
by bluca (subscriber, #118303)
[Link] (6 responses)
Posted May 17, 2023 17:49 UTC (Wed)
by ovitters (guest, #27950)
[Link]
Posted May 17, 2023 17:54 UTC (Wed)
by archaic (subscriber, #111970)
[Link] (4 responses)
Posted May 17, 2023 18:25 UTC (Wed)
by smcv (subscriber, #53363)
[Link]
That activity has been temporarily suspended, but we expect it to become desirable in future, after some technical issues that block it have been resolved; so by the definition you cited, this is indeed a moratorium.
This does not affect whether /usr is merged on end-user systems: it only affects the state of the dpkg database and the contents of new .deb files. So it is misleading to summarize this as the /usr merge having been paused.
Posted May 17, 2023 18:28 UTC (Wed)
by bluca (subscriber, #118303)
[Link] (2 responses)
Posted May 17, 2023 18:36 UTC (Wed)
by dullfire (guest, #111432)
[Link] (1 responses)
Posted May 17, 2023 18:55 UTC (Wed)
by bluca (subscriber, #118303)
[Link]
Debian pauses its /usr merge — again
Debian pauses its /usr merge — again
Debian pauses its /usr merge — again
Debian pauses its /usr merge — again
Debian pauses its /usr merge — again
Debian pauses its /usr merge — again
Debian pauses its /usr merge — again
Debian pauses its /usr merge — again
Debian pauses its /usr merge — again
Debian pauses its /usr merge — again
Debian pauses its /usr merge — again
Debian pauses its /usr merge — again
Debian pauses its /usr merge — again
Debian pauses its /usr merge — again
Debian pauses its /usr merge — again
Debian pauses its /usr merge — again
So what's being voted on here?
Debian pauses its /usr merge — again
Debian pauses its /usr merge — again
The title is misleading because the technical committee didn't understand the definition of moratorium, which is:
Debian pauses its /usr merge — again
a temporary suspension of an activity or law until future consideration warrants lifting the suspension
The TC's email was subjected with:
Reinstatement of merged-/usr file movement moratorium
Therefore, they (the TC, not LWN) said they were "reinstating" the "suspension". I agree the article's title is misleading, but it does accurately reflect Debian's title, if not content.
Debian pauses its /usr merge — again
Debian pauses its /usr merge — again
Debian pauses its /usr merge — again
Debian pauses its /usr merge — again
