Otto Kekäläinen <[email protected]> writes: > The tag2upload service is tightly coupled with dgit, and while dgit by > design will never support pristine-tar type of ability to reproduce > upstream tarballs bit-for-bit, it should at least have the actual > upstream signed tags instead (from upstreams that publish them).
I have been using dgit with pristine-tar for years. It works fine with pristine-tar. People have told you this repeatedly. Please listen to us and stop repeating this blatantly misleading statement in every discussion about dgit. My current practice when importing a new upstream that uses a signed tarball is: % gbp import-orig --upstream-vcs-tag=... .../path/to/tarball ... do various other packaging work ... % dgit sbuild % dgit push-source If I start working on a package from a new machine, I run origtargz to recreate the upstream tarball from pristine-tar before running dgit operations. Everything works exactly like it did when I was using only git-buildpackage and uploading with dput, except better. -- Russ Allbery ([email protected]) <https://www.eyrie.org/~eagle/>
