From: Alan Grimes <alonzotg@verizon.net>
To: gentoo-user@lists.gentoo.org, Laurence Perkins <lperkins@openeye.net>
Subject: Re: [gentoo-user] pain, PAIN, and more pain again.
Date: Tue, 21 Jun 2022 02:50:00 -0400 [thread overview]
Message-ID: <03ee142a-bef7-cc1c-3d3f-f37626ee77e5@verizon.net> (raw)
In-Reply-To: <MW2PR07MB40584008DB0FF0DEDD745E38D2B09@MW2PR07MB4058.namprd07.prod.outlook.com>
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. =\
--
Beware of Zombies. =O
#EggCrisis #BlackWinter
White is the new Kulak.
Powers are not rights.
prev parent reply other threads:[~2022-06-21 6:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <17f99aef-fb3a-f460-d73e-7601081b8956.ref@verizon.net>
2022-06-19 3:54 ` [gentoo-user] pain, PAIN, and more pain again Alan Grimes
2022-06-19 4:14 ` Anna “CyberTailor”
2022-06-19 12:43 ` Michael
2022-06-19 13:41 ` Dr Rainer Woitok
2022-06-20 17:39 ` Laurence Perkins
2022-06-21 6:50 ` Alan Grimes [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=03ee142a-bef7-cc1c-3d3f-f37626ee77e5@verizon.net \
--to=alonzotg@verizon.net \
--cc=gentoo-user@lists.gentoo.org \
--cc=lperkins@openeye.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox