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 57707158041 for ; Mon, 6 Sep 2021 17:38:49 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 55DA0E0858; Mon, 6 Sep 2021 17:38:42 +0000 (UTC) Received: from mail-qt1-f170.google.com (mail-qt1-f170.google.com [209.85.160.170]) (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 E4FBDE0823 for ; Mon, 6 Sep 2021 17:38:41 +0000 (UTC) Received: by mail-qt1-f170.google.com with SMTP id g11so5958316qtk.5 for ; Mon, 06 Sep 2021 10:38:41 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:subject:to:mime-version:in-reply-to :message-id:content-disposition:content-transfer-encoding; bh=bKwrwVZ83XlhncSJ4VraOpGYeaTcq91xW1itx9r1Jok=; b=MiR0Ll5ukzZT4i7msuTFvLeDgq5alyaQtnmtpk8NsplxYIExj/yie7hTWM4FXGtUEm obbEoq4+Fe8/d//IQ+9gfdCUTUQlQRLttqwwYh6PrRxh8xoSYp5Gzw21UKperv/l2xon a+Oi/rt+X2fYc0SP4QpqT/zmPWXLOJtYHNKw/P7fMywrGSGuF028jbSXmcHOPQfhoAcc d883h4da5Q3FBT0zmWn8o2cC1u+6nO/rT1e7IfDVXG1dOYC4bb3FYI8k6UNkmQuYFyju MIaxj1jnlxG0uP0WXsqGgFO4nK+xm95sTfVDlwwYzAybH6yF1yPlE39Wc4qG+S9E5kwK 8hlQ== X-Gm-Message-State: AOAM533Cp1eqnfagmU6JzYNj9xoWQdrRl1aJOiBcuSiWk/CzJAWq8OqB FZePKn22ThVPML8b8IFQpkM+t3oyaDxsSFxmbQ0= X-Google-Smtp-Source: ABdhPJyGmN40zHF2BC0nn8uAMrFv9maXye//d6LxUJikK8bKVI4KhiII45WD5jHKnBTarZyjucBE9A== X-Received: by 2002:a05:622a:15d0:: with SMTP id d16mr11692473qty.185.1630949920782; Mon, 06 Sep 2021 10:38:40 -0700 (PDT) Received: from ffortso9 (c-76-23-130-96.hsd1.ct.comcast.net. [76.23.130.96]) by smtp.gmail.com with ESMTPSA id r23sm5696490qtp.60.2021.09.06.10.38.39 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 06 Sep 2021 10:38:40 -0700 (PDT) Date: Mon, 06 Sep 2021 13:38:38 -0400 From: Jack Subject: Re: [gentoo-user] Emerge -u -k package install order - broken system To: gentoo-user@lists.gentoo.org 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 In-Reply-To: <12960787.dW097sEU6C@zeus> X-Mailer: Balsa 2.6.3-real-2-g105dcf012 Message-Id: Content-Type: text/plain; charset=us-ascii; DelSp=Yes; Format=Flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 4431e2f0-acbe-4662-add9-07306549363b X-Archives-Hash: 171122d4cf8dc774cb55f30a8215f0da On 2021.09.06 10:33, Alexander Puchmayr wrote: > Hi there, >=20 > I just tried to upgrade a older installation via binary packages and =20 > this > broke my system. After around 25 packages of almost 300 it stopped =20 > with error > and failing packages. >=20 > $ emerge > Failed to validate a sane '/dev'. > bash process substitution doesn't work; this may be an indication of =20 > 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 >=20 > --> looks allright, but: >=20 > $ bash > bash: /lib64/libc.so.6: version `GLIBC_2.33' not found (required by =20 > /lib64/ > libreadline.so.8) >=20 > --> system broken(!), cannot start any shell anymore, cannot install =20 > anything > anymore and it's obvious that the system is bricked after reboot or =20 > even when > the ssh session I'm logged in is closed. >=20 > It seems like as if sys-libs/readline-8.1_p1-r1-1:0/8::gentoo is =20 > installed > *before* installing a suitable glibc, breaking any binary that has =20 > the useflag > readline (including bash). >=20 > 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 =20 have installed - specifically glibc. As for recovery, you most likely need to boot to a live image (CD or =20 USB) then chroot into the existing system. I'm only guessing as to =20 what is the minimal list of files you will need to replace, but I'd see =20 if you can find or create a binary package of the latest glibc and then =20 install or unpack that to your system. As to whether this might be a bug in portage, I'd say you need to =20 provide more details about exactly what you did. What emerge line, =20 what you mean by installation via binary packages, and where you got =20 those binary packages. If you do still have a running shell, does emerge still run at all?