#1142892 debootsnap/debrebuild cannot find linux-libc-dev:amd64=7.1.5-1

#1142892#5
Date:
2026-07-27 17:24:47 UTC
From:
To:
debootsnap/debrebuild cannot find the package below, needed to
reproduce a build via .buildinfo:

linux-libc-dev:amd64=7.1.5-1

Checked https://snapshot.debian.org/package/linux-libc-dev/7.1.5-1/
and the version is not listed there.

Encountered while running the salsa-ci "reproducible" pipeline job
for the 6tunnel package.

#1142892#10
Date:
2026-07-27 17:37:55 UTC
From:
To:
Control: tags -1 + moreinfo

There isn't an amd64 binary package for linux-libc-dev. It's
architecture-independent, so arch:all.

I'm assuming that's just a display issue, and that your failing build
is https://salsa.debian.org/damian/6tunnel/-/jobs/10019014

That build was run at 12:07. The amd64 build for src:linux version
7.1.5-1 finished at 11:37, so was quite possibly not in a location
where the salsa-ci job could find it at the time. If you retry the job
now, does it succeed?

That's because your URL form is wrong. The package needed there is a
source package, not a binary package.

https://snapshot.debian.org/package/linux/7.1.5-1/#linux-libc-dev_7.1.5-1
shows the package as expected.

I'm not seeing an issue with snapshot.debian.org in the above.

Regards,

Adam

#1142892#17
Date:
2026-07-27 19:57:03 UTC
From:
To:
* Adam D. Barratt <adam@adam-barratt.org.uk> [2026-07-27 18:37]:

The buildinfo files only contains the host architecture, not
architecture of the individual packages.

Yes, that's due to salsa-ci using incoming.d.o in the original build.
The issue is tracked here:

https://salsa.debian.org/salsa-ci-team/pipeline/-/work_items/587

I would propose to close this bug.

Cheers Jochen

#1142892#22
Date:
2026-07-27 21:02:20 UTC
From:
To:
Hi Adam and Jochen, Thanks for the clarification! I retried the job and it passed this time. THis confirms it was just a timing/propagation issue with the linux-libc-dev source package not yet being available on snapshot.debian.org at the moment the job ran, as you predicted.
I am closing this bug now.

Thanks again for looking into it,
Damian Daniel