| 1 |
On 01/06/10 21:04, Neil Bothwick wrote: |
| 2 |
> On Tue, 01 Jun 2010 19:46:33 +1000, Jake Moe wrote: |
| 3 |
> |
| 4 |
> |
| 5 |
>> My question is: is there a way that Portage can compare what's |
| 6 |
>> currently on the hard disk with what it installed, and do some sort of |
| 7 |
>> checksum verification on it? |
| 8 |
>> |
| 9 |
> Portage records a checksum for each file it installs, that's how it known |
| 10 |
> not to delete files that were not installed by the ebuild it is |
| 11 |
> unmerging. equery has an option to check packages against these |
| 12 |
> |
| 13 |
> equery check --only-failures '*' |
| 14 |
> |
| 15 |
> Note that it will show failures on any files that have been modified |
| 16 |
> since installation, such as configuration and data files, so you'll have |
| 17 |
> to check these manually, but if a library or executable shows up you |
| 18 |
> almost certainly have a problem. |
| 19 |
> |
| 20 |
> |
| 21 |
Thanks for that Neil. Sounds like just what I need. However, when I |
| 22 |
run it, I get: |
| 23 |
|
| 24 |
|
| 25 |
jmoe@jhb5970 ~ $ equery check --only-failures '*' |
| 26 |
!!! unknown local option --only-failures, ignoring |
| 27 |
!!! Invalid Atom: '' |
| 28 |
jmoe@jhb5970 ~ $ equery check '*' |
| 29 |
!!! Invalid Atom: '' |
| 30 |
jmoe@jhb5970 ~ $ |
| 31 |
|
| 32 |
|
| 33 |
Is the '*' atom spec a new Portage feature? I haven't switched to the |
| 34 |
new Portage yet, I'm still using "stable". Maybe it's time I bite the |
| 35 |
bullet and upgrade... |
| 36 |
|
| 37 |
John Moe |
Archives