[gentoo-user] Libsld, what gives?

[gentoo-user] Libsld, what gives?

[Alan Grimes]

Even though only 45 days have passed since my last update, I felt like 
doing one tonight. Usually I should wait six months just to save myself 
the aggrivation...  (I'm looking to set up a local bitcoin wallet 
because the exchanges are not to be trusted anymore...)

Naturally nothnig worked because, hey, this is gentoo....  (My system 
was * * * * *  perfect after the update 45 days ago...)

I'm jackhammering the system now and I'm getting about 50% error spew 
and 50% successful install... Hopefully my list of out of date packages 
will begin to wane soon and the deeper issues will be exposed. If I just 
say "hey what do you need to update everything" it barfs with only the 
following:

my best guess is that the penguins are dropping dead after poisoning 
themselves with the fake vaccine and making a mess of things as they go 
down. =\


tortoise ~ # ./pretendupdate

These are the packages that would be merged, in order:

Calculating dependencies... done!

emerge: there are no ebuilds to satisfy 
"media-libs/libsdl2[abi_x86_32?,alsa?,custom-cflags?,joystick?,nas?,opengl?,oss?,pulseaudio?,sound?,static-libs?,video?,X?]".
(dependency required by "media-libs/libsdl-1.2.60::poly-c" [ebuild])
(dependency required by "dev-libs/zziplib-0.13.72-r2::gentoo[sdl]" [ebuild])
(dependency required by "app-text/texlive-core-2021-r4::gentoo" [installed])
(dependency required by "dev-texlive/texlive-formatsextra-2021::gentoo" 
[installed])
(dependency required by 
"app-text/docbook-sgml-utils-0.6.14-r5::gentoo[jadetex]" [installed])
(dependency required by "gnome-extra/gnome-color-manager-3.36.0::gentoo" 
[installed])
(dependency required by "gnome-base/gnome-control-center-43.1::gentoo" 
[ebuild])
(dependency required by "gnome-base/gnome-shell-42.5-r2::gentoo" [ebuild])
(dependency required by 
"gnome-extra/gnome-browser-connector-42.1::gentoo" [ebuild])

  * IMPORTANT: 2 news items need reading for repository 'gentoo'.
  * Use eselect news read to view new items.

tortoise ~ #

-- 
Beware of Zombies. =O
#EggCrisis  #BlackWinter
White is the new Kulak.
Powers are not rights.

[gentoo-user] Re: Libsld, what gives?

[Grant Edwards]

On 2022-11-16, Alan Grimes <alonzotg@verizon.net> wrote:

> Even though only 45 days have passed since my last update, I felt
> like doing one tonight. Usually I should wait six months just to
> save myself the aggrivation...  (I'm looking to set up a local
> bitcoin wallet because the exchanges are not to be trusted
> anymore...)
>
> Naturally nothnig worked because, hey, this is gentoo....

One wonders why you continue to run Gentoo, since it's so awful and
you hate it so much.

--
Grant

RE: [gentoo-user] Re: Libsld, what gives?

[Laurence Perkins]

> -----Original Message-----
> From: Grant Edwards <grant.b.edwards@gmail.com> 
> Sent: Wednesday, November 16, 2022 6:01 AM
> To: gentoo-user@lists.gentoo.org
> Subject: [gentoo-user] Re: Libsld, what gives?
> 
> On 2022-11-16, Alan Grimes <alonzotg@verizon.net> wrote:
> 
> > Even though only 45 days have passed since my last update, I felt like 
> > doing one tonight. Usually I should wait six months just to save 
> > myself the aggrivation...  (I'm looking to set up a local bitcoin 
> > wallet because the exchanges are not to be trusted
> > anymore...)
> >
> > Naturally nothnig worked because, hey, this is gentoo....
> 
> One wonders why you continue to run Gentoo, since it's so awful and you hate it so much.
> 
> --
> Grant
> 

Because it's the only thing that lets him make all the esoteric customizations he wants.  I have a brother who has the same kinds of troubles just about as often.  He just also knows that it's because he wants to compile everything with LLVM/Clang.

Unfortunately, the package manager that can account for everything the user might possibly have changed and make it compile anyway is still a work in progress.

LMP

Re: [gentoo-user] Re: Libsld, what gives?

[Peter Humphrey]

