Control: usertag -1 debsources
Control: merge 761077 -1

Hi Tomas,

On Mon, Dec 14, 2020 at 02:13:49PM +0100, Tomas Pospisek wrote:
> Go to 
> https://codesearch.debian.net/search?q=Client+sent+an+HTTP+request+to+an+HTTPS+server
> select first link 
> https://codesearch.debian.net/show?file=gcc-10_10.2.1-1%2Fgcc-10.2.0%2Flibgo%2Fgo%2Fnet%2Fhttp%2Fserver.go&line=1798
> get a 404 with a list of 12 alternative source files of different
> versions of gcc-XX/XX.Y.Z-W/gcc-XX.V.U/libgo/go/net/http/server.go
> each returning a 404.
> 
> I have now clicked through quite a few links to source files, but
> have yet to find one that won't return a 404...?
> 
> Maybe the search index would need to be purged of source files that
> have disappeared (been updated) or something?

Thank you very much for the detailed bug report, and apologies for the
delay in getting back to you.

After further inspection, it turns out the tarball containing the
source for gcc-10 contains embedded tarballs. See
http://deb.debian.org/debian/pool/main/g/gcc-10/gcc-10_10.2.1.orig.tar.xz
and https://sources.debian.org/src/gcc-10/10.2.0-3/

Debsources unpacked the first tarball, and the embedded ones are
technically the "source" of gcc-10. The path you obtained from
codesearch.debian.net points to a file inside the tarball inside the
tarball; this is unfortunately not supported by sources.d.o.

I didn't know codesearch supported this feature. CCing Michael, in
case you have an idea on how not to point to sources.d.o for code
results originating from unpacked archives. :)

Cheers,
--
Matthieu

Attachment: signature.asc
Description: PGP signature

Reply via email to