From: Alexander Puchmayr <alexander.puchmayr@linznet.at>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Emerge -u -k package install order - broken system
Date: Mon, 06 Sep 2021 16:33:32 +0200 [thread overview]
Message-ID: <12960787.dW097sEU6C@zeus> (raw)
Hi there,
I just tried to upgrade a older installation via binary packages and this
broke my system. After around 25 packages of almost 300 it stopped with error
and failing packages.
$ emerge
Failed to validate a sane '/dev'.
bash process substitution doesn't work; this may be an indication of a broken
'/dev/fd'.
$ ls -l /dev/fd/
insgesamt 0
lrwx------ 1 root root 64 6. Sep 14:18 0 -> /dev/pts/0
lrwx------ 1 root root 64 6. Sep 14:18 1 -> /dev/pts/0
lrwx------ 1 root root 64 6. Sep 14:18 2 -> /dev/pts/0
lr-x------ 1 root root 64 6. Sep 14:18 3 -> /proc/27261/fd
--> looks allright, but:
$ bash
bash: /lib64/libc.so.6: version `GLIBC_2.33' not found (required by /lib64/
libreadline.so.8)
--> system broken(!), cannot start any shell anymore, cannot install anything
anymore and it's obvious that the system is bricked after reboot or even when
the ssh session I'm logged in is closed.
It seems like as if sys-libs/readline-8.1_p1-r1-1:0/8::gentoo is installed
*before* installing a suitable glibc, breaking any binary that has the useflag
readline (including bash).
Two questions:
How do I get out of this mess?
Why does portage not work in correct package order? Portage bug?
next reply other threads:[~2021-09-06 14:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 14:33 Alexander Puchmayr [this message]
2021-09-06 17:38 ` [gentoo-user] Emerge -u -k package install order - broken system Jack
2021-09-07 7:03 ` Alexander Puchmayr
2021-09-07 7:31 ` [gentoo-user] Emerge -u -k package install order - broken system [SOLVED] Alexander Puchmayr
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=12960787.dW097sEU6C@zeus \
--to=alexander.puchmayr@linznet.at \
--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