On Wednesday, 16 November 2022 14:00:36 GMT Grant Edwards wrote:
> On 2022-11-16, Alan Grimes <alonzotg@verizon.net> wrote:
> > Even though only 45 days have passed since my last update, I felt
> > like doing one tonight. Usually I should wait six months just to
> > save myself the aggrivation...  (I'm looking to set up a local
> > bitcoin wallet because the exchanges are not to be trusted
> > anymore...)
> > 
> > Naturally nothnig worked because, hey, this is gentoo....
> 
> One wonders why you continue to run Gentoo, since it's so awful and
> you hate it so much.

And I wonder why anyone bothers answering him.

Let him stew in his own juice.

-- 
Regards,
Peter.

Re: [gentoo-user] Libsld, what gives?

[Andreas Fink]

On Wed, 16 Nov 2022 02:11:18 -0500
Alan Grimes <alonzotg@verizon.net> wrote:

> I'm jackhammering the system now and I'm getting about 50% error spew
I would suggest a different tool than a jackhammer to fix the problems.

RE: [gentoo-user] Libsld, what gives?

[Laurence Perkins]

>-----Original Message-----
>From: Andreas Fink <finkandreas@web.de> 
>Sent: Wednesday, November 16, 2022 6:59 AM
>To: gentoo-user@lists.gentoo.org
>Subject: Re: [gentoo-user] Libsld, what gives?
>
>On Wed, 16 Nov 2022 02:11:18 -0500
>Alan Grimes <alonzotg@verizon.net> wrote:
>
>> I'm jackhammering the system now and I'm getting about 50% error spew
>I would suggest a different tool than a jackhammer to fix the problems.
>
>
A machete is a much better choice usually.  Chop out all the weeds like poorly-maintained overlays, programs you don't use any more, and (in extremity) the virtuals and perl.

Trying to go deep first and fix the core with all the brush and rubbish still cluttering up the top is usually an exercise in frustration and a good way to have some errant twig poke you in the eye repeatedly.

LMP

Re: [gentoo-user] Libsld, what gives?

[Alan Grimes]

Andreas Fink wrote:
> On Wed, 16 Nov 2022 02:11:18 -0500
> Alan Grimes <alonzotg@verizon.net> wrote:
>
>> I'm jackhammering the system now and I'm getting about 50% error spew
> I would suggest a different tool than a jackhammer to fix the problems.

Basic assumption: Problems are caused by outdated packages.
Underlying problem: In order to break a log-jam it is necessary to purge 
outdated packages.
Facts on the ground: The only way to make ANY progress in updating 
outdated packages is to jackhammer the hell out of all packages in hopes 
that some of them might sucessfully update which will, hopefully either:

A. allow other packages to sucessfully update
B. Expose something that can be fixed.

Once the logjam is broken, the system is then --emptytree world'ed and 
declared healthy... Expected failure rate is on the order of 0.3% of 
hopefully unimportant packages.

It is known that the KDE group of packages has incomplete dependency 
graph because it is hopelessly convoluted, and it always causes problems 
and the only way to break through it is the jackhammer approach.

LLVM and friends also fails to update when updating within a single slot 
and this is VERY annoying...

What causes me to post to the list is when I get failures that prevent 
me from even beginning to jackhammer the system.

-- 
Beware of Zombies. =O
#EggCrisis  #BlackWinter
White is the new Kulak.
Powers are not rights.

RE: [gentoo-user] Libsld, what gives?

[Laurence Perkins]

>-----Original Message-----
>From: Alan Grimes <alonzotg@verizon.net> 
>Sent: Wednesday, November 16, 2022 8:18 AM
>To: gentoo-user@lists.gentoo.org; Andreas Fink <finkandreas@web.de>
>Subject: Re: [gentoo-user] Libsld, what gives?
>
>Andreas Fink wrote:
>> On Wed, 16 Nov 2022 02:11:18 -0500
>> Alan Grimes <alonzotg@verizon.net> wrote:
>>
>>> I'm jackhammering the system now and I'm getting about 50% error spew
>> I would suggest a different tool than a jackhammer to fix the problems.
>
>Basic assumption: Problems are caused by outdated packages.
>Underlying problem: In order to break a log-jam it is necessary to purge outdated packages.
>Facts on the ground: The only way to make ANY progress in updating outdated packages is to jackhammer the hell out of all packages in hopes that some of them might sucessfully update which will, hopefully either:
>
>A. allow other packages to sucessfully update B. Expose something that can be fixed.
>
>Once the logjam is broken, the system is then --emptytree world'ed and declared healthy... Expected failure rate is on the order of 0.3% of hopefully unimportant packages.
>
>It is known that the KDE group of packages has incomplete dependency graph because it is hopelessly convoluted, and it always causes problems and the only way to break through it is the jackhammer approach.
>
>LLVM and friends also fails to update when updating within a single slot and this is VERY annoying...
>
>What causes me to post to the list is when I get failures that prevent me from even beginning to jackhammer the system.
>
>--
>Beware of Zombies. =O
>#EggCrisis  #BlackWinter
>White is the new Kulak.
>Powers are not rights.
>

