* Jonathan Dowland <j...@debian.org> [241126 12:59]: > On Tue Nov 26, 2024 at 10:50 AM GMT, Andrey Rakhmatullin wrote: > > Yes, as they don't enable pristine-tar > > Is pristine-tar still valuable these days?
Unfortunately yes. AFAIK the two options for fixing this that are usually proposed are: 1) treat it as a problem of each individual developer, just like pristine-tar. Instead of pristine-tar, invent new tooling to manage tarballs. This path often tries to solve the problem only for Debian and only in a narrow scenario. 2) Have all uploads always supply a new orig.tar.gz. This could mean either treating every package as Debian-native, or some other solution. This is a global solution and reduces complexity instead of adding to it. > > and cannot guess your branch naming system. > > I haven't checked, but in an ideal world gbp would default to the same > values for these as described in DEP-14. In that same ideal world, we'd > have DEP-14 out of Draft status. IIRC gbp has an open bug for that in the state of "please send patches that do not break backwards compat". DEP14 also IMO needs to make a call on the layout, and not leave options, for any tooling to support it. Chris
