On 2023-04-06 17:22, Alan Grimes wrote:
1. My system was basically working last time I updated it several
months ago.
2. Now both of my main web browsers are severely if not utterly foobar.
3. It required effort to change the system from the first state to the
second...
-> how much effort did it it take? =\
That said, the situation here was very stratge. I was looking for a
chance to insert some down time for the system to swap out the water
block on the CPU. I had gone out shopping and when I returned Chromium
had suddenly stopped working for reasons I can't fathom. Ok, so I took
the machine down and did the maintenance.
When I brought it back up, chromium was still foobar and I'm like
WTF...
Apparently it inserted trillions of crash reports in its log directory
and rm -rf'ing the crash reports alone is taking a very long time.
(HDD on that volume...)
On the build side, my pain list is as follows:
tortoise /var/tmp/portage # tree -L 2
.
├── dev-lang
│ └── ruby-3.1.4 << surprised as hell... no idea...
├── dev-ruby
│ [REDACTED]
│ ├── rubygems-3.4.6 << reports can't find variable "RUBY" even
though it is definitely set.
│ [REDACTED]
├── media-libs
│ └── nas-1.9.5 <<< wtf, don't care enough to examine it.
└── net-libs
├── signon-ui-0.15_p20171022-r1
└── webkit-gtk-2.40.0-r410 <<< apparently only user of Ruby no
idea what it does or why it's on my system.
Hi Alan,
Hope this helps. The `equery` tool has a "depends" argument which shows
packages depending on the atom argument. `equery depends webkit-gtk`
will show any current installed packages depending on it.
When I have a stale system to update, portage is always the first
package I worry about getting updated. Once that is updated start with
system packages and then world packages. But even with portage if there
are emerge errors I uninstall every package causing an error. In a
worst case, I have to go through the handbook and find the instructions
for installing as on a fresh install and install it,
https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Stage. In
portage's case, I have had to remove setuptools and certifi to get past
a dependency loop which was preventing portage from updating. Removing
as many packages as necessary generally helps. The packages can be
added back once the base components are updated.
Regards,
John
