From: Bill Kenworthy <billk@iinet.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Heads Up - glibc-2.27 breaks my system
Date: Sun, 4 Feb 2018 07:21:13 +0800 [thread overview]
Message-ID: <13505bb7-59fb-9c04-49ed-330dec53fbd5@iinet.net.au> (raw)
In-Reply-To: <ECG2WIIQ.5AMCU36I.MKOZ4QLR@JKLOKMVG.W5CU7Y75.4SYPDRXD>
On 04/02/18 01:34, Helmut Jarausch wrote:
> On 02/03/2018 04:11:33 PM, Marc Joliet wrote:
>> Am Samstag, 3. Februar 2018, 10:50:53 CET schrieb Helmut Jarausch:
>> > On 02/03/2018 06:54:06 AM, 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
1. do another backup
2. take your last good binary package and unpack it in the root
directory - it is an "image" of that package as it sits in the file system.
3. rebuild that version of glibc by overiding emerge - comment out "die
"aborting to save your system" in /usr/portage/eclass/toolchain-glibc.eclass
I have done this a couple of times with gcc (when manual deletes have
gone rogue) but it should work with glibc as you have not recompiled any
new packages.
BillK
next prev parent reply other threads:[~2018-02-03 23:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-02 17:34 [gentoo-user] Heads Up - glibc-2.27 breaks my system Helmut Jarausch
2018-02-02 21:07 ` Floyd Anderson
[not found] ` <5x7d1x01i1kktTk01x7eRl>
2018-02-03 5:42 ` John Campbell
2018-02-03 5:54 ` Dale
2018-02-03 8:23 ` [gentoo-user] " Nikos Chantziaras
2018-02-03 14:08 ` Dale
2018-02-04 18:01 ` Nikos Chantziaras
2018-02-04 18:23 ` Dale
2018-02-03 9:50 ` [gentoo-user] " Helmut Jarausch
2018-02-03 15:11 ` Marc Joliet
2018-02-03 17:34 ` Helmut Jarausch
2018-02-03 17:56 ` Marc Joliet
2018-02-03 23:21 ` Bill Kenworthy [this message]
2018-02-04 11:52 ` Helmut Jarausch
2018-02-04 8:39 ` Neil Bothwick
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=13505bb7-59fb-9c04-49ed-330dec53fbd5@iinet.net.au \
--to=billk@iinet.net.au \
--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