Bug#1074014: Bug#1073608: Bug#1074014: Bug#1073622: Bug#1073608: mksh, pax: no move to /usr going to happen, because:

2024-08-08 Thread Thorsten Glaser
Helmut Grohne dixit: >> Maybe the protective diversions also protect against this problem as well >> as the problem of moved files? I unfortunately failed to spot where the >> protective diversions were added in dh_movetouser (if that even is the >> right place to be looking), so I'm fairly sure

Bug#1074014: Bug#1073622: Bug#1073608: mksh, pax: no move to /usr going to happen, because:

2024-08-08 Thread Russ Allbery
Russ Allbery writes: > Sure, no problem. I'll file a bug against dash. #1007263 had already been filed and was on a very similar topic, so I have added some supplemental information to that bug report. -- Russ Allbery (r...@debian.org)

Bug#1074014: Bug#1073622: Bug#1073608: mksh, pax: no move to /usr going to happen, because:

2024-08-08 Thread Russ Allbery
Helmut Grohne writes: > Such concern is unwarranted. When dpkg unpacks a .deb, it unpacks all > the files with a .dpkg-tmp suffix appended. Hence, we also get a file > /usr/bin/mksh.dpkg-tmp. Once all of these are synced, it issues a > sequence of renames, including rename(/usr/bin/mksh.dpkg-tmp,

Bug#1074014: Bug#1073622: Bug#1073608: mksh, pax: no move to /usr going to happen, because:

2024-08-08 Thread Helmut Grohne
Hi Russ, On Thu, Aug 08, 2024 at 08:40:46AM -0700, Russ Allbery wrote: > Just to be sure, though, I don't think this is the problem that Thorsten > was worried about. My understanding of the problem Thorsten was reporting > was slightly different: Thank you for bridging the gap in communication.

Bug#1074014: Bug#1073608: Bug#1074014: Bug#1073622: Bug#1073608: mksh, pax: no move to /usr going to happen, because:

2024-08-08 Thread Russ Allbery
Thorsten Glaser writes: > There is absolutely no reason to force files to move, given they are now > aliased already *anyway*. I think this is the relevant Policy point. I pretty strongly disagree with this, and I think we also have a consensus on the Policy list that, no, we need to force all

Bug#1074014: Bug#1073608: Bug#1074014: Bug#1073622: Bug#1073608: mksh, pax: no move to /usr going to happen, because:

2024-08-08 Thread Russ Allbery
Helmut Grohne writes: > What changed over time is that we first added diversions for > transitioning from bash to dash and later removed that mechanism as the > transition is complete and the desire to choose your /bin/sh is not as > prevalent as it used to be (mainly because choice of /bin/sh no

Bug#1074014: Bug#1073622: Bug#1073608: mksh, pax: no move to /usr going to happen, because:

2024-08-08 Thread Russ Allbery
Helmut Grohne writes: > I was looking at this too narrowly from a mksh-perspective only and I > still think that the addition of dh_movetousr to mksh does not worsen > the situation on the mksh side. What I didn't see as clearly earlier is > that the way people tend to use mksh is by adding a loc

Bug#1074014: Bug#1073608: Bug#1074014: Bug#1073622: Bug#1073608: mksh, pax: no move to /usr going to happen, because:

2024-08-08 Thread Helmut Grohne
Hi Sam, I see this is getting a bit off-topic and reommend that you spin off a discussion on d-devel if this really matters to you. On Wed, Aug 07, 2024 at 04:27:01PM -0600, Sam Hartman wrote: > > "Helmut" == Helmut Grohne writes: > > Helmut> In bullseye and earlier, I guess it works. >