Hi Ian
Running locally, pristine-tar checkout works just fine:
$ pristine-tar checkout -- ../python-bumps_1.0.5.orig.tar.gz
pristine-tar: successfully generated ../python-bumps_1.0.5.orig.tar.gz
I suspect different versions behaviour differently. The tag2upload
source package construction currently runs largely on stable.
I'm afraid I don't have time to try a local repro and experiment with
different versions right now. I might have some time for that
tomorrow. But if you felt like telling what it does for you on stable
(if that's not what you're running) that would be very helpful.
The above is pristine-tar 1.50+nmu2 running on stable. (I picked up dgit
itself from sid so that I could try out the new pristine-tar workflow
but the machine is otherwise all trixie)
Versions of packages pristine-tar depends on:
ii bzip2 1.0.8-6
ii libbz2-1.0 1.0.8-6
ii libc6 2.41-12+deb13u4
ii libsys-cpuaffinity-perl 1.13~03-2+b4
ii pbzip2 1.1.13-1
ii perl 5.40.1-6
ii pixz 1.0.7-4
ii tar 1.35+dfsg-3.1
ii xdelta 1.1.3-10.7
ii xdelta3 3.0.11-dfsg-1.2
ii xz-utils 5.8.1-1+deb13u1
ii zlib1g 1:1.3.dfsg+really1.3.1-1+b1
pristine-tar and xdelta3 seem most relevant and have the same versions
in trixie and sid.
Looking at this particular repo - there is a .gitattributes file - how
is the pristine-tar orig-generating path interacting with .gitattributes?
regards
Stuart
--
Stuart Prescott http://www.nanonanonano.net/ [email protected]
Debian Developer http://www.debian.org/ [email protected]
GPG fingerprint 90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
