| 1 |
On Monday 17 September 2007 15:33:54 Mick wrote: |
| 2 |
> This is how I understood that is should work too. If for what ever reason |
| 3 |
> it doesn't rebuild the above packages itself, it should either say why |
| 4 |
> (e.g. keyword masked, Blocked, not in portage, etc.) and, or pass it on to |
| 5 |
> me to emerge/unmerge manually as required. I thought that invariably this |
| 6 |
> is how portage behave, hence this thread to resolve my confusion. Are we |
| 7 |
> in agreement that there is something wrong on this occasion - should I file |
| 8 |
> a bug? Or a 'feature request? Or wait until it happens again? |
| 9 |
|
| 10 |
Reading the full output you posted, I suspect I see the problem. |
| 11 |
# revdep-rebuild -X -p -v |
| 12 |
should be |
| 13 |
# revdep-rebuild -X -- -p -v |
| 14 |
|
| 15 |
The revdep-rebuild help doesn't say it does anything with a -p arguement to |
| 16 |
itself, but it may well do. The -- is a separator between revdep-rebuild |
| 17 |
arguements, and arguements it passes to emerge. |
| 18 |
|
| 19 |
-- |
| 20 |
Mike Williams |
| 21 |
-- |
| 22 |
gentoo-user@g.o mailing list |
Archives