Jake Moe wrote:
On 01/06/10 21:04, Neil Bothwick wrote:
On Tue, 01 Jun 2010 19:46:33 +1000, Jake Moe wrote:
My question is: is there a way that Portage can compare what's
currently on the hard disk with what it installed, and do some sort of
checksum verification on it?
Portage records a checksum for each file it installs, that's how it known
not to delete files that were not installed by the ebuild it is
unmerging. equery has an option to check packages against these
equery check --only-failures '*'
Note that it will show failures on any files that have been modified
since installation, such as configuration and data files, so you'll have
to check these manually, but if a library or executable shows up you
almost certainly have a problem.
Thanks for that Neil. Sounds like just what I need. However, when I
run it, I get:
j...@jhb5970 ~ $ equery check --only-failures '*'
!!! unknown local option --only-failures, ignoring
!!! Invalid Atom: ''
j...@jhb5970 ~ $ equery check '*'
!!! Invalid Atom: ''
j...@jhb5970 ~ $
Is the '*' atom spec a new Portage feature? I haven't switched to the
new Portage yet, I'm still using "stable". Maybe it's time I bite the
bullet and upgrade...
John Moe
I'm running the latest portage and the command worked fine here. I been
running the latest portage for a while and it works fine. May as well
upgrade and check out the new features.
Dale
:-) :-)
