On 2/28/26 9:37 PM, Dale wrote:
On 2/28/26 6:19 PM, Michael wrote:
On Saturday, 28 February 2026 12:42:47 Greenwich Mean Time Dale wrote:
So, somehow, the profile link was broken. No idea how since I haven't
touched it in a while.
Hmm ... time for fsck and 'smartctl -t long' in case you have a fs or
drive
problem?
Honestly, I was thinking the same thing. It got warm today so I shut
the rig down. I'm about to reboot it. May start the test. I think
that hard drive is like 160GB or something.
I got the rig booted and ran a selftest. It passed. No errors or
anything. That's good I guess. I think the drive is like 15 years
old. Still works tho.
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.
Did you perchance uninstall app-admin/eselect? I think eselect
profile is not
a separate eselect module.
I can't imagine why I would. I admit, I did unmerge a ton of QT and
KDE packages, plus Seamonkey and Gimp. I didn't unmerge any system
type packages tho. Most of what I unmerged was GUI related packages.
What confused me tho, it was complaining about python exec or
something. I think that was in the original post. That was confusing
as all that was installed. Python had to be working because emerge
was working. I seem to recall emerge being a python based command.
About to restart and see if it goes any further. Biggest problem is
I'm running low on /var space. You might recall, for some reason the
file system won't enlarge after expanding the LVM space. Yea, that
rig. Part of me is thinking about reinstalling it again. It is a
really old install. It could use some rearranging file
system/partition wise.
Dale
:-) :-)
Well, after it passed the self test and I got /var resized, I tried
emerge -auDN world again. One package failed complaining about not
having dbus in the error log. I recalled umerging dbus and when I
double checked, it was not installed. I installed it again and as I
type, it is compiling away. I'm not sure why emerge didn't notice it
needed dbus and emerged that first tho. It should have noticed that I'd
think. Anyway, the error gave me the clue and I think it is going to
work now.
I still have no idea how the profile got messed up. I also don't
understand why eselect could not set it correctly either. Still, it
seems to be working. Maybe when it is done I can try it again. Maybe I
did unmerge some package that eselect needs. Now to hope this completes
without any more problems.
Oh, anyone notice emerge has a new feature? It now spits this out, a LOT.
--- /var/tmp/portage has insufficient free space, emerge job parallelism
reduced. free: 40.73 GiB, required 41.10 GiB
Just so folks are aware, you can't outrun it. I expanded the file
system twice and it just raises the limit higher again. Basically,
unless you set it to some huge amount, I think it is going to complain a
bit. I think the dev is going to have to take user feedback and figure
out how to tweak it. I think it is a good idea but just needs a little
help with its counting. LOL It doesn't stop the emerge tho. It keeps
going. Maybe over time it will get improved. Oh, you can disable it.
You add --jobs-tmpdir-require-free-gb 0 to either the command line or
the emerge options in make.conf. Again, it doesn't stop emerge so I'd
leave it. I think the devs will work this out with improvements until
it works better. It can also be a good thing. If I understand this
correctly, it will hold larger jobs if needed so that it doesn't run out
of drive space or memory if using tmpfs. I'm going to be patient as it
doesn't stop anything. Forum link.
https://forums.gentoo.org/viewtopic-t-1176493-start-0-postdays-0-postorder-asc-highlight-.html
Well, the old rig is still compiling away. It's slow but it gets
there. I may put in a larger hard drive. I got some 250GB drives and
it will give me a little more than the 160GB that the current one has.
I dunno.
https://forums.gentoo.org/viewtopic-t-1176493-start-0-postdays-0-postorder-asc-highlight-.html
Dale
:-) :-)
