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