Ansgar 🙀 <ans...@43-1.org> writes: > On Fri, 2024-06-21 at 08:29 -0700, Russ Allbery wrote:
>> Wait, why would I ever want to upload a 3.0 (native) package for a >> non-native package with the tooling as it is today in Debian? > As far as I understand this whole thread is about changing the tooling. This whole thread is about deploying something that already works with our existing tooling and doesn't require boil-the-ocean changes to Debian infrastructure or workflows. > Why do you point them to build artifacts instead of just the diff > (including individual commits) between the upstream tree and Debian tree > in Git? ...what? Because that's a godawful UI? Because there are lots of intermixed commits, some of which are to Debian files and some of which are to upstream files? Because it requires a whole bunch of Git knowledge to extract anything vaguely useful from that and how to do so depends on exactly what my workflow is? Because I want to use the same system that everyone else uses in Debian so that all any upstream, downstream, or person working on packages for another distro has to do is go to the package tracker for my package and click on the patches link? > I would still like to understand how your packages would not work with > the suggested integrity check. Could you give an example, possibly with > a reference to a Git repository as well? https://tracker.debian.org/pkg/tf5 See the "debian patches" link in the right sidebar. -- Russ Allbery (r...@debian.org) <https://www.eyrie.org/~eagle/>
