From: Andreas Fink <finkandreas@web.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Glibc and binpackages
Date: Thu, 12 Jan 2023 20:14:00 +0100 [thread overview]
Message-ID: <20230112201400.455f98e0@web.de> (raw)
In-Reply-To: <MW2PR07MB40587B1DDD6DEF70CC352B99D2FD9@MW2PR07MB4058.namprd07.prod.outlook.com>
On Thu, 12 Jan 2023 17:53:55 +0000
Laurence Perkins <lperkins@openeye.net> wrote:
> I'm not sure if I'm doing something horribly wrong, or missing something blindingly obvious, but I've just had to boot a rescue shell yet again, so I'm going to ask.
>
> To save time and effort, I have my big, powerful machine create binpackages for everything when it updates, and then let all my smaller machines pull from that. It works pretty well for the most part.
>
> But when there's a glibc update I have to specifically install it first. If I don't, then about half the time emerge decides that because it doesn't have to worry about build dependencies for binpackages, it can obviously update glibc last... Then it updates something that's needed for handling updates and that's it, stuck. If I'm lucky it's a compile tool, not one for handling binpackages and I can just tell it to do the glibc package next. Quite often though it's something like tar that's fundamental to installing anything at all and I have to ferry the new glibc over on a USB stick and unpack it with busybox... Occasionally it's something critical for the whole system and then I have to boot to a rescue shell of some kind.
>
> Think it's worth a feature request to have emerge prioritize glibc as high up in the list as it can when installing things? Or am I the only one who runs into this?
>
> LMP
I was running into this issue too already, but then at some point I
started more regularly updating and this problem disappeared.
I fully agree, that glibc should be updated rather earlier than later,
especially when compression libraries were built with a newer glibc.
/Andreas
next prev parent reply other threads:[~2023-01-12 19:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 17:53 [gentoo-user] Glibc and binpackages Laurence Perkins
2023-01-12 19:14 ` Andreas Fink [this message]
2023-01-13 16:17 ` John Blinka
2023-01-17 16:41 ` Laurence Perkins
2023-01-17 22:09 ` Wol
2023-01-17 17:07 ` Andreas Fink
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=20230112201400.455f98e0@web.de \
--to=finkandreas@web.de \
--cc=gentoo-user@lists.gentoo.org \
/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