Sysop: | Amessyroom |
---|---|
Location: | Fayetteville, NC |
Users: | 43 |
Nodes: | 6 (0 / 6) |
Uptime: | 94:18:44 |
Calls: | 290 |
Calls today: | 1 |
Files: | 904 |
Messages: | 76,378 |
I was a happy user of pristine-tar for >10 years but since some time
(about 2 months) I end up with brocken tarball checksums when doing `gbp buildpackage` in *every* case.
I was a happy user of pristine-tar for >10 years but since some time (about 2 months) I end up with brocken tarball checksums when doing `gbp buildpackage` in *every* case.
Does it actually use pristine-tar?
I admit I can't say. The information is obtained from the pristine-tar branch. I simply assume gbp is calling pristine-tar.
do you have an example to analyze the problem.
The problem is that it seems to happen only on my laptop.
Whats the output of
cat ~/.gbp.conf
I was a happy user of pristine-tar for >10 years but since some time (about 2 months) I end up with brocken tarball checksums when doing `gbp
buildpackage` in *every* case.
Does it actually use pristine-tar?
I admit I can't say. The information is obtained from the pristine-tar branch. I simply assume gbp is calling pristine-tar.
You shouldn't assume but check whether it is calling it.
Whats the output of
cat ~/.gbp.conf
Ahhhhh, well, that was the trigger I needed. Usually I had
pristine-tar = True
Ahhhhh, well, that was the trigger I needed. Usually I had
pristine-tar = True
I hold the strong opinion that this is bad and repos using pristine-tar should have pristine-tar=True in debian/gbp.conf.
It is unlikely to be the consensus opinion.
Ahhhhh, well, that was the trigger I needed. Usually I had
pristine-tar = True
I hold the strong opinion that this is bad and repos using pristine-tar should have pristine-tar=True in debian/gbp.conf.
It is unlikely to be the consensus opinion.
It simply fits the policy of the teams I'm working in and thus was
sensible for me.
As long as all people who work on those packages have it enabled
globally...