I've just cleand up ~12 GB of /var/lib/apt/lists/partial/*.FAILED (on a 20GB
partition :-)) and I wonder what apt could do better in order to avoid similar
Some details: those *.FAILED files are due to hash mismatches when periodically
consulting httpredir.debian.org, due to unattended-upgrades cron job. Of course
the update failures there are not apt's fault. Most of the files seem to be
diffs to Packages, Sources, or Translation files, with the former dominating
disk space consumption.
OTOH, neither "apt-get clean" nor the daily apt cron job seem to clean up
*.FAILED files, that stay around for at least several months (I've seen in
there files as old as early September).
Maybe either, or both, of the clean action of apt and its cron job can be
modified to cater for cleaning up and avoiding filling the disk?
Many thanks in advance for your consideration, and for maintaining apt!
-- System Information:
Debian Release: 8.6
APT prefers stable
APT policy: (990, 'stable'), (500, 'stable-updates'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
Versions of packages apt depends on:
ii debian-archive-keyring 2014.3
ii gnupg 1.4.18-7+deb8u3
ii libapt-pkg4.12 126.96.36.199.3
ii libc6 2.19-18+deb8u6
ii libgcc1 1:4.9.2-10
ii libstdc++6 4.9.2-10
apt recommends no packages.
Versions of packages apt suggests:
pn apt-doc <none>
ii aptitude 0.6.11-1+b1
ii dpkg-dev 1.17.27
ii python-apt 0.9.3.12
-- no debconf information