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 188F21382C5 for ; Sun, 4 Feb 2018 18:23:20 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 58969E0D90; Sun, 4 Feb 2018 18:23:12 +0000 (UTC) Received: from mail-yw0-x241.google.com (mail-yw0-x241.google.com [IPv6:2607:f8b0:4002:c05::241]) (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 DA6CFE0C31 for ; Sun, 4 Feb 2018 18:23:11 +0000 (UTC) Received: by mail-yw0-x241.google.com with SMTP id u21so16915225ywc.2 for ; Sun, 04 Feb 2018 10:23:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=IsrwUEcxaPtfJTqTb3F8NtgYcAqw4b79pALEHIPo6qA=; b=TJ/Pso34KdoR6ZkkXfSQoLdF5tYXaFn4xCicWYZRda7dz/TcBytn97QiKfV5q1NaBv VqD/kaCNLxhkXYFHw0Wn/Md1aHi7tXYVDzoBU2223M97D2ytRNKUfEONIVMCs/5ZfKEg TtA9RjFp5I4eotNjin9kVivOstw3P+3sMktS1IHSrsy7NJLBc9aEFAQHfbf42M8VjOtE Pba3mC6LH8O9qHOETp4pt9fEAoPMy8A5Rh8gG+YILQ+nr2P5ddrO7maXmcwdnZLALv3V vkquYqWjJHoovtQNdisU9ICl92/EP7cHjWhz9mvrMcap4fZIhYJcdUWzEdby6L2NJ8eA DQDg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=IsrwUEcxaPtfJTqTb3F8NtgYcAqw4b79pALEHIPo6qA=; b=mJReZKHM7rV2UYHEVzap92yxnHiHru/Z4wL6DZD2Wg/4893G8YD0Uea3z3fWS9HjiH finG7h7XYNKGqTVH1ntfSBs+qABuFoVBebq/zbuUnnGL7H42DA//3FKvavUWBuJkRh+m FgyNozgBaj3XzLY5pWOPws5K6fSCfOKXw7qunCKJ7THrKt265d7gGSrIDr+MZLqz2n84 C/n3LkmMEE5KcWtdwYUBYNLbE1jQev6Pl4mlkqmUdDAz7F+jgb6+pAMJQB0zXNN93FhX fCBm3HSxY8OwBKmijIlGD5iRiK89BZhHM/52YSiaps8WLas4qkasmFN6mJ81r2MMfeBD vv+w== X-Gm-Message-State: AKwxytdkFB1+MV26csnnO93j1DDjr6Ec2NsMw0efUWVwSC8Z4yeY7fqV VEHjODThoHEAH8AYnmndVh8jYQ== X-Google-Smtp-Source: AH8x226ij+T9xoUt00UBFEMiyf+JWMyLGYpwE59dqd37sWpLvZxbwsJRbBTcjN7OXm1ZmiHSItXhbg== X-Received: by 10.129.157.17 with SMTP id u17mr29175766ywg.86.1517768591024; Sun, 04 Feb 2018 10:23:11 -0800 (PST) Received: from [192.168.2.5] (adsl-65-0-93-225.jan.bellsouth.net. [65.0.93.225]) by smtp.gmail.com with ESMTPSA id z77sm2429557ywd.21.2018.02.04.10.23.09 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 04 Feb 2018 10:23:10 -0800 (PST) Subject: Re: [gentoo-user] Re: Heads Up - glibc-2.27 breaks my system To: gentoo-user@lists.gentoo.org References: <5x7d1x01i1kktTk01x7eRl> <475348c8-d753-88f6-b282-0a90a5b3baa6@gmail.com> <6947ed70-7549-65ef-a8e9-345e2757d084@gmail.com> From: Dale Message-ID: <86070c3e-fca8-903e-8072-da4b3e7fdc2e@gmail.com> Date: Sun, 4 Feb 2018 12:23:09 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.6.0 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 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Archives-Salt: e0d56c88-adf4-46f5-972e-a8d9f2cc38fc X-Archives-Hash: df12332cb762ca1ba42330b9a0c0d039 Nikos Chantziaras wrote: > On 03/02/18 16:08, Dale wrote: >> Nikos Chantziaras wrote: >>> It is perfectly fine to downgrade glibc if you didn't emerge anything >>> that compiled binaries. >>> >>> If you did, you can still downgrade, but then you need to rebuild the >>> packages that you emerged since the glibc upgrade. qlop is your friend >>> here; it lets you find out the dates on which you emerged packages. >> >> That makes sense.  So, if worse comes to worse, downgrade, then emerge >> -e world if unsure what all has been updated since.  If, using qlop or >> friends, you can figure what was done since the upgrade, emerge those to >> make sure the linking is correct.  At least that is a option that should >> be doable.  That's better than thinking you can't downgrade for any >> reason, period. > > You might not be able to do that, if python (used by emerge) uses > something that breaks when downgrading glibc. Or gcc. Or binutils. Or > bash. Or anything else that's needed during an emerge. > > So you need to check with qlop *before* downgrading, and if it looks > like something critical was built against the new glibc, then all bets > are off. Which is why the downgrade protection exists in the first place. > > The only way out of this, is restoring from backup or fixing things by > booting from a sysrescuecd or similar. > > If only firefox or your media player and stuff like that got built > against the new glibc, then it's fine to downgrade. Otherwise, you > could end up bricking your system. > > > I see.  That would cause problems.  Depending on how bad it is affected, even emerge -k may not work same could be said for tar to I guess.  So, while upgrading glibc is required, eventually, it is also risky unless it is well, very well, tested.  I searched the wiki, I don't see anything about this topic.  I don't know how to do the wiki thing but it would be nice for someone who does to create a wiki page for this.  It is likely a rare thing to happen but the consequences of it are pretty serious and tricky to fix.  To keep from hijacking this thread anymore, I'd be happy to start a new thread, let people post what they know and should be on the wiki and then whoever knows how to do a wiki page move whatever is agreed on to the page.  Any takers?  Dale :-)  :-)