Ansgar 🙀 <ans...@43-1.org> writes: > The only published branch (debian/unstable) looks like it would be > trivial to for git-debpush to compute an integrity hash as suggested > using only a bit shell around Git commands (no dpkg, dgit or anything)? > (AFAIU git-debpush would already check that patches apply cleanly here, > so it could provide hashes of either patches-applied or patches- > unapplied.)
Oh! Well, that's certainly embarrassing. This is exactly what Ian was trying to tell me in the other thread, and I didn't understand what he was saying. I thought dgit plus git-debrebase deferred more work to the post-tag step than it actually does. I guess that shows you how much attention I pay to debian/patches when it's being tool-managed for me. So yes, you're right, the git-debrebase example is not nearly as interesting as I had thought because the tooling works differently than I had realized. I'm sorry for all the noise! That means I don't have a ready example for you. My packages all use git-debrebase these days. I have seen other discussions go by about workflows that require different types of transformations, but I did not retain the names of the source packages and my memory is not clear enough to throw up good search terms. Maybe someone else has a link for you. -- Russ Allbery (r...@debian.org) <https://www.eyrie.org/~eagle/>
