| 1 |
On Sunday 01 March 2009 19:59:05 Grant wrote: |
| 2 |
> >> I'm getting more weird portage behavior and I don't see how to solve |
| 3 |
> >> this. I've tried un-emerging and re-emerging ffmpeg to no avail. |
| 4 |
> >> Please let me know if you have any ideas. |
| 5 |
> >> |
| 6 |
> >> # emerge -avDuN world |
| 7 |
> > |
| 8 |
> > ^ |
| 9 |
> > This |
| 10 |
> > entirely conflicts with |
| 11 |
> > |
| 12 |
> >> New USE are correctly set, but --newuse wasn't requested, so an |
| 13 |
> > |
| 14 |
> > ^^^^^^^^^^^^^^^^^^^^^^^^^ |
| 15 |
> > this. |
| 16 |
> > |
| 17 |
> > What version of portage are you on? Try mask it, downgrade, and try |
| 18 |
> > again. If that fixes, I strongly suspect you have uncovered a bug that |
| 19 |
> > needs reporting. |
| 20 |
> |
| 21 |
> I've tried portage-2.1.6.7 and 2.1.6.4 with the same results. |
| 22 |
|
| 23 |
OK. Meawhile Dirk spotted the overlay thing, which looks a likely candidate |
| 24 |
for the true cause |
| 25 |
|
| 26 |
-- |
| 27 |
alan dot mckinnon at gmail dot com |
Archives