Hi Sean, On Thu, Mar 24, 2022 at 09:31:21AM -0700, Sean Whitton wrote: > We should distinguish two senses of "supported". > > There is the sense of what Debian-the-project supports. That is > specified in the TC decision. That is not subjective.
This could be a language issue on my side. As I see it, the Debian project clearly endorses merged-/usr. I have difficulties calling it support, because that would go in hand with fixing the resulting problems - which is not happening. In my reading, support is an activity rather than a statement. That activity is missing. I even ran into /usr-merge fallout in 2022 myself. The statement is clear enough and Guillem's warning is clearly not helping the state of affairs. > The difficulty is that Guillem's warning kind of refers to both. Yeah, I see how you get there. It is fully in line with the confusion I see elsewhere. Let us try to turn this upside down: How can Guillem express his dissatisfaction with the current process in a way that does not cause harm? Guillem has to deal with quite a number of /usr-merge-caused bugs. Many of them lack patches and/or are duplicating existing ones. In cases patches were posted (e.g. dpkg-shlibdeps), Guillem has included them. Part of the answer would have been talking to the ctte at the time the decision was made. It's sad that he opted for not doing that. Helmut
