[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#661947: marked as done (apt-get clean deletes /var/cache/apt/*.bin)

Your message dated Fri, 14 Aug 2015 10:05:09 +0200
with message-id <20150814080509.GA11109@crossbow>
and subject line Re: apt-get clean deletes /var/cache/apt/*.bin
has caused the Debian Bug report #661947,
regarding apt-get clean deletes /var/cache/apt/*.bin
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
661947: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661947
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: apt
Version: 0.8.15.9
Severity: normal

when i run apt-get clean, it deletes the files /var/cache/apt/pkgcache.bin and
/var/cache/apt/srcpkgcache.bin.

this also applies to the version in experimental (0.8.16~exp12), but the
version in squeeze (0.8.10.3+squeeze1) doesn't exhibit this behavior.

is this an intentional change? 

removing *.bin causes some issues with copy-on-write root filesystems,
needlessly recreating the *.bin files, though i'm able to reproduce the
behavior on several fairly conventional installs as well.

thanks for the exellence that is apt!

live well,
  vagrant

--- End Message ---
--- Begin Message --- 
On Mon, Mar 12, 2012 at 09:34:58PM +0400, sergio wrote:
> Clean is suitable to run after dist-upgrade as update before.
> No one will say update after clean for create caches back.

Any apt command will recreate the caches, not just update. On the other
hand, if the caches exist all commands will use it and if it is corrupt
they all will crash.

btw: At least the pkgcache is invalid after a dist-upgrade anyway.

If you want a command which just regenerates the caches to ensure they
are recent, try "apt-cache gencaches", but as said, any apt command
needing them will do that implicitely.


> If anyone wants to repair corrupted cache, there are update.

Corrupted caches result in segfaults. People do random things then they
encounter a segfault. Most browse the web and the first thing suggested
there is 'apt-get clean' as that helps with all sorts of problems.  It
is also consistent with other comments which use the clean subcommand to
remove intermediate files which can easily be regenerated if need be,
like make, git, ….

So, not a bug, but a feature/working as designed. Hence closing.


Best regards

David Kalnischkies

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: