Hi,
On 8/21/25 11:54 PM, Ian Jackson wrote:
Ian Jackson writes ("Re: [tag2upload 529] failed, cage 0.2.0+20250816-1"):
Hi. I saw this and investigated:
Debian tag2upload service writes ("[tag2upload 529] failed, cage
0.2.0+20250816-1"):
...
builder:work$ git fetch origin --no-tags
'refs/tags/debian/0.2.0+20250816-1:refs/tags/debian/0.2.0+20250816-1'
'refs/tags/upstream/0.2.0+20250816:refs/tags/upstream/0.2.0+20250816'
fatal: couldn't find remote ref refs/tags/upstream/0.2.0+20250816
t2u processor [dgit-repos-server]: failed command: ./ssh-builder
'[email protected]' 'env -C
/tmp/autopkgtest-virt-docker.shared.lqkafdxw/downtmp/work git fetch origin
--no-tags
'\''refs/tags/debian/0.2.0+20250816-1:refs/tags/debian/0.2.0+20250816-1'\''
'\''refs/tags/upstream/0.2.0+20250816:refs/tags/upstream/0.2.0+20250816'\'''
I looked at the logs. I can see in our debug log:
2025-08-16T13:32:55.066031Z debian/ tag created, job 529
2025-08-16T13:32:55.070689Z service starts work
2025-08-16T13:33:13.349728Z failed, sent this email
2025-08-16T13:34:45.507584Z upstream/ tag created
2025-08-16T13:37:23.286918Z debian/ tag deleted
2025-08-16T13:37:37.092350Z debian/ tag recreated, job 530, but duplicate
The service will only ever process each tag once. You'll be able to
get this to work by adding a new changelog stanza, I think.
(See under "Notes and advice" in the wiki).
I think git-debpush ought to have done better here. I will file a
bug.
Hi again. I realise this was a week ago now, but:
I filed #1111305, thinking that it git-debpush had erroneously failed
to push the debian/ tag. But now that I look at the code it seems to
do the thing I was accusing it of not doing. I wrote a test case and
it passes:
https://salsa.debian.org/dgit-team/dgit/-/merge_requests/303
Is it possible that you used git-debpush --tag-only, and then manually
pushed the debian/ tag ?
Yes! Sorry, I should have mentioned that earlier, I did not realize
git-debpush does additional/different checks when pushing.
cheers,
Birger
Regards,
Ian.
