Debian packaging

Problem is (a) it's yet another tool to learn and (b) worse, I want the (1) raw upstream git archive with (2) any Debian patches, then (3) the Debian packaging (_without_ any "debian/patches" subdirectory) on top of that.

"dgit" is more than likely to fail at (1), esp. when the "original" archive isn't but has been stripped from anything non-DFSG-free. Also, it first merges Debian packaging and then unravels debian/patches/series, while a sane upstream-able git tree is structured the other way round.

The Debian archive structure is from a world where there was no widely-available distributed VCS and source tarballs were required. Today? not so much.

I feed "archive location + commit ID" to my builder, from a post-commit hook, and expect it to build the binary packages and to push them to my archive. Done.

I do not want to futz around with collecting, assembling and uploading source packages. Doing that is not just superfluous – the whole ancient mechanism blocks further progress. IMHO it's beyond time for Debian to drop all that nonsense and switch to making "git push" the one and only way to update Debian source packages. You can simply run "dgit clone … && git push --force dgit/sid archive:sid" when somebody does a legacy source upload.