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 808121382C5 for ; Sat, 3 Feb 2018 14:09:05 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 79B95E0B2E; Sat, 3 Feb 2018 14:08:58 +0000 (UTC) Received: from mail-yw0-x231.google.com (mail-yw0-x231.google.com [IPv6:2607:f8b0:4002:c05::231]) (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 00C65E0B1A for ; Sat, 3 Feb 2018 14:08:57 +0000 (UTC) Received: by mail-yw0-x231.google.com with SMTP id t201so15369853ywf.1 for ; Sat, 03 Feb 2018 06:08:57 -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=iysUrVuDpNvLDZzzveWwTzjdQkIWFNaXVmJ/TCPxpH8=; b=YtsfkjVF9bHbB41IJqmtbJ8D4iNYPMFg+DyqAnlxhNsKrciDkfYpNTEEqoEozGM3NM EdmpI2EVkuspxntgz8d3TjViXoRbxB17TfCCWqSw3cKdL4LnxXjfwfL6yU+xC9JGM+Id B507O71hsD9+29PsKdPN8ytNk49C+njrPVI1U2I9KL1ms5I5vF7LWkwQNzr6vigRXQJg oL4ZWy6AFa2eUfHvil6ajQ3PW7IbYCF+PCQRc7SgR6kU4CVNI/SgqjF3hCuqcDKB5lO7 0AQDRZbsAhig/hdibD+MMXbjIKcUUMjlRgnLcpuQKt7q9D7m/ClWrWm4lTi81h/STcJj aR7g== 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=iysUrVuDpNvLDZzzveWwTzjdQkIWFNaXVmJ/TCPxpH8=; b=AC+o4eUGu7ntusw+GZ7eTAt0EBxHnk32FlisJ111Yk595MzCRDseu+5u4Lx7NCNwIY DLiAC/4U7gRmMoRLifzXbaELBSw7HdaXc9mcA3pqm/zTQrgZN+Oylt9p1R5GQM0P4cVh 4AIW1mXrXt6Q5eOlHhTFmFbICKILxq5PIRqAzQEB8ik2wl3ym/6Oqilod4a4IRjZrznI 1J3/WMtul57q7zXyy/iOw0vn/QQCTsq3sqPQqluAgvzmAYQp2vWb6qOYp+TmF/cYt486 zHuIFcDSwQQfrHKD5c5iZrB9Ng0G1wkOOqn9RYN99yMtASgDXNnZ2GeddwsXmvN9P1H9 2qPg== X-Gm-Message-State: APf1xPAPX2Pz2pM/KINVS1Orpzw5zjNqMgVgyCckSNqjNFKsarz7yraD CTYuyU7keipvQ3BV1FGvEe0= X-Google-Smtp-Source: AH8x226a7nHmKBl8fTGjk3SU2gnxR1SO2B4cTqxzeO1R74dbluE+M4IjD0MSSDH8ZD926YxrkOZqpg== X-Received: by 10.129.61.20 with SMTP id k20mr770011ywa.471.1517666937051; Sat, 03 Feb 2018 06:08:57 -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 y187sm1595161ywy.57.2018.02.03.06.08.55 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 03 Feb 2018 06:08:56 -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> From: Dale Message-ID: <6947ed70-7549-65ef-a8e9-345e2757d084@gmail.com> Date: Sat, 3 Feb 2018 08:08:55 -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: 0cc05af0-5694-4faf-b0de-13202bd3ef45 X-Archives-Hash: 07dbc11ae1cdcb16b6f17d77b5eb88c6 Nikos Chantziaras wrote: > On 03/02/18 07:54, Dale wrote: >> While on this topic, I have a question about glibc.  I have it set in >> make.conf to save the binary packages.  Generally I use it when I need >> to go back shortly after a upgrade, usually Firefox or something. >> However, this package is different since going back a version isn't a >> good idea.  My question tho, what if one does go back a version using >> those saved binary packages?  Has anyone ever did it and it work or did >> it and it fail miserably? > > 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. > > This whole thing is not actually special to glibc. Other libraries > work in a similar manner. You can't just link other software against a > new version of the library, then remove the library and replace it > with an older one. It might result in breakage. But glibc is used by > almost everything, it's not "just a library", it is *the* library, and > so it has a special protection to prevent a downgrade. You can bypass > that protection and downgrade anyway, but then you need to know what > you're doing and how to restore your system correctly. If any > sys-devel packages are affected, you might not be able to do it. If > only end-user packages are affected which are not used during an > emerge, then it's quite safe to downgrade. > > > 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.  I wonder, is this sort of info on Gentoo's wiki?  If not, shouldn't it be?  I've always read that downgrading is a bad idea and strongly discouraged but if one runs unstable on a regular basis or just hits that random corner case bug, one may run into this even if one doesn't have the experience to know how to put the broken pieces back together again.  Thanks for the info.  At least there is a option, even if it might get interesting.  ;-) Dale :-)  :-)