Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
[gentoo-user] pain, PAIN, and more pain again.
59 views
Skip to first unread message
Alan Grimes
Jun 19, 2022, 12:00:04 AM6/19/22
to
I probably owe you guys an appology which is not forthcoming, at least
not tonight for obvious reasons. Instead, lets me explain my problem
solving procedure.
At this point in time, if you have a problem, especially on linux, it is
almost never the problem that existed before a penguin tried to solve it
for you. Instead, the problem you are facing is the problem caused when
either a penguin or a whole flock of penguins sanctamoniously decided
that you needed a solution and that this solution would be installed on
your system without your intervention, or knowledge or concent.
Occasionally they get away wtith this and your life gets a little easier
and you are none the wiser. Usually, however, their solution to the
thing that wasn't really bothering you in the first place fails
spectacularly and spoils your whole week.
Ok, what are your options?
A: Figure out what brand of dope the penguin was on and what dose, ratio
of dope to vodka, and get on precisely the same prescription to get in
just the right mindset to try to understand how their crappy software
was supposed to work so you can fix it.
B. Exterminate the penguin's software from your computer so that you can
experience the underlying problem in its rawest and most brutal form and
find that it's not even worth solving or that it admits an utterly
trivial solution that, at least, makes sense to you and that you won't
have any trouble maintaining for the long haul.
For me, choice A is always always always wrong. The computer is supposed
to work for you, not the other way around. If you are spending hours, or
even weeks of your rotten miserable life chasing down obscure answers to
questions you shouldn't even have, then you are doing computing wrong
and need to stop, take two steps back, and figure out what your real
problem is.
I get angry when Linux does not let me do that. =|
Instead, the penguins seem obsessed with inventing more and more garbage
that I need to manage.
Example:
Old way:
"My boot drive is plugged into this port on the motherboard"
New way:
Spend hours figuring out what your UUID is, create a physical pocket
folder (which you will subsequently have to store and manage) with the
UUID which is long and complex and copy it by hand, very carefully, then
set that up in your mtab....
Example:
Old way: "My network printer is at this IP address"
New way:
Master a list of 5-6 obscure and arcane packages that let you assign
"human friendly" network names to devices and then get all those
packages working with each other so you can print. Yeah, it looks more
like christmass tree wiring than a solution to a problem, You'll be
doing it again from scratch next month when we decide to change it again
for no reason and No, you can't print using the old way.
Ie, the printer I spent $400 on so that I could print from anywhere in
my house only works with my windows computer because I made the mistake
of updating CUPS.
It's only been 3 months innce I updated last so therefore I'm hurting
BAD tonight. I had to update the hack I used last time to get around the
libicuuc fuckup by implementing the same hack again but version
bumped... (symlink 1.71.1 to 1.70)... It seemed gung ho about python
3.11 but it turned out that 3.11 is still beta and that I should ignore
it.
The maintainers of steam overlay seem to have given up, so I used layman
to -d it and now I get
!!! Invalid PORTDIR_OVERLAY (not a dir): '/var/lib/layman/steam-overlay'
each time I invoke emerge...
What's killing me dead, however is:
>>> Running pre-merge checks for www-client/chromium-104.0.5110.0
* sys-devel/clang:14 is missing! Cannot use LLVM slot 14 ...
* =sys-devel/lld-13* is missing! Cannot use LLVM slot 13 ...
* =sys-devel/lld-12* is missing! Cannot use LLVM slot 12 ...
* =sys-devel/lld-11* is missing! Cannot use LLVM slot 11 ...
* sys-devel/clang:10 is missing! Cannot use LLVM slot 10 ...
* sys-devel/clang:9 is missing! Cannot use LLVM slot 9 ...
* sys-devel/clang:8 is missing! Cannot use LLVM slot 8 ...
* ERROR: www-client/chromium-104.0.5110.0::gentoo failed (pretend phase):
* No LLVM slot <= 14 satisfying the package's dependencies found
installed!
*
* Call stack:
* ebuild.sh, line 127: Called pkg_pretend
* chromium-104.0.5110.0.ebuild, line 283: Called pre_build_checks
* chromium-104.0.5110.0.ebuild, line 243: Called llvm_pkg_setup
* llvm.eclass, line 201: Called get_llvm_prefix '14'
* llvm.eclass, line 180: Called die
* The specific snippet of code:
* die "No LLVM slot${1:+ <= ${1}} satisfying the package's
dependencies found installed!"
*
* If you need support, post the output of `emerge --info
'=www-client/chromium-104.0.5110.0::gentoo'`,
* the complete build log and the output of `emerge -pqv
'=www-client/chromium-104.0.5110.0::gentoo'`.
* The complete build log is located at
'/var/tmp/portage/www-client/chromium-104.0.5110.0/temp/build.log'.
* The ebuild environment file is located at
'/var/tmp/portage/www-client/chromium-104.0.5110.0/temp/die.env'.
* Working directory:
'/var/tmp/portage/www-client/chromium-104.0.5110.0/empty'
* S:
'/var/tmp/portage/www-client/chromium-104.0.5110.0/work/chromium-104.0.5110.0'
>>> Failed to emerge www-client/chromium-104.0.5110.0, Log file:
##########################
Slot conflict???
No problem! I'll just go to eselect and pick a different slot.........
Oh wait, that was the OLD way of selecting slots... I went searching for
an explanation for how to set it up and it was like:
shifty informant: "Well you are supposed to go to the alley behind the
tavern?"
Me: "Which tavern?"
shifty informant: "You know *the* tavern... You go there between
midnight and 3 AM and when you are confronted you make the sign."
Me: "What sign, how am I supposed to make the sign?"
shifty informant: "You know, the sign, every thief knows how to make
it..."
Me: [ starts to say I'm not a thief then gives up..]
shifty informant: When you get inside the club just show off your dagger
throwing skills and then they'll give you the line you need to put in
the file to make it work."
Me: I don't even own a dagger.... Wait, file?!?!? WHAT FILE??? WHERE
IS THIS FILE??? WHY DO i HAVE TO EDIT IT?? WHERE DID YOU RUN OFF TO???
WHO DO I TALK TO TO GET SOME REAL INFORMATION???
KDE will keep me busy the rest of the night, I only use a handful of its
utilities and don't even know how to set it up as a window manager but
it likes to version bump its packages several times an hour and cause
emerge conflicts just to piss me off...
--
Beware of Zombies. =O
#EggCrisis #BlackWinter
White is the new Kulak.
Powers are not rights.
not tonight for obvious reasons. Instead, lets me explain my problem
solving procedure.
At this point in time, if you have a problem, especially on linux, it is
almost never the problem that existed before a penguin tried to solve it
for you. Instead, the problem you are facing is the problem caused when
either a penguin or a whole flock of penguins sanctamoniously decided
that you needed a solution and that this solution would be installed on
your system without your intervention, or knowledge or concent.
Occasionally they get away wtith this and your life gets a little easier
and you are none the wiser. Usually, however, their solution to the
thing that wasn't really bothering you in the first place fails
spectacularly and spoils your whole week.
Ok, what are your options?
A: Figure out what brand of dope the penguin was on and what dose, ratio
of dope to vodka, and get on precisely the same prescription to get in
just the right mindset to try to understand how their crappy software
was supposed to work so you can fix it.
B. Exterminate the penguin's software from your computer so that you can
experience the underlying problem in its rawest and most brutal form and
find that it's not even worth solving or that it admits an utterly
trivial solution that, at least, makes sense to you and that you won't
have any trouble maintaining for the long haul.
For me, choice A is always always always wrong. The computer is supposed
to work for you, not the other way around. If you are spending hours, or
even weeks of your rotten miserable life chasing down obscure answers to
questions you shouldn't even have, then you are doing computing wrong
and need to stop, take two steps back, and figure out what your real
problem is.
I get angry when Linux does not let me do that. =|
Instead, the penguins seem obsessed with inventing more and more garbage
that I need to manage.
Example:
Old way:
"My boot drive is plugged into this port on the motherboard"
New way:
Spend hours figuring out what your UUID is, create a physical pocket
folder (which you will subsequently have to store and manage) with the
UUID which is long and complex and copy it by hand, very carefully, then
set that up in your mtab....
Example:
Old way: "My network printer is at this IP address"
New way:
Master a list of 5-6 obscure and arcane packages that let you assign
"human friendly" network names to devices and then get all those
packages working with each other so you can print. Yeah, it looks more
like christmass tree wiring than a solution to a problem, You'll be
doing it again from scratch next month when we decide to change it again
for no reason and No, you can't print using the old way.
Ie, the printer I spent $400 on so that I could print from anywhere in
my house only works with my windows computer because I made the mistake
of updating CUPS.
It's only been 3 months innce I updated last so therefore I'm hurting
BAD tonight. I had to update the hack I used last time to get around the
libicuuc fuckup by implementing the same hack again but version
bumped... (symlink 1.71.1 to 1.70)... It seemed gung ho about python
3.11 but it turned out that 3.11 is still beta and that I should ignore
it.
The maintainers of steam overlay seem to have given up, so I used layman
to -d it and now I get
!!! Invalid PORTDIR_OVERLAY (not a dir): '/var/lib/layman/steam-overlay'
each time I invoke emerge...
What's killing me dead, however is:
>>> Running pre-merge checks for www-client/chromium-104.0.5110.0
* sys-devel/clang:14 is missing! Cannot use LLVM slot 14 ...
* =sys-devel/lld-13* is missing! Cannot use LLVM slot 13 ...
* =sys-devel/lld-12* is missing! Cannot use LLVM slot 12 ...
* =sys-devel/lld-11* is missing! Cannot use LLVM slot 11 ...
* sys-devel/clang:10 is missing! Cannot use LLVM slot 10 ...
* sys-devel/clang:9 is missing! Cannot use LLVM slot 9 ...
* sys-devel/clang:8 is missing! Cannot use LLVM slot 8 ...
* ERROR: www-client/chromium-104.0.5110.0::gentoo failed (pretend phase):
* No LLVM slot <= 14 satisfying the package's dependencies found
installed!
*
* Call stack:
* ebuild.sh, line 127: Called pkg_pretend
* chromium-104.0.5110.0.ebuild, line 283: Called pre_build_checks
* chromium-104.0.5110.0.ebuild, line 243: Called llvm_pkg_setup
* llvm.eclass, line 201: Called get_llvm_prefix '14'
* llvm.eclass, line 180: Called die
* The specific snippet of code:
* die "No LLVM slot${1:+ <= ${1}} satisfying the package's
dependencies found installed!"
*
* If you need support, post the output of `emerge --info
'=www-client/chromium-104.0.5110.0::gentoo'`,
* the complete build log and the output of `emerge -pqv
'=www-client/chromium-104.0.5110.0::gentoo'`.
* The complete build log is located at
'/var/tmp/portage/www-client/chromium-104.0.5110.0/temp/build.log'.
* The ebuild environment file is located at
'/var/tmp/portage/www-client/chromium-104.0.5110.0/temp/die.env'.
* Working directory:
'/var/tmp/portage/www-client/chromium-104.0.5110.0/empty'
* S:
'/var/tmp/portage/www-client/chromium-104.0.5110.0/work/chromium-104.0.5110.0'
>>> Failed to emerge www-client/chromium-104.0.5110.0, Log file:
##########################
Slot conflict???
No problem! I'll just go to eselect and pick a different slot.........
Oh wait, that was the OLD way of selecting slots... I went searching for
an explanation for how to set it up and it was like:
shifty informant: "Well you are supposed to go to the alley behind the
tavern?"
Me: "Which tavern?"
shifty informant: "You know *the* tavern... You go there between
midnight and 3 AM and when you are confronted you make the sign."
Me: "What sign, how am I supposed to make the sign?"
shifty informant: "You know, the sign, every thief knows how to make
it..."
Me: [ starts to say I'm not a thief then gives up..]
shifty informant: When you get inside the club just show off your dagger
throwing skills and then they'll give you the line you need to put in
the file to make it work."
Me: I don't even own a dagger.... Wait, file?!?!? WHAT FILE??? WHERE
IS THIS FILE??? WHY DO i HAVE TO EDIT IT?? WHERE DID YOU RUN OFF TO???
WHO DO I TALK TO TO GET SOME REAL INFORMATION???
KDE will keep me busy the rest of the night, I only use a handful of its
utilities and don't even know how to set it up as a window manager but
it likes to version bump its packages several times an hour and cause
emerge conflicts just to piss me off...
--
Beware of Zombies. =O
#EggCrisis #BlackWinter
White is the new Kulak.
Powers are not rights.
Anna “CyberTailor”
Jun 19, 2022, 12:20:03 AM6/19/22
to
*reads*
Get a +1 from me. I hope you become a Gentoo, Alpine or Slackware dev
one day.
*reads more*
On 2022-06-18 23:54, Alan Grimes wrote:
> --
> Beware of Zombies. =O
> #EggCrisis #BlackWinter
> White is the new Kulak.
> Powers are not rights.
Disregard that. Stay away from all distros. And touch some grass please.
Get a +1 from me. I hope you become a Gentoo, Alpine or Slackware dev
one day.
*reads more*
On 2022-06-18 23:54, Alan Grimes wrote:
> --
> Beware of Zombies. =O
> #EggCrisis #BlackWinter
> White is the new Kulak.
> Powers are not rights.
Michael
Jun 19, 2022, 8:50:04 AM6/19/22
to
On Sunday, 19 June 2022 04:54:26 BST Alan Grimes wrote:
[snippage of long prose ...]
> Example:
>
> Old way:
>
> "My boot drive is plugged into this port on the motherboard"
>
> New way:
>
> Spend hours figuring out what your UUID is, create a physical pocket
> folder (which you will subsequently have to store and manage) with the
> UUID which is long and complex and copy it by hand, very carefully, then
> set that up in your mtab....
It doesn't take hours to run 'blkid'.
> Example:
>
> Old way: "My network printer is at this IP address"
>
> New way:
>
> Master a list of 5-6 obscure and arcane packages that let you assign
> "human friendly" network names to devices and then get all those
> packages working with each other so you can print. Yeah, it looks more
> like christmass tree wiring than a solution to a problem, You'll be
> doing it again from scratch next month when we decide to change it again
> for no reason and No, you can't print using the old way.
>
> Ie, the printer I spent $400 on so that I could print from anywhere in
> my house only works with my windows computer because I made the mistake
> of updating CUPS.
I have always been using an IP address to specify my printer. In a different
topology with multiple printers and regularly changing users/PCs I would
consider a different more automated approach.
> It's only been 3 months innce I updated last so therefore I'm hurting
> BAD tonight. I had to update the hack I used last time to get around the
> libicuuc fuckup by implementing the same hack again but version
> bumped... (symlink 1.71.1 to 1.70)... It seemed gung ho about python
> 3.11 but it turned out that 3.11 is still beta and that I should ignore
> it.
>
> The maintainers of steam overlay seem to have given up, so I used layman
> to -d it and now I get
> !!! Invalid PORTDIR_OVERLAY (not a dir): '/var/lib/layman/steam-overlay'
> each time I invoke emerge...
Take a look at:
https://wiki.gentoo.org/wiki/Eselect/Repository
> What's killing me dead, however is:
> >>> Running pre-merge checks for www-client/chromium-104.0.5110.0
>
> * sys-devel/clang:14 is missing! Cannot use LLVM slot 14 ...
> * =sys-devel/lld-13* is missing! Cannot use LLVM slot 13 ...
> * =sys-devel/lld-12* is missing! Cannot use LLVM slot 12 ...
> * =sys-devel/lld-11* is missing! Cannot use LLVM slot 11 ...
> * sys-devel/clang:10 is missing! Cannot use LLVM slot 10 ...
> * sys-devel/clang:9 is missing! Cannot use LLVM slot 9 ...
> * sys-devel/clang:8 is missing! Cannot use LLVM slot 8 ...
> * ERROR: www-client/chromium-104.0.5110.0::gentoo failed (pretend phase):
> * No LLVM slot <= 14 satisfying the package's dependencies found
> installed!
Err ...
~ $ eix -l chromium | grep '104.0.5110.0'
[M]~ 104.0.5110.0 (0/dev) [+X component-build cups custom-cflags
debug gtk4 +hangouts headless +js-type-check kerberos libcxx lto +official pgo
pic +proprietary-codecs pulseaudio screencast selinux +suid +system-ffmpeg
+system-harfbuzz +system-icu +system-png vaapi wayland widevine
CPU_FLAGS_ARM="neon" L10N="+af +am +ar +bg +bn +ca +cs +da +de +el +en-GB +es
+es-419 +et +fa +fi +fil +fr +gu +he +hi +hr +hu +id +it +ja +kn +ko +lt +lv +ml
+mr +ms +nb +nl +pl +pt-BR +pt-PT +ro +ru +sk +sl +sr +sv +sw +ta +te +th +tr
+uk +ur +vi +zh-CN +zh-TW"] ["component-build? ( !suid !libcxx )
screencast? ( wayland ) !headless? ( || ( X wayland ) ) pgo? ( X !wayland )"]
So, you're trying to install a masked version of chromium, which may or may
not ever make it into the testing/stable tree without further development work
on it and any one of its dependencies and you blame some penguin for the
result?
> *
> * Call stack:
> * ebuild.sh, line 127: Called pkg_pretend
> * chromium-104.0.5110.0.ebuild, line 283: Called pre_build_checks
> * chromium-104.0.5110.0.ebuild, line 243: Called llvm_pkg_setup
> * llvm.eclass, line 201: Called get_llvm_prefix '14'
> * llvm.eclass, line 180: Called die
> * The specific snippet of code:
> * die "No LLVM slot${1:+ <= ${1}} satisfying the package's
> dependencies found installed!"
[snip ...]
> >>> Failed to emerge www-client/chromium-104.0.5110.0, Log file:
> ##########################
>
>
> Slot conflict???
>
> No problem! I'll just go to eselect and pick a different slot.........
>
>
> Oh wait, that was the OLD way of selecting slots... I went searching for
> an explanation for how to set it up and it was like:
[snip ...]
You should be able to install a specific slot, but you may have to keyword it
if you're on a stable arch. Starting with lld, clang, llvm and whatever else
may be needed. However, why would you want to try a masked package - unless
you have the time, knowledge and inclination beyond authoring long prose posts
in a mailing list to contribute to its development?
> KDE will keep me busy the rest of the night, I only use a handful of its
> utilities and don't even know how to set it up as a window manager but
> it likes to version bump its packages several times an hour and cause
> emerge conflicts just to piss me off...
If you use (mostly) stable arch packages emerge conflicts tend to be a rare
event.
[snippage of long prose ...]
> Example:
>
> Old way:
>
> "My boot drive is plugged into this port on the motherboard"
>
> New way:
>
> Spend hours figuring out what your UUID is, create a physical pocket
> folder (which you will subsequently have to store and manage) with the
> UUID which is long and complex and copy it by hand, very carefully, then
> set that up in your mtab....
> Example:
>
> Old way: "My network printer is at this IP address"
>
> New way:
>
> Master a list of 5-6 obscure and arcane packages that let you assign
> "human friendly" network names to devices and then get all those
> packages working with each other so you can print. Yeah, it looks more
> like christmass tree wiring than a solution to a problem, You'll be
> doing it again from scratch next month when we decide to change it again
> for no reason and No, you can't print using the old way.
>
> Ie, the printer I spent $400 on so that I could print from anywhere in
> my house only works with my windows computer because I made the mistake
> of updating CUPS.
topology with multiple printers and regularly changing users/PCs I would
consider a different more automated approach.
> It's only been 3 months innce I updated last so therefore I'm hurting
> BAD tonight. I had to update the hack I used last time to get around the
> libicuuc fuckup by implementing the same hack again but version
> bumped... (symlink 1.71.1 to 1.70)... It seemed gung ho about python
> 3.11 but it turned out that 3.11 is still beta and that I should ignore
> it.
>
> The maintainers of steam overlay seem to have given up, so I used layman
> to -d it and now I get
> !!! Invalid PORTDIR_OVERLAY (not a dir): '/var/lib/layman/steam-overlay'
> each time I invoke emerge...
https://wiki.gentoo.org/wiki/Eselect/Repository
> What's killing me dead, however is:
> >>> Running pre-merge checks for www-client/chromium-104.0.5110.0
>
> * sys-devel/clang:14 is missing! Cannot use LLVM slot 14 ...
> * =sys-devel/lld-13* is missing! Cannot use LLVM slot 13 ...
> * =sys-devel/lld-12* is missing! Cannot use LLVM slot 12 ...
> * =sys-devel/lld-11* is missing! Cannot use LLVM slot 11 ...
> * sys-devel/clang:10 is missing! Cannot use LLVM slot 10 ...
> * sys-devel/clang:9 is missing! Cannot use LLVM slot 9 ...
> * sys-devel/clang:8 is missing! Cannot use LLVM slot 8 ...
> * ERROR: www-client/chromium-104.0.5110.0::gentoo failed (pretend phase):
> * No LLVM slot <= 14 satisfying the package's dependencies found
> installed!
~ $ eix -l chromium | grep '104.0.5110.0'
[M]~ 104.0.5110.0 (0/dev) [+X component-build cups custom-cflags
debug gtk4 +hangouts headless +js-type-check kerberos libcxx lto +official pgo
pic +proprietary-codecs pulseaudio screencast selinux +suid +system-ffmpeg
+system-harfbuzz +system-icu +system-png vaapi wayland widevine
CPU_FLAGS_ARM="neon" L10N="+af +am +ar +bg +bn +ca +cs +da +de +el +en-GB +es
+es-419 +et +fa +fi +fil +fr +gu +he +hi +hr +hu +id +it +ja +kn +ko +lt +lv +ml
+mr +ms +nb +nl +pl +pt-BR +pt-PT +ro +ru +sk +sl +sr +sv +sw +ta +te +th +tr
+uk +ur +vi +zh-CN +zh-TW"] ["component-build? ( !suid !libcxx )
screencast? ( wayland ) !headless? ( || ( X wayland ) ) pgo? ( X !wayland )"]
So, you're trying to install a masked version of chromium, which may or may
not ever make it into the testing/stable tree without further development work
on it and any one of its dependencies and you blame some penguin for the
result?
> *
> * Call stack:
> * ebuild.sh, line 127: Called pkg_pretend
> * chromium-104.0.5110.0.ebuild, line 283: Called pre_build_checks
> * chromium-104.0.5110.0.ebuild, line 243: Called llvm_pkg_setup
> * llvm.eclass, line 201: Called get_llvm_prefix '14'
> * llvm.eclass, line 180: Called die
> * The specific snippet of code:
> * die "No LLVM slot${1:+ <= ${1}} satisfying the package's
> dependencies found installed!"
> >>> Failed to emerge www-client/chromium-104.0.5110.0, Log file:
> ##########################
>
>
> Slot conflict???
>
> No problem! I'll just go to eselect and pick a different slot.........
>
>
> Oh wait, that was the OLD way of selecting slots... I went searching for
> an explanation for how to set it up and it was like:
You should be able to install a specific slot, but you may have to keyword it
if you're on a stable arch. Starting with lld, clang, llvm and whatever else
may be needed. However, why would you want to try a masked package - unless
you have the time, knowledge and inclination beyond authoring long prose posts
in a mailing list to contribute to its development?
> KDE will keep me busy the rest of the night, I only use a handful of its
> utilities and don't even know how to set it up as a window manager but
> it likes to version bump its packages several times an hour and cause
> emerge conflicts just to piss me off...
event.
Dr Rainer Woitok
Jun 19, 2022, 9:50:04 AM6/19/22
to
Alan,
On Saturday, 2022-06-18 23:54:26 -0400, you wrote:
> ...
> ...
Write a message on parchment, roll the parchment up and seal it, then
hand it to your most reliable friend who will mount his fastest mare and
ride off ...
That's as reliable as your best friend and as fast as his fastest mare.
New way:
Fire up a computer, open a mail application with an awkward user inter-
face, write a mail using a sloppy keyboard, thus introducing plenty of
typos (including in the receiver's email address), above all depend on
misconfigured name servers, mail servers, power stations, you-name-it,
and eventually get back a non-delivery-notice ...
That's as unreliable as it can be.
Sincerely,
Rainer
On Saturday, 2022-06-18 23:54:26 -0400, you wrote:
> ...
> At this point in time, if you have a problem, especially on linux, it is
> almost never the problem that existed before a penguin tried to solve it
> for you.
Perhaps Ubuntu would be your friend?
> almost never the problem that existed before a penguin tried to solve it
> for you.
> ...
> Example:
>
> Old way:
>
> "My boot drive is plugged into this port on the motherboard"
>
> New way:
>
> Spend hours figuring out what your UUID is, create a physical pocket
> folder (which you will subsequently have to store and manage) with the
> UUID which is long and complex and copy it by hand, very carefully, then
> set that up in your mtab....
Old way:
>
> Old way:
>
> "My boot drive is plugged into this port on the motherboard"
>
> New way:
>
> Spend hours figuring out what your UUID is, create a physical pocket
> folder (which you will subsequently have to store and manage) with the
> UUID which is long and complex and copy it by hand, very carefully, then
> set that up in your mtab....
Write a message on parchment, roll the parchment up and seal it, then
hand it to your most reliable friend who will mount his fastest mare and
ride off ...
That's as reliable as your best friend and as fast as his fastest mare.
New way:
Fire up a computer, open a mail application with an awkward user inter-
face, write a mail using a sloppy keyboard, thus introducing plenty of
typos (including in the receiver's email address), above all depend on
misconfigured name servers, mail servers, power stations, you-name-it,
and eventually get back a non-delivery-notice ...
That's as unreliable as it can be.
Sincerely,
Rainer
Alan Grimes
Jun 21, 2022, 3:00:04 AM6/21/22
to
Laurence Perkins wrote:
> I know how it goes. But do be fair, it was the motherboard manufacturers who changed how the boot process works, not the penguins. 😉 The penguins are just trying to adapt to it.
>
> I'm not sure where your problems are coming from. I use CUPS by IP address in my setup. You just need to also use static IP addresses for all your printers, etc. Or else things may randomly stop working when your router reboots.
>
> As for your update woes, I handle it by using a setup that supports snapshottable subvolumes. I put my personal files on one, and the OS on another. Then, for updates, you take a snapshot first, and if it all goes kablooey you can easily roll back while you sort out the issue. For bonus points you can update the snapshot and then switch to it and delete the original only once you have everything working the way you like it again.
>
> In this case though, I think your trouble comes from trying to install a version of Chromium that's still in development. That's why it was masked. Masks like that usually indicate that there's something horribly wrong with it and you shouldn't use it unless there's no choice. Try 103 maybe? The betas usually work.
Nah, actually once all the crap and annoyances cleared my entire failure
list looks like:
atg@tortoise /var/tmp/portage $ tree -L 2
.
├── dev-lang
│ ├── spidermonkey-78.15.0
│ └── spidermonkey-91.10.0
├── dev-texlive
│ └── texlive-latex-2021
├── net-misc
│ └── ipv6calc-4.0.1
└── www-client
└── falkon-22.04.2
9 directories, 0 files
atg@tortoise /var/tmp/portage $
####
which is basically the shortest it's ever been. Spidermonkey wanted to
build against LLD-13 but rust was built against LLD-14 which was a
problem for some reason... =\ The others were similar failures, Ipv6calc
was a major WTF, it was like they were building a library by patching
all of the clients instead of just pushing out a header, so no wonder
that failed. I forgot about the other two, very very stupid problems
that aren't even worth thinking about.
My main problem as of the last post was that I had PART of the LLVM-14
suite installed so chromium could not find a LLVM version that had all
of its parts available and started using language that confused me with
a different gentoo concept.
Once that and a few other log jams were cleared, (I had to emptytree
world the system to get much of it to update...) but after that and a
few rebuilds after that, everything quieted down and is working again.
The procedure for using steam overlay has changed radically from the
earlier procedure. =\
> I know how it goes. But do be fair, it was the motherboard manufacturers who changed how the boot process works, not the penguins. 😉 The penguins are just trying to adapt to it.
>
> I'm not sure where your problems are coming from. I use CUPS by IP address in my setup. You just need to also use static IP addresses for all your printers, etc. Or else things may randomly stop working when your router reboots.
>
> As for your update woes, I handle it by using a setup that supports snapshottable subvolumes. I put my personal files on one, and the OS on another. Then, for updates, you take a snapshot first, and if it all goes kablooey you can easily roll back while you sort out the issue. For bonus points you can update the snapshot and then switch to it and delete the original only once you have everything working the way you like it again.
>
> In this case though, I think your trouble comes from trying to install a version of Chromium that's still in development. That's why it was masked. Masks like that usually indicate that there's something horribly wrong with it and you shouldn't use it unless there's no choice. Try 103 maybe? The betas usually work.
Nah, actually once all the crap and annoyances cleared my entire failure
list looks like:
atg@tortoise /var/tmp/portage $ tree -L 2
.
├── dev-lang
│ ├── spidermonkey-78.15.0
│ └── spidermonkey-91.10.0
├── dev-texlive
│ └── texlive-latex-2021
├── net-misc
│ └── ipv6calc-4.0.1
└── www-client
└── falkon-22.04.2
9 directories, 0 files
atg@tortoise /var/tmp/portage $
####
which is basically the shortest it's ever been. Spidermonkey wanted to
build against LLD-13 but rust was built against LLD-14 which was a
problem for some reason... =\ The others were similar failures, Ipv6calc
was a major WTF, it was like they were building a library by patching
all of the clients instead of just pushing out a header, so no wonder
that failed. I forgot about the other two, very very stupid problems
that aren't even worth thinking about.
My main problem as of the last post was that I had PART of the LLVM-14
suite installed so chromium could not find a LLVM version that had all
of its parts available and started using language that confused me with
a different gentoo concept.
Once that and a few other log jams were cleared, (I had to emptytree
world the system to get much of it to update...) but after that and a
few rebuilds after that, everything quieted down and is working again.
The procedure for using steam overlay has changed radically from the
earlier procedure. =\
0 new messages