public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Marc Joliet <marcec@gmx.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Heads Up - glibc-2.27 breaks my system
Date: Sat, 03 Feb 2018 16:11:33 +0100	[thread overview]
Message-ID: <1683273.yOecnO1sV8@thetick> (raw)
In-Reply-To: <3KMHQSSJ.5OF2LM5M.6F23E2P7@7X75SCQB.6UAZSSP5.KSKAEDEJ>

[-- Attachment #1: Type: text/plain, Size: 1351 bytes --]

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
> > it and it fail miserably? 
> 
> I've tried to binary emerge my previous version. This didn't succeed
> since
> the ebuild disallows downgrading glibc.
> 
> Luckily I had backuped my system just 20 hours ago.

Having up-to-date backups is always good :) .

> Does anybody know how to restore ONLY those files which are
> more recent on the target file system.
> (My whole back is 124 Gb large which is a lot to copy back)

If you can access the backups like a normal file system, then using rsync with 
the --update option looks to me like what you want:

"-u, --update                skip files that are newer on the receiver".

> Many thanks for a hint,
> Helmut

HTH
-- 
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-02-03 15:11 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 [this message]
2018-02-03 17:34           ` Helmut Jarausch
2018-02-03 17:56             ` Marc Joliet
2018-02-03 23:21             ` Bill Kenworthy
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=1683273.yOecnO1sV8@thetick \
    --to=marcec@gmx.de \
    --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