Quoting Лухнов Андрей Олегович (2018-12-19 17:49:01)
> apt is perfectly working inside that docker container.
>
> And the contents of /etc/apt/apt.conf.d/docker-clean is as follows:
>
> DPkg::Post-Invoke { "rm -f /var/cache/apt/archives/*.deb
> /var/cache/apt/archives/partial/*.deb /var/cache/apt/*.bin || true"; };
> APT::Update::Post-Invoke { "rm -f /var/cache/apt/archives/*.deb
> /var/cache/apt/archives/partial/*.deb /var/cache/apt/*.bin || true"; };
>
> Dir::Cache::pkgcache "";
> Dir::Cache::srcpkgcache "";
>
> So, apt is not broken either.What I call "broken" is an environment without a prepopulated apt cache - no matter if such environment is working fine for other uses of apt. Just for the record - see below... > I think, it worth to mention, that if I edit d-devlibdeps remove > --no-generate flag from apt-cache, everything works fine. interesting: The option is workaround for https://bugs.debian.org/630591 which is since fixed in apt. We can indeed drop that and have d-shlibs work also in arguably broken environment. Thanks a lot! - 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
