Package: git-debpush Version: 13.12 Watching the t2u logs I saw another job failed because the tag was 404 where the whole repository was also 404, probably because the repo permissions were misconfigured. This has happened several times now.
I think git-debpush could detecct this, if we're prepared to give it salsa-specific information. In particular, if the remote is [email protected]:user/project then we should check that https://salsa.debian.org/user/project.git is reachable via git without athentication. Or something. Empirically: git-ls-remote https://salsa.debian.org/dgit-team/dgit.git '' # exit status 0, printing nothing git-ls-remote https://salsa.debian.org/dgit-team/no-such-repo.git '' # prompts for a username # same behaviour for a repo that I think exists privately Alternative approaches (eg querying the gitlab API) might need more much-more-gitlab-spdcific information in git-debpush. To avoid adding latency, this should be done in parallel with the git fetch. Ian. -- Ian Jackson <[email protected]> These opinions are my own. Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.
