| 1 |
On Wednesday 06 Jul 2011 10:51:20 Neil Bothwick wrote: |
| 2 |
> On Wed, 6 Jul 2011 10:36:40 +0100, Peter Ruskin wrote: |
| 3 |
> > > It sounds like you need to start with qcheck -aBT and trawl |
| 4 |
> > > through the output, re-emerging anything questionable. |
| 5 |
> > |
| 6 |
> > I don't think I trust the output of that: |
| 7 |
> > |
| 8 |
> > # qcheck -aBT |
| 9 |
> |
| 10 |
> [big snip] |
| 11 |
> |
| 12 |
> It produces false positives and you need to look at the output for each |
| 13 |
> affected package, but do you know a better way of detecting corruption |
| 14 |
> of installed files? |
| 15 |
|
| 16 |
I wasn't familiar with qcheck (yes, I know, I lead a sheltered life!) but |
| 17 |
adding --verbose does not reveal additional info. When you say "look at the |
| 18 |
output", do you mean the output of emerge -1aDv <package> ? |
| 19 |
-- |
| 20 |
Regards, |
| 21 |
Mick |
Archives