Bastian Blank dijo [Thu, May 18, 2023 at 09:05:44PM +0200]: > But why does the state of the package (native vs non-native) can have > any effect on a CTTE decision? Or do you want to say I can block CTTE > from reaching any kind of decision just by uploading a package as > native? Sorry, but this does not compute. > (...) > Sure, but this is a direct violation of a CTTE decision. How often do > you think someone could do that?
During my time as a Technical Committe member, /usr-merge was the point we most came back to. And yes, the way the TC decisions were dodged or omitted by the dpkg maintainers was... quite depressing. However, my reply should only be read regarding what I believe should be done in the following ~month before the release. Of course, I don't see the situation as ideal, nor as something that should persist. I hope a _fixed_ dpkg is uploaded and becomes part of Bookworm's first point release. But, even if it were on the table (which is not AFAICT), I would (in a strictly personal capacity) oppose the TC requiring such a patch at this point.
