If the upstream tag is not present on salsa, but is present locally,
git-debpush currently sends the signed tag2upload tag to the service,
which then fails because it can't find the upstream tag.

I think git-debpush could spot this.

Maybe it should always push the upstream tag if it's present locally
but not on the remote.  It should certainly at least fail a check
in this situation.

Ian.

(Sean: feel free to take off the newcomer tag if you think this is too
fiddly.  I think it should be fine given we'll be around to help.)

Hello,

I actually thought it already pushed the upstream tag in this case.
So, I agree, and I'd suggest pushing it rather than failing a check.

Should be okay with our help, yeah.

Hello,

Fixing this is blocked on working around [1].  We can work around that
sufficient for this bug by doing separate pushes for each tag.

[1]  https://gitlab.com/gitlab-org/gitlab/-/issues/562101

https://salsa.debian.org/salsa/support/-/issues/498

Ian Jackson writes ("Re: [tag2upload 529] failed, cage 0.2.0+20250816-1"):

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 ?

Regards,
Ian.

Hi,

Yes! Sorry, I should have mentioned that earlier, I did not realize
git-debpush does additional/different checks when pushing.

cheers,
Birger

Birger Schacht writes ("Bug#1111305: [tag2upload 529] failed, cage 0.2.0+20250816-1"):

Right, if you say --tag-only it doesn't fetch or push anything.

Thanks for confirming.

Ian.

Hello,

I think that means there is no bug here, so I'm going ahead and closing.