Quoting Andrey Gursky (2016-11-13 21:09:59) > On Sun, 13 Nov 2016 20:39:44 +0100 Andrey Gursky wrote: > > On Sun, 13 Nov 2016 20:18:27 +0100 Jonas Smedegaard wrote: > > > Quoting Andrey Gursky (2016-11-13 19:46:07) > > > > few hours ago I successfully built pjproject locally. Now it fails > > > > similarly to [1]. After googling I've found this 5-years old bug. And > > > > indeed "apt-get update" fixed the issue. But only until next time it > > > > fails again if I forget to run "apt-get update" (as root) before > > > > building a package (as user). > > > > > > Suggestions for eliminating that need is much appreciated. > > > > > > I suspect this bug is related to (arguably too optimized?) bootstrapping > > > routines for build environments. > > > > > > I never experienced that issue myself. I use cowbuilder. > > > > > > Feel free to use this bugreport to share details on build environments > > > (even though I will likely not take much part in that): If that > > > suspicion turns out to have some merit, we can reassign this bugreport > > > to the relevant bootstrapping tool. > > > > It failed on my working system, where I'm building with dpkg-buildpackage. > > Tried to recall my last actions with package system. And now I know how > to reproduce it. It is enough to install the same version or update or > downgrade a package from a local file with "dpkg -i". And besides of > "apt-get update" it is enough to open/close aptitude to make d-shlibs > work again.
Ah, if aptitude updates apt-cache, then that explains my not running into this issue: I quite often use aptitude. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
