Quoting Chris Lamb (2016-06-29 18:24:13) >> this failure is most likely because your build environment is buggy > > It's always a fresh, clean container image that I recreate entirely > (not dist-upgrade) at 07:00 UTC on my laptop from the latest sid. I > run build-dep and then build with debuild; nothing special.
I believe that you do not expect your environment to be _too_ special, but highly suspect that you have applied some optimizations over, say, running debian-installer from bare metal for each and every build. Can you try add an "apt update" in the build environment before building the package, and see if it still fails? > Other systems -- including the reproducible builds servers -- can > reproduce the FTBFS, so I am not convinced at this point that my > environment is buggy. Where do you see that? The log currently linked from tracker.debian.org was another issue (since fixed in CDBS). >> apt-file initializes its database when installed, and d-shlibs rely >> on that. > > Ah, smells like the bug is there - d-shlibs does not depend on apt-file [...] Sorry, not apt-file but apt-cache. What d-shlibs rely on is an up-to-date APT cache (it calls "apt-cache --no-generate due to bug#630591 - which seems a no-op since ages but shouldn't fail either). - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
