On Tue, 6 Aug 2024 at 11:10, Matthew Vernon <matt...@debian.org> wrote: > > Hi, > > On 06/08/2024 10:42, Luca Boccassi wrote: > > > This is not a hard technical problem with no known solution that we > > are asking for design guidance on. This is a trivial technical > > problem with a hard social conflict at its core. What we are really > > blocked on is that the current owner of os-release refuses to let us > > fix it. > This is an unfair and inaccurate summary. The policy question of "should > testing and unstable be differentiated by os-release" isn't > straightforward, and there isn't consensus that the answer should be > "yes", as you would like it to be.
But in what way is it inaccurate? Are you saying there _is_ a hard technical problem with no known solution somewhere? My point is that I don't think there is one. I understand that the policy question is not straightforward, but that's exactly the point I was trying to convey: nitpicking over how a specific solution looks like is a distraction from the policy question, which is the important part of all of this, and the part that really needs clarification. And same question as I asked Sean earlier - by "consensus" here, do you mean that you want to see more people outside of TC members chiming in on the policy question? Again, I have not publicised this anywhere. I can do that and get more people to chime in, if that's the request. > Debian's current (and long-standing) answer to that question is "no", > and my view is that you have not advanced a sufficiently compelling case > that this answer should be changed. Sorry, I don't follow. How is that related to the implementation details of how to solve it?
