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