On Fri, Aug 21, 2015 at 10:54:52PM +0100, Chris Lamb wrote:
> $ sudo apt-get update
> Get:1 http://mirror.dc15.debconf.org sid InRelease [215 kB]
> Get:2 http://mirror.dc15.debconf.org experimental InRelease [161 kB]
> Get:3 http://mirror.dc15.debconf.org sid/main Sources [10.4 MB]
> Get:4 http://mirror.dc15.debconf.org sid/main amd64 Packages [10.1 MB]
> Get:5 http://mirror.dc15.debconf.org experimental/main amd64 Packages
> [1157 kB]
> Fetched 22.0 MB in 4s (4550 kB/s)                      
> Reading package lists... Done
> W: Size of file
> /var/lib/apt/lists/mirror.dc15.debconf.org_debian_dists_sid_main_source_Sources.gz
> is not what the server reported 10394726 10402082
> W: Size of file
> /var/lib/apt/lists/mirror.dc15.debconf.org_debian_dists_sid_main_binary-amd64_Packages.gz
> is not what the server reported 10057069 10057260

(These warnings are… strange. Didn't you wonder about them?)


> $ sudo apt-get install -t experimental apt
> [..]
> Setting up libapt-pkg5.0:amd64 (1.1~exp9) ...
> Setting up apt (1.1~exp9) ...
> Installing new version of config file /etc/apt/apt.conf.d/01autoremove
> ...
> Installing new version of config file /etc/cron.daily/apt ...
> Processing triggers for libc-bin (2.19-19) ...
> 
> $ sudo apt-get update
> Hit:1 http://mirror.dc15.debconf.org/debian sid InRelease
> Hit:2 http://mirror.dc15.debconf.org/debian experimental InRelease
> Reading package lists... Error!
> E: Unable to create caches as file usage is disabled, but memory not
> allowed either!
> E: The package lists or status file could not be parsed or opened.

The bugscript would have asked you for your configuration, so I am going
to do it now instead: "apt-config dump".

The message itself comes (or at least should) in response to
Dir::Cache::pkgcache and Dir::Cache::srcpkgcache being empty and if the
cache is forbidden to be build entirely in memory – which is the case
for apt running as root for, well, reasons. I guess we should drop this,
even through keeping everything in memory can be very slow… (I will have
to recheck tomorrow if I haven't changed the semantics with my recent
rewrite of the cache building. What I said is what happen in
/experimental currently, I might have messed up the semantics…)

You could try "-o Debug::NoLocking=1" btw, which should cause even root
to use an entirely memory based cache. It does disable all locking
through, so avoid running multiple apt/dpkg instances in the meantime…


Best regards

David Kalnischkies

Attachment: signature.asc
Description: Digital signature

Reply via email to