From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 0E6C3158041 for ; Tue, 7 Sep 2021 07:05:53 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E96D1E0940; Tue, 7 Sep 2021 07:05:45 +0000 (UTC) Received: from isp1.netcon.at (unknown [62.218.194.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 377E4E0931 for ; Tue, 7 Sep 2021 07:05:44 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by isp1.netcon.at (Postfix) with ESMTP id B321718E7BF2 for ; Tue, 7 Sep 2021 09:05:26 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at isp1.netcon.intern Received: from isp1.netcon.at ([127.0.0.1]) by localhost (isp1.netcon.at [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 7rfz4Vg0-r6s for ; Tue, 7 Sep 2021 09:05:26 +0200 (CEST) Received: from puchmayr.linznet.at (be-9b-bb-d-c3.91-142-26-35.cust.kabelspeed.at [91.142.26.35]) by isp1.netcon.at (Postfix) with ESMTPS id C722F18E7C11 for ; Tue, 7 Sep 2021 09:03:16 +0200 (CEST) Received: (qmail 2346 invoked from network); 7 Sep 2021 07:03:08 -0000 Received: from zeus.local (HELO zeus.localnet) (192.168.1.2) by mail.local with SMTP; 7 Sep 2021 07:03:08 -0000 From: Alexander Puchmayr To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Emerge -u -k package install order - broken system Date: Tue, 07 Sep 2021 09:03:15 +0200 Message-ID: <2132328.bB369e8A3T@zeus> In-Reply-To: References: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Archives-Salt: 764de128-554a-4340-8943-59eb40b3ee74 X-Archives-Hash: 1c02aae1945a8ad401656fdb79efdbe4 Am Montag, 6. September 2021, 19:38:38 CEST schrieb Jack: > On 2021.09.06 10:33, Alexander Puchmayr wrote: > > 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? > > It might help if you stated which version of packages you currently > have installed - specifically glibc. > > As for recovery, you most likely need to boot to a live image (CD or > USB) then chroot into the existing system. I'm only guessing as to > what is the minimal list of files you will need to replace, but I'd see > if you can find or create a binary package of the latest glibc and then > install or unpack that to your system. > > As to whether this might be a bug in portage, I'd say you need to > provide more details about exactly what you did. What emerge line, > what you mean by installation via binary packages, and where you got > those binary packages. > > If you do still have a running shell, does emerge still run at all? What I did is: * On my build host, I compiled the full system and creating packages * On the client (i.e. The machine in question) I simply did a emerge -auvDNk world. * Portage did not complain about any conflicts, the amount of packages is what I expected, so I started the upgrade. * After about 25 packages installed successfully, emerge stopped with the errors explained before. For me the problem is solved now as I could recover the system, but I still would like to know how to prevent this -- installing glibc prior world may be a good idea. Thanks, Alex