Hi,

While working on https://debaudit.debian.net/, I ran into an issue with
ntirpc/7.0-1, which is currently in unstable and trying to migrate to
forky.

debaudit detects the following issue in unstable:
You can find more details at:
https://debaudit.debian.net/git2orig/result/d4a2dd4bb2e0707350ce51f556688db8bd00a5005eff7416727391a07e7ba73b

The version in forky (6.3-4) tested fine, with the following diagnostic:
Since Debaudit is in heavy development, I am very interested in hearing if the
issue was misdetected somehow.

Thanks,

Lucas Nussbaum

Hi Lucas,

Am 02.03.26 um 07:57 schrieb Lucas Nussbaum:
This page does not show any problems. Maybe it was a transient error?

gbp.conf is in my git history:

Regards
Christoph

Hi Christoph,

The logs on the service performing the checks are:

2026-02-28 02:51:07,984 - debaudit.cli - INFO - [git2dsc] Processing ntirpc...
2026-02-28 02:51:12,402 - debaudit.cli - INFO - [87/189] Saving result for https://deb.debian.org/debian/pool/main/n/ntirpc/ntirpc_7.0-1.dsc: 310 - gbp.conf but no corresponding commit
2026-02-28 03:00:10,657 - debaudit.cli - INFO - [git2orig] Processing ntirpc...
2026-02-28 03:00:17,150 - debaudit.cli - INFO - [73/188] Saving result for https://deb.debian.org/debian/pool/main/n/ntirpc/ntirpc_7.0-1.dsc: 310 - gbp.conf but no corresponding commit

=> at this point, neither the pristine-tar branch nor the git were
available?

2026-03-02 20:31:47,381 - debaudit.cli - INFO - [git2orig] Processing ntirpc...
2026-03-02 20:31:56,550 - debaudit.cli - INFO - [5/9] Saving result for https://deb.debian.org/debian/pool/main/n/ntirpc/ntirpc_7.0-1.dsc: 903 - tarballs identical (pristine-tar, gbp)

=> and at this point, both were (for 7.0-1) ?

2026-03-03 02:54:52,186 - debaudit.cli - INFO - [git2dsc] Processing ntirpc...
2026-03-03 02:54:56,445 - debaudit.cli - INFO - [1/32] Saving result for https://deb.debian.org/debian/pool/main/n/ntirpc/ntirpc_7.0-2.dsc: 310 - gbp.conf but no corresponding commit

=> no tag for 7.0-2

2026-03-03 02:57:00,088 - debaudit.cli - INFO - [git2orig] Processing ntirpc...
2026-03-03 02:57:07,753 - debaudit.cli - INFO - [3/32] Saving result for https://deb.debian.org/debian/pool/main/n/ntirpc/ntirpc_7.0-2.dsc: 901 - tarballs identical (pristine-tar)

=> but pristine-tar branch (which was already there, for 7.0, from the
7.0-1 upload)

2026-03-03 13:12:41,401 - debaudit.cli - INFO - [git2dsc] Processing ntirpc...
2026-03-03 13:12:51,965 - debaudit.cli - INFO - [1/1] Saving result for https://deb.debian.org/debian/pool/main/n/ntirpc/ntirpc_7.0-2.dsc: 910 - git-generated dsc identical to archive dsc after normalization
2026-03-03 13:13:06,303 - debaudit.cli - INFO - [git2orig] Processing ntirpc...
2026-03-03 13:13:15,521 - debaudit.cli - INFO - [1/1] Saving result for https://deb.debian.org/debian/pool/main/n/ntirpc/ntirpc_7.0-2.dsc: 903 - tarballs identical (pristine-tar, gbp)

=> 7.0-2 tag available

Is there any chance that you are not pushing the tags (and other
branches like pristine-tar) at upload time?

Lucas

Am 03.03.26 um 14:46 schrieb Lucas Nussbaum:
Right. I normally wait with the pushing the tags until the upload is
accepted, because I had the case that my upload was not accepted, and I
still had to change the release. But maybe I have to change that routine
...

( or even try tag2upload )

Christoph