On 1/29/26 1:39 AM, Dale wrote:
I masked that version and then tried again. That opened a can of worms. Let's deal with the problem below first. Maybe that will fix this. This resulted in a HUGE list of problems. I suspect this is either a tree problem, not the most likely thing, or a setting in /etc/portage somewhere, most likely.
It got warm here so I shut down the old rig. I was also ready to hit it, with a large hammer. A bit ago I booted it back up, cool at night at least. I started unmerging things and adjusting settings. I finally started trying to emerge some packages, like portage, so that I could do it in smaller increments. Then I got a interesting tidbit of info from emerge. The profile link was not set correctly. I can't recall exactly what it said but basically, it didn't have a profile to use. I used eselect to list the profiles, sure enough, none were selected. I also couldn't get it to set a profile either. I had to use ln -s to set it manually. Once I did that, it was able to upgrade, just a lot less packages since I removed a lot of stuff. LOL
So, somehow, the profile link was broken. No idea how since I haven't touched it in a while. Fixing that seems to have it working again. I'm not sure why eselect can't set it tho. I may still have something set wrong somewhere.
This also likely explains why I was having so much trouble syncing the tree as well. I'll know that next time I sync it I guess.
Thanks to all. Maybe it will chug along now. Dale :-) :-)
