On 6/9/19 1:38 PM, Dale wrote:
While I see that point and quite often it is a good idea, it could
also be that a fix is in the newer tree. It could even be that you
caught the tree in the middle of some sort of change and you missed
part of it.
If it were me, I'd try everything you can but if you can't find a
solution, I'd sync and see what happens. I've had a fresh sync fix
issues on a few occasions. It's somewhat rare but can happen.
Just a thought.
Your logic makes sense.
I actually did end up reluctantly doing that at one point when I
couldn't access my ZFS pool, which contained /usr/portage. So, an
emerge --sync was run to populate /usr/portage while attempting to fix ZFS.
I abandoned that line of work after a couple of hours and ended up
restoring my ZFS module backup from a few days prior. That got me
access to my ZFS pool again.
So, I'm disinclined to think that it's a bum copy of portage.
But, it is still a valid question to to ask.
