| 1 |
>> I'm getting more weird portage behavior and I don't see how to solve |
| 2 |
>> this. I've tried un-emerging and re-emerging ffmpeg to no avail. |
| 3 |
>> Please let me know if you have any ideas. |
| 4 |
>> |
| 5 |
>> # emerge -avDuN world |
| 6 |
> ^ |
| 7 |
> This |
| 8 |
> entirely conflicts with |
| 9 |
> |
| 10 |
>> New USE are correctly set, but --newuse wasn't requested, so an |
| 11 |
> ^^^^^^^^^^^^^^^^^^^^^^^^^ |
| 12 |
> this. |
| 13 |
> |
| 14 |
> What version of portage are you on? Try mask it, downgrade, and try again. If |
| 15 |
> that fixes, I strongly suspect you have uncovered a bug that needs reporting. |
| 16 |
|
| 17 |
I've tried portage-2.1.6.7 and 2.1.6.4 with the same results. |
| 18 |
|
| 19 |
- Grant |
Archives