Re: Do we still need pristine-tar?

[Nilesh Patra <nilesh@riseup.net>]

Hi Charles,

On 04/09/25 5:37 pm, Charles Plessy wrote:
> I tried git debpush (tag2upload) in a package I maintain by myself, and
> I loved it.

+1.

> With git debpush, the tag2upload service builds the source package,
> therefore there is no need to care about the upstream package MD5 sum.

It uses git-deborig and it makes the tar directly off git tag. So indeed, this
relieves us from caring much about md5sums and maintaining correct sums in git.

> Therefore I wonder if we can retire from using pristine-tar?  Although
> it has not been a source of trouble recently, it happened in the past
> and I am not sure about the future (not to mention that it does not
> seem to be maintained upstream).

Do you happen to know if t2u also works fine for multi-orig tarballs and can
regenerate them reliably? And if so how?

In particular, we use MUT for packages which need embedding of test data, as
written in policy https://med-team.pages.debian.net/policy/#embedding-large-test-data

I tried this on stringtie package but it seemed to not output the test data tarball.

With pristine-tar:

| $ gbp export-orig --pristine-tar
| gbp:info: Creating /tmp/test/stringtie_2.2.1+ds.orig.tar.xz
| gbp:info: Creating /tmp/test/stringtie_2.2.1+ds.orig-debian-tests-data.tar.xz
|
| $ ls ..
| stringtie  stringtie_2.2.1+ds.orig-debian-tests-data.tar.xz  stringtie_2.2.1+ds.orig.tar.xz

With git-deborig (or t2u):

| $ git-deborig
| $ ls ..
| stringtie  stringtie_2.2.1+ds.orig.tar.xz

Best,
Nilesh