Hi, On 12/01/2024 12:31, Helmut Grohne wrote:
For the gzip case, we have the additional question whether we tolerate the temporary policy violation for the trixie upgrade or halt the /usr-move and retry with a modified dpkg (that could land in trixie, so we could complete in forky).
What's the scope of dpkg modification needed here? And is likely the sort of thing the dpkg maintainers would accept. Were we not already in a bit of a mire here, it's not clear to me that policy is wrong here (and thus that we should set it aside).
I also note that there may be unknowns beneath. In May last year, things looked good, then we found empty directory loss and m-a:same shared file loss. Then things looked good again until October when we found this. Chances are, there are more unknowns.
This continues to make me worry we are not on the path of robust engineering. But I appreciate I'm in a very small minority in that regard.
Regards, Matthew