Your message dated Tue, 6 Aug 2024 14:18:17 +0000 (UTC) with message-id <pine.bsm.4.64l.2408061412430.16...@herc.mirbsd.org> and subject line mksh, pax: no move to /usr going to happen, because: has caused the Debian Bug report #1073608, regarding mksh: move aliased files from / to /usr (DEP17) 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 ow...@bugs.debian.org immediately.) -- 1073608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073608 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: mksh Version: 59c-37 Severity: important Tags: patch trixie sid User: helm...@debian.org Usertags: dep17m2 dep17dhmovetousr This package is part of the /usr-move (DEP17) transition, because it contains files in aliased locations and should have those files moved to the corresponding /usr location. The goal of this move is eliminating bugs arising from aliasing, such as file loss during package upgrades. The following files in the following binary packages are affected. mksh contains: * bin * bin/lksh * bin/mksh * bin/mksh-static * bin/rlksh * bin/rmksh You may add dh-sequence-movetousr to Build-Depends to perform the move. This is an easy and readily applicable measure that has been verified for this package using a test build. The main advantage of this method is the low effort and it just works when backporting to bookworm. However, it is more of a stop-gap measure as eventually the installation procedure should refer to the files that are actually used for installation. This often means updating debian/*.install files but also changing flags passed to a configure script or similar measures. In case you do not anticipate your package being uploaded to bookworm-backports, please prefer a manual move, but generally prefer moving over delaying any further. After having done this move, please keep in mind that the relevant changes need to be reverted for bookworm-backports, with these exceptions: Â * dh-sequence-movetousr and dh_movetousr cancel themselves. Â * dh_installsystemd and dh_installudev revert to the aliased location. Â * The pkg-config variables systemdsystemunitdir in systemd.pc and udevdir in udev.pc reverts to aliased. Please keep in mind that restructuring changes may introduce problems after moving. A change is considered restructuring if formerly aliased files formerly owned by one package are later to be owned by a package with a different name. Such uploads should be done to experimental and quarantine for three days before moving to unstable. This way, automatic analysis (https://salsa.debian.org/helmutg/dumat) can detect problems and file bugs. Such bugs shall include support for resolving the problems. The severity of this bug shall be raised to RC on August 6th. For additional information about refer to https://wiki.debian.org/UsrMerge and https://subdivi.de/~helmut/dep17.html.
--- End Message ---
--- Begin Message ---Halmut, we have exchanged numerous eMails, and you’ve not disagreed with the last points you raised. I did get a disagreement from guillem about omitting the top-level directory (which was only a workaround for the “dpkg-deb -x mksh.deb / will break a /usr-merged system” thing you said. There are two places to address: 1. the /bin symlink The implicit Pre-Depends on the Essential set being unpacked, where base-files contains the /bin symlink, is sufficient to avoid /bin ending up as a directory. No action needs to be taken in the packages that are not part of the (Pseudo‑)Essential set. 2. the dpkg-deb -x issue Since guillem has rejected the possible workaround suggestion, he, as dpkg maintainer, can fix this in dpkg-deb itself. Au contraire, moving the files WILL break users’ systems, as having /bin/sh be a symlink to lksh is a supported configuration, and I am a̲b̲s̲o̲̲l̲u̲t̲e̲l̲̲y̲ ̲N̲O̲T̲ taking a possible convoluted thing to work around this. mksh is continuously backported (not in bpo) as well, I’m totally not going to break things. And if mksh doesn’t need it, then pax also doesn’t. bye, //mirabilos -- Gestern Nacht ist mein IRC-Netzwerk explodiert. Ich hatte nicht damit gerechnet, darum bin ich blutverschmiert… wer konnte ahnen, daß SIE so reagier’n… gestern Nacht ist mein IRC-Netzwerk explodiert~~~ (as of 2021-06-15 The MirOS Project temporarily reconvenes on OFTC)
--- End Message ---
