Groups > linux.debian.bugs.dist > #1251655

Bug#1107103: Salsa also broken

From	"Trent W. Buck" <twb@cyber.com.au>
Newsgroups	linux.debian.bugs.dist
Subject	Bug#1107103: Salsa also broken
Date	2025-07-02 13:40 +0200
Message-ID	<L43YJ-eHFP-9@gated-at.bofh.it> (permalink)
References	<KST6F-7hfP-9@gated-at.bofh.it> <L40o9-eFjl-7@gated-at.bofh.it> <L43vH-eHvr-5@gated-at.bofh.it> <KST6F-7hfP-9@gated-at.bofh.it> <L43vH-eHvr-5@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On 2/7/25 21:00, Chris Hofstaedtler wrote:
> I'm not sure why we're discussing curl behaviour in a w3m bug.
> Anyway what you are seeing here is a bug in curl: [...]
> Anyway, none of that is relevant for w3m TTBOMK.

My fault.

w3m didn't work, so I cross-checked with curl, which also didn't work 
for http 1.0 (but did for http 1.1).

So I guessed that meant salsa was broken for http 1.0, and mentioned it 
on the "w3m can't do github because w3m is http 1.0" bug.

It didn't occur to me that curl might fail for unrelated reasons.

Further testing shows that
"w3m https://salsa.debian.org/debian/logcheck" works, but
"dman logcheck" then clicking (^I^M) the same link fails, with error message
"Can't load https://salsa.debian.org/debian/logcheck"

I don't know what's going on there, but I agree it's not relevant to 
1107103 (w3m HTTP/1.0 client is too old for github.com).

Sorry for the noise.

Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Bug#1107103: Salsa also broken "Trent W. Buck" <twb@cyber.com.au> - 2025-07-02 09:50 +0200
  Bug#1107103: Salsa also broken Chris Hofstaedtler <zeha@debian.org> - 2025-07-02 13:10 +0200
    Bug#1107103: Salsa also broken "Trent W. Buck" <twb@cyber.com.au> - 2025-07-02 13:40 +0200

csiph-web