On donderdag 10 november 2022 03:42:36 CET Christoph Anton Mitterer wrote: > On Thu, 2022-11-10 at 03:37 +0100, Christoph Anton Mitterer wrote: > > $ ls -al 6.0.0-3-amd64/build 6.0.0-3-amd64/source > > lrwxrwxrwx 1 calestyo calestyo 36 Nov 5 14:41 6.0.0-3-amd64/build -> > > /usr/src/linux-headers-6.0.0-3-amd64 lrwxrwxrwx 1 calestyo calestyo 37 > > Nov 5 14:41 6.0.0-3-amd64/source -> > > /usr/src/linux-headers-6.0.0-3-common > The date of the symlinks is November the 5th, however I built the > custom kernel this night. https://tracker.debian.org/news/1381949/accepted-linux-607-1-source-into-unstable/ Shows that 6.0.0-3 was accepted into Unstable on Nov 5 ... > So there must have been something else that created them (dkms? - at > least not me personally)... or is there some date mangling somewhere > for making reproducible builds? https://tracker.debian.org/pkg/linux does say "Does not build reproducibly" But in the aforemention link you can also see this line: "Date: Sat, 05 Nov 2022 14:41:22 +0100" It _could_ be a coincidence, but I doubt it. So it looks like it's not fully reproducible (yet), but using that date is a step towards it. Getting (back) to the actual subject of the bug report, it seems quite likely that you also have linux-headers-X.Y.Z installed. And IIRC, it needs/creates those 'source' and 'build' dirs/links.
Attachment:
signature.asc
Description: This is a digitally signed message part.