Your message dated Mon, 4 May 2026 10:52:47 +0100 with message-id <[email protected]> and subject line Re: Bug#1133887: gitlab repo accessibility checking defeated by gitlab changes? has caused the Debian Bug report #1133887, regarding gitlab repo accessibility checking defeated by gitlab changes? to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 1133887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1133887 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: git-debpush Version: 15.5 Severity: important Debian tag2upload service writes ("[tag2upload 3642] failed prs 0.5.2+dfsg-8"): > tag fetch failed: > problem at forge: > fetch tag: > not found, or inaccessible: > 404 Not Found, > url=https://salsa.debian.org/api/v4/projects/97265/repository/tags/debian%2F0.5.2+dfsg-8 > git-debpush is supposed to check for this, but my local experiments show confusing behaviour by gitlab. I think changes to gitlab and/or the new anti-"AI"-DoS system may have defeated it. Matthias, can you confirm what version of git-debpush you used, and whether you overrode any checks (interactively, or with --force) ? In my local shell: $ curl -L -v https://salsa.debian.org/debian/prs >t ... < HTTP/2 302 ... < location: https://salsa.debian.org/users/sign_in ,,, > GET /users/sign_in HTTP/2 ... < HTTP/2 200 Accessing a public repo does not trigger a redirect with curl. In my trixie firefox, in a private browsing window, not logged in, using browser dev tools: GET https://salsa.debian.org/debian/prs Status 404 I have not been able to discover when gitlab sends 404 (as would cause the existing git-debpush check to function correctly) and when it sends a 302 to redirect to a 200 login page. Possible workaround: $ GIT_ASKPASS=true git ls-remote https://salsa.debian.org/debian/drs remote: HTTP Basic: Access denied. If a password was provided for Git authentication, the password was incorrect or you're required to use a token instead of a password. If a token was provided, it was either incorrect, expired, or improperly scoped. See https://salsa.debian.org/help/topics/git/troubleshooting_git.md#error-on-git-fetch-http-basic-access-denied fatal: Authentication failed for 'https://salsa.debian.org/debian/drs.git/' Empirically, if GIT_ASKPASS is set and appers to succeed, git seems to ignore the credential.helper config options. 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.
--- End Message ---
--- Begin Message ---Based on information from the user whose job prompted this report, I think in fact it is working. 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.
--- End Message ---
