Re: [gentoo-user] Logic?

2023-04-07 Thread William Kenworthy
The rubygem / webkit problem has cropped up recently - do something like 
this


1. Mask webkit (I needed to do yelp as well on one system)

2. emerge any remaining updates so you can depclean

3. emerge --depclean (this removes old ruby versions and fixes the system

4. unmask webkit etc.

4. finish the updates.

BillK


On 7/4/23 17:31, John Acree wrote:

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







Re: [gentoo-user] Logic?

2023-04-07 Thread John Acree

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



Re: [gentoo-user] Logic?

2023-04-06 Thread Matt Connell
On Thu, 2023-04-06 at 17:22 -0400, 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.

https://en.wikipedia.org/wiki/Rolling_release



[gentoo-user] Logic?

2023-04-06 Thread Alan Grimes
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.


41 directories, 0 files
tortoise /var/tmp/portage #

The barf from ruby-3.1.4 is:

#

make[2]: Leaving directory 
'/var/tmp/portage/dev-lang/ruby-3.1.4/work/ruby-3.1.4'
make[2]: Entering directory 
'/var/tmp/portage/dev-lang/ruby-3.1.4/work/ruby-3.1.4'

:
make[2]: Leaving directory 
'/var/tmp/portage/dev-lang/ruby-3.1.4/work/ruby-3.1.4'
make -f exts.mk -Oline RUBY="./miniruby -I./lib -I. -I.ext/common " 
top_srcdir="." note

make[1]: Nothing to be done for 'note'.
>>> Source compiled.
>>> Test phase [not enabled]: dev-lang/ruby-3.1.4

>>> Install dev-lang/ruby-3.1.4 into 
/var/tmp/portage/dev-lang/ruby-3.1.4/image

 * Removing default gems before installation
make -j48 V=1 DESTDIR=/var/tmp/portage/dev-lang/ruby-3.1.4/image 
GEM_DESTDIR=/usr/lib64/ruby/gems/3.1.0 install

: > revision.tmp
    BASERUBY = /usr/bin/ruby --disable=gems
    CC = x86_64-pc-linux-gnu-gcc
    LD = x86_64-pc-linux-gnu-ld
    LDSHARED = x86_64-pc-linux-gnu-gcc -shared
    CFLAGS = -march=native -pipe -O3 -fno-strict-aliasing -fPIC
    XCFLAGS = -D_FORTIFY_SOURCE=2 -fstack-protector-strong 
-fno-strict-overflow -fvisibility=hidden -fexcess-precision=standard 
-DRUBY_EXPORT -I. -I.ext/include/x86_64-linux -I./include -I. 
-I./enc/unicode/13.0.0

    CPPFLAGS =
    DLDFLAGS = -Wl,-O1 -Wl,--as-needed 
-Wl,--compress-debug-sections=zlib -Wl,-soname,libruby31.so.3.1 
-fstack-protector-strong

    SOLIBS = -lz -lpthread -lrt -lrt -lgmp -ldl -lcrypt -lm
    LANG = en_US.utf8
    LC_ALL =
    LC_CTYPE =
    MFLAGS = -j48 -Oline 
--jobserver-auth=fifo:/var/tmp/portage/dev-lang/ruby-3.1.4/temp/GMfifo41 
--sync-mutex=fnm:/var/tmp/portage/dev-lang/ruby-3.1.4/temp/GmU4nvzS

x86_64-pc-linux-gnu-gcc (Gentoo 12.2.1_p20230304 p13) 12.2.1 20230304
Copyright (C) 2022 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

/usr/bin/ruby --disable=gems -C "." \
    -Itool/lib -rfileutils -rbundled_gem -answ \
    -e 'BEGIN {FileUtils.mkdir_p(d = ".bundle/gems")}' \
    -e 'gem, ver, _, rev = *$F' \
    -e 'next if !ver or /^#/=~gem' \
    -e 'g = "#{gem}-#{ver}"' \
    -e 'if File.directory?("#{d}/#{g}")' \
    -e 'elsif rev and File.exist?(gs = "gems/src/#{gem}/#{gem}.gemspec")' \
    -e   'BundledGem.copy(gs, ".bundle")' \
    -e 'else' \
    -e   'BundledGem.unpack("gems/#{g}.gem", ".bundle")' \
    -e 'end' \
    -e 'FileUtils.rm_rf("#{d}/#{g}/.github")' \
    gems/bundled_gems
/usr/lib64/ruby/3.1.0/rubygems.rb:15:in `require_relative': cannot load 
such file -- /usr/lib64/ruby/3.1.0/rubygems/compatibility (LoadError)

    from /usr/lib64/ruby/3.1.0/rubygems.rb:15:in `'
    from 
/var/tmp/portage/dev-lang/ruby-3.1.4/work/ruby-3.1.4/tool/lib/bundled_gem.rb:2:in 
`require'
    from 
/var/tmp/portage/dev-lang/ruby-3.1.4/work/ruby-3.1.4/tool/lib/bundled_gem.rb:2:in 
`'

    from -e:in `require'
make: *** [uncommon.mk:1370: extract-gems-sequential] Error 1
make: *** Waiting for unfinished jobs
/usr/bin/ruby --disable=gems ./tool/file2lastrev.rb -q --revision.h 
--srcdir="." > revision.tmp

./config.status --file=-:./template/ruby.pc.in | \
sed -e 's/\$(\([A-Za-z_][A-Za-z0-9_]*\))/${\1}/g' \
    -e 's|^prefix=.*|prefix=/usr|' \
    > ruby.tmp.pc
pkg_config=x86_64-pc-linux-gnu-pkg-config && PKG_CONFIG_PATH=. 
${pkg_config:-:} --print-errors ruby.tmp

mv -f ruby.tmp.pc ruby-3.1.pc
 * ERROR: dev-lang/ruby-3.1.4::gentoo failed (install phase):
 *   emake failed
 *
 * If you need support,