If you're going to try to dig all the way to the bottom first then --ignore-world and --ignore-built-slot-operator-deps can be helpful for forcing it to build what it needs to break a dependency loop.  But do be aware that things may cease to function during the intermediate stages.

If those are not sufficiently strong, then you can climb into the package repo and start issuing ebuild commands yourself and it will do what it's told without bothering about checking dependencies at all.  Make sure you know what you're doing...  Obviously...

But seriously, try disabling any overlays first if at all possible.  It's quite common for those to lag behind the main repo and turn things into a tangled mess.  

An expected failure rate "on the order of" 0.3% means you expect it to be no less than 0.03% and no more than 30%...  So I think you're probably already within that envelope.  :D

LMP

Re: [gentoo-user] Libsld, what gives?

[Alan Grimes]

Laurence Perkins wrote:
>> If you're going to try to dig all the way to the bottom first then --ignore-world and --ignore-built-slot-operator-deps can be helpful for forcing it to build what it needs to break a dependency loop.  But do be aware that things may cease to function during the intermediate stages.
>>
>> If those are not sufficiently strong, then you can climb into the package repo and start issuing ebuild commands yourself and it will do what it's told without bothering about checking dependencies at all.  Make sure you know what you're doing...  Obviously...
>>
>> But seriously, try disabling any overlays first if at all possible.  It's quite common for those to lag behind the main repo and turn things into a tangled mess.

At this point the jackhammers have gone silent and I'm left with the 
issue I had before:


tortoise ~ # emerge --update --newuse --deep --with-bdeps=y world 
--verbose --backtrack=40 --changed-deps --verbose-conflicts --pretend 
--ignore-built-slot-operator-deps=y

These are the packages that would be merged, in order:

Calculating dependencies... done!

emerge: there are no ebuilds to satisfy 
"media-libs/libsdl2[abi_x86_32?,alsa?,custom-cflags?,joystick?,nas?,opengl?,oss?,pulseaudio?,sound?,static-libs?,video?,X?]".
(dependency required by "media-libs/libsdl-1.2.60::poly-c" [ebuild])
(dependency required by "dev-libs/zziplib-0.13.72-r2::gentoo[sdl]" [ebuild])
(dependency required by "app-text/texlive-core-2021-r4::gentoo" [installed])
(dependency required by "dev-texlive/texlive-formatsextra-2021::gentoo" 
[installed])
(dependency required by 
"app-text/docbook-sgml-utils-0.6.14-r5::gentoo[jadetex]" [installed])
(dependency required by "gnome-extra/gnome-color-manager-3.36.0::gentoo" 
[installed])
(dependency required by "gnome-base/gnome-control-center-43.1::gentoo" 
[installed])
(dependency required by "gnome-base/gnome-shell-42.5-r2::gentoo" 
[installed])
(dependency required by 
"gnome-extra/gnome-browser-connector-42.1::gentoo" [ebuild])
tortoise ~ #


I then checked my overlays, and it turns out I had an outrageously 
bloated number of layers installed:

tortoise ~ # layman -l

  * poly-c                    [Rsync     ] 
(rsync://rsync.gentoofan.org/poly-c )
  * wichtounet                [Git       ] 
(https://github.com/wichtounet/wichtounet-overlay.git )

tortoise ~ #
#############################

I think one of those was because mainline had stopped maintaining 
seamnokey and I needed it maintained. No idea what I was smoking when I 
applied the other or even which is which. In all likelyhood I had a 
problem and applying that overlay solved it and because I didn't have a 
problem after solving said problem, I forgot about it and can't really 
say what or even when it was I had that problem. All I have now is this 
lingering sense that touching those overlays will result in misery and 
suffering so it's best not to even look up how to remove either of them.

eclan still shows a large number of outdated packages on the system so 
there is definitely lots of updating to work if I can get emerge out of 
its current hissy-fit.

tortoise ~ # eclean-dist
  * Building file list for distfiles cleaning...
  * ERROR: games-strategy/boswars-9999::poly-c failed (depend phase):
  *   EAPI 6 unsupported.
  *
  * Call stack:
  *             ebuild.sh, line 614:  Called source 
'/var/lib/layman/poly-c/games-strategy/boswars/boswars-9999.ebuild'
  *   boswars-9999.ebuild, line   7:  Called inherit 'desktop' 
'scons-utils' 'subversion'
  *             ebuild.sh, line 294:  Called __qa_source 
'/usr/portage/eclass/scons-utils.eclass'
  *             ebuild.sh, line 109:  Called source 
'/usr/portage/eclass/scons-utils.eclass'
  *    scons-utils.eclass, line  89:  Called die
  * The specific snippet of code:
  *      *) die "EAPI ${EAPI} unsupported."
  *
  * If you need support, post the output of `emerge --info 
'=games-strategy/boswars-9999::poly-c'`,
  * the complete build log and the output of `emerge -pqv 
'=games-strategy/boswars-9999::poly-c'`.
  * Working directory: '/usr/lib/python3.10/site-packages'
  * S: '/var/tmp/portage/games-strategy/boswars-9999/work/boswars-9999'
  * Cleaning distfiles...
  [    1.7 M ] frameworkintegration-5.98.0.tar.xz
  [   86.9 K ] kaccounts-integration-22.08.1.tar.xz
  [   63.1 K ] kaccounts-providers-22.08.1.tar.xz
  [   71.8 K ] kactivities-5.98.0.tar.xz
  [   88.9 K ] kauth-5.98.0.tar.xz
  [  127.0 K ] kbookmarks-5.98.0.tar.xz
  [  185.0 K ] kcmutils-5.98.0.tar.xz
  [  121.6 K ] kcompletion-5.98.0.tar.xz
  [   27.7 K ] kcrash-5.98.0.tar.xz
  [  202.3 K ] kdeclarative-5.98.0.tar.xz
  [   38.6 K ] kded-5.98.0.tar.xz
  [    3.5 M ] kdelibs4support-5.98.0.tar.xz
  [  430.4 K ] kdoctools-5.98.0.tar.xz
  [    1.6 M ] kemoticons-5.98.0.tar.xz
  [   94.9 K ] kglobalaccel-5.98.0.tar.xz
  [   72.1 K ] kguiaddons-5.98.0.tar.xz
  [    1.9 M ] khtml-5.98.0.tar.xz
  [  116.7 K ] kinit-5.98.0.tar.xz
  [  331.3 K ] kjs-5.98.0.tar.xz
  [   85.4 K ] knotifyconfig-5.98.0.tar.xz
  [  192.2 K ] kparts-5.98.0.tar.xz
  [  126.4 K ] kross-5.98.0.tar.xz
  [   85.7 K ] krunner-5.98.0.tar.xz
  [  262.6 K ] kservice-5.98.0.tar.xz
  [  320.6 K ] ktextwidgets-5.98.0.tar.xz
  [  878.1 K ] kunitconversion-5.98.0.tar.xz
  [  325.1 K ] kwallet-5.98.0.tar.xz
  [  882.2 K ] kxmlgui-5.98.0.tar.xz
  [  170.8 K ] purpose-5.98.0.tar.xz
  [   64.8 K ] qqc2-desktop-style-5.98.0.tar.xz
  ===========
  [   14.0 M ] Total space from 30 files were freed in the distfiles 
directory

    The following unavailable installed packages were found
              app-arch/upx-3.96-r2
              app-arch/zip-3.0-r5
              dev-cpp/rapidfuzz-cpp-1.7.0
              dev-lang/go-1.19.1
              dev-lang/python-2.7.18_p15-r1
              dev-libs/jansson-2.14
              dev-libs/kpathsea-6.3.3_p20210325
              dev-libs/libfmt-7.1.3
              dev-libs/libgdata-0.18.1
              dev-libs/libgusb-0.4.0
              dev-libs/libsodium-1.0.18
              dev-libs/serd-0.30.14-r1
              dev-libs/sord-0.16.12-r1
              dev-lua/luajson-1.3.4-r100
              dev-python/Levenshtein-0.20.5
              dev-python/aiohttp-3.8.3
              dev-python/distro-1.7.0
              dev-python/hatch-fancy-pypi-readme-22.7.0
              dev-python/mypy_extensions-0.4.3-r1
              dev-python/pillow-9.2.0
              dev-python/poetry-core-1.2.0
              dev-python/pytz-2022.2.1
              dev-python/rapidfuzz-2.10.2
              dev-python/twisted-22.8.0
              dev-util/byacc-20220128
              dev-util/opencl-headers-2022.09.23
              gnome-base/gnome-settings-daemon-42.2-r3
              gnome-base/gvfs-1.50.2
              gnome-extra/gnome-browser-connector-42.0
              kde-frameworks/kcalendarcore-5.98.0
              kde-frameworks/kdnssd-5.98.0
              kde-frameworks/kholidays-5.98.0
              kde-frameworks/kplotting-5.98.0
              kde-frameworks/kquickcharts-5.98.0
              mail-mta/ssmtp-2.64-r4
              media-gfx/mypaint-brushes-2.0.2
              media-libs/dssi-1.1.1-r1
              media-libs/ftgl-2.1.3_rc5
              media-libs/libquicktime-1.2.4-r3
              media-libs/libvpx-1.12.0
              media-libs/lilv-0.24.18-r1
              media-libs/raptor-2.0.15-r6
              media-libs/suil-0.10.16-r1
              media-video/pipewire-0.3.59
              net-libs/libaccounts-glib-1.26
              net-libs/libotr-4.1.1
              net-libs/libsignon-glib-2.1-r1
              net-libs/telepathy-logger-qt-17.09.0
              net-libs/telepathy-qt-0.9.8-r1
              net-misc/freerdp-2.8.0
              sys-apps/hwdata-0.362
              sys-devel/autoconf-2.13-r3
              sys-devel/clang-runtime-15.0.1 ...distfile name(s) not 
known/saved
              sys-devel/clang-toolchain-symlinks-15-r1 ...distfile 
name(s) not known/saved
              sys-fs/lvm2-2.03.16_pre
              sys-fs/mtools-4.0.41
              sys-kernel/vanilla-sources-5.19.12
              sys-kernel/vanilla-sources-5.19.8
              sys-libs/compiler-rt-15.0.1
              sys-libs/compiler-rt-sanitizers-15.0.1
              x11-base/xorg-x11-7.4-r3 ...distfile name(s) not known/saved

tortoise ~ #

Hmm, poly-c is looking like it's a common factor here.




-- 
Beware of Zombies. =O
#EggCrisis  #BlackWinter
White is the new Kulak.
Powers are not rights.

RE: [gentoo-user] Libsld, what gives?

[Laurence Perkins]

>tortoise ~ # eclean-dist
>  * Building file list for distfiles cleaning...
>  * ERROR: games-strategy/boswars-9999::poly-c failed (depend phase):
>  *   EAPI 6 unsupported.

Possibly also need to upgrade portage and/or gentoolkit first.  That's usually a good idea regardless.

>Hmm, poly-c is looking like it's a common factor here.
>
>

Overlays can go stale, even if they were previously necessary to fix something.  For long-term use pulling just the ebuilds you need into your own overlay often works out better.

LMP

Re: [gentoo-user] Libsld, what gives?

[Michael Cook]

On 11/16/22 19:18, Laurence Perkins wrote:
>
>> tortoise ~ # eclean-dist
>>   * Building file list for distfiles cleaning...
>>   * ERROR: games-strategy/boswars-9999::poly-c failed (depend phase):
>>   *   EAPI 6 unsupported.
> Possibly also need to upgrade portage and/or gentoolkit first.  That's usually a good idea regardless.
>
>> Hmm, poly-c is looking like it's a common factor here.
>>
>>
> Overlays can go stale, even if they were previously necessary to fix something.  For long-term use pulling just the ebuilds you need into your own overlay often works out better.
>
> LMP

Personally I just mask the overlay and unmask what I need. If something 
breaks, I look into fixing it. Upgrading rather frequently seems to 
limit this, just maintain the system. Waiting months and then having to 
deal with tons of changes and an overlay going dead (I don't think 
poly-c exists anymore?) is way worse.

Re: [gentoo-user] Libsld, what gives?

[Julien Roy]

[-- Attachment #1: Type: text/plain, Size: 299 bytes --]

Alan Grimes <alonzotg@verizon.net> writes:

> (dependency required by "media-libs/libsdl-1.2.60::poly-c" [ebuild])

This ebuild is from a different overlay, it's probably not helping. The
first thing I'd try is disabling the overlay to see if this is the cause
of the problem.

-- 
Julien

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 617 bytes --]

Re: [gentoo-user] Libsld, what gives?

[Paul Colquhoun]

[-- Attachment #1: Type: text/plain, Size: 588 bytes --]

On Wednesday, November 16, 2022 6:11:18 P.M. AEDT Alan Grimes wrote:
> Even though only 45 days have passed since my last update, I felt like
> doing one tonight. Usually I should wait six months just to save myself
> the aggrivation...

No, waiting 6 months between updates *causes* aggrivation.

Try updateing on a regular schedule, at 1 or 2 week intervals, and see if 
your experience improves.


-- 
Reverend Paul Colquhoun, ULC.     http://andor.dropbear.id.au/
  Asking for technical help in newsgroups?  Read this first:
     http://catb.org/~esr/faqs/smart-questions.html#intro


[-- Attachment #2: Type: text/html, Size: 1522 bytes --]

Re: [gentoo-user] Libsld, what gives?

[Dr Rainer Woitok]

Paul,

On Thursday, 2022-11-17 17:52:17 +1100, you wrote:

> On Wednesday, November 16, 2022 6:11:18 P.M. AEDT Alan Grimes wrote:
> > ...
> >                    Usually I should wait six months just to save myself
> > the aggrivation...
> 
> No, waiting 6 months between updates *causes* aggrivation.

The last word you're using here was originally coined by Allan.  Since I
didn't find it in my dictionary, I assume it doesn't exist.   So I would
suggest using either "aggravation" or "aggrievation", another word I did
not find in my dictionary, but which seems to fit even better ... :-)

Sincerely,
  Rainer

Re: [gentoo-user] Libsld, what gives?

[Peter Humphrey]

On Thursday, 17 November 2022 12:52:33 GMT Dr Rainer Woitok wrote:
> Paul,
> 
> On Thursday, 2022-11-17 17:52:17 +1100, you wrote:
> > On Wednesday, November 16, 2022 6:11:18 P.M. AEDT Alan Grimes wrote:
> > > ...
> > > 
> > >                    Usually I should wait six months just to save myself
> > > 
> > > the aggrivation...
> > 
> > No, waiting 6 months between updates *causes* aggrivation.
> 
> The last word you're using here was originally coined by Allan.  Since I
> didn't find it in my dictionary, I assume it doesn't exist.   So I would
> suggest using either "aggravation" or "aggrievation", another word I did
> not find in my dictionary, but which seems to fit even better ... :-)

If you consult a dictionary, you'll find that 'aggravate' means 'make worse'; 
thus, a medical condition may be aggravated by neglect.

The word you want is 'annoyance' - or just 'trouble'.

-- 
Regards,
Peter.

[gentoo-user] Re: Libsld, what gives?

[Grant Edwards]

On 2022-11-17, Paul Colquhoun <paulcol@andor.dropbear.id.au> wrote:
> On Wednesday, November 16, 2022 6:11:18 P.M. AEDT Alan Grimes wrote:
>> Even though only 45 days have passed since my last update, I felt like
>> doing one tonight. Usually I should wait six months just to save myself
>> the aggrivation...
>
> No, waiting 6 months between updates *causes* aggrivation.

Indeed.

> Try updateing on a regular schedule, at 1 or 2 week intervals, and
> see if your experience improves.

He's been told this many times. He prefers to wait and complain.

--
Grant

Re: [gentoo-user] Re: Libsld, what gives?

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 532 bytes --]

On Thu, 17 Nov 2022 13:14:44 -0000 (UTC), Grant Edwards wrote:

> > Try updateing on a regular schedule, at 1 or 2 week intervals, and
> > see if your experience improves.  
> 
> He's been told this many times. He prefers to wait and complain.

It could be worse, he could update every 1 or 2 weeks and complain/rant
every time :-O


-- 
Neil Bothwick

"Thou shalt not battle over operating systems. I am wise and in My wisdom
have created diverse and various operating systems."
  The Ten Usenet Commandments: One

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] Re: Libsld, what gives?

[Mark Knecht]

[-- Attachment #1: Type: text/plain, Size: 174 bytes --]

On Thu, Nov 17, 2022 at 6:48 AM Neil Bothwick <neil@digimed.co.uk> wrote:
>
> It could be worse, he could update every 1 or 2 weeks and complain/rant
> every time :-O
>

:-)

[-- Attachment #2: Type: text/html, Size: 291 bytes --]