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 447C31382C5 for ; Sat, 3 Feb 2018 17:57:02 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D903DE0B5E; Sat, 3 Feb 2018 17:56:54 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (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 2067FE0B35 for ; Sat, 3 Feb 2018 17:56:53 +0000 (UTC) Received: from thetick.localnet ([93.181.44.247]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0M3zne-1ezyJP3YcU-00ra6E for ; Sat, 03 Feb 2018 18:56:41 +0100 From: Marc Joliet To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Heads Up - glibc-2.27 breaks my system Date: Sat, 03 Feb 2018 18:56:28 +0100 Message-ID: <12769143.OtNcr2bO8Y@thetick> In-Reply-To: References: <1683273.yOecnO1sV8@thetick> 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 Content-Type: multipart/signed; boundary="nextPart3237776.naWBnLPt3h"; micalg="pgp-sha256"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:Ck4zbDtEbYa3jZmixr+/E0GaHKnJfLjc/YcitJ7cT+ir9XOv9aK 9ZXF8ATtheOvJoA6fbhlAAQTO9GJYvgKKpH99FrTrTy+dMZHDYqZ7bYtK3U5lM3146aY5DI kRdGL6WC0Er/W4pMNcTPSI77LpbnobxoLugUV9iQS/DlddjyzNpGw36Ipmf8DaicF5RtNHH i7KlU3K6cVhLQtwG9BMRA== X-UI-Out-Filterresults: notjunk:1;V01:K0:Ha9cv7/qTPg=:ZopDFI5FEuj/2vGf0RffjM 8FRyhcTarfWAND5castQYsg3aIvtSGQxfBSm8aUS2GD1UrgGjURaJ1vV+od5VsO3adz/jFMRA TxxKzMDqnr4jZTw85S0w5YM1bRdTaoVWGxM/Ce9SA5e+Ct0Zo42ite7rAQUBrsrrOCiTGEPJ7 6mclCVTTfaQ4GnJ3ONqXihc+mwctpRFuMSrgo9HS2Bqj7yn6MxIGewpPDkEMb228pK4n7rrqN QeHD5CHrpBW4Quqi8iI4MfkGejKbqFRRlyZcqmD8BepygM7+fbOTDVxWrevvuzjY99zGsU/jb TGjtmoLbTRVf3eaxsurWHFIKTz2rhzkvvZ5uxRc2WHWnj/6YP5jxSrHlMmCmMG8YnmiDMVyoa IjFlM0BNV1v8tFyVBfPS+khwXRO7j4auSjKMH1O3N3vk68xWwesEwuH7bebc8RyQFmbTEgo+P eioYaVCPbWj8TcbXS2q3Bm6kvtPlUOPCd3ip/kyHfrdSgyUHQ6jvmpz+xvJFYE2W/7moMm1T8 0q42nXSMRGxCgt67XJ9B8HBhcaZaVPY/BA/QWqF3iUnAKATB/cUtaHmrinMD7l5A6lBDdEQxT cGvRHKv63ZfqyAOdlCmLiGiz8ek80G2Qj9qYgVrJCutOC45cPHNIagxIS7qNqM5oQRwcY1DMW /V4IzIXI0kftmTSYOViNxRheGXhnfIvdRoWO3X3/Bac/0+c8ycK5Mz+xeymNkALVRQrNUi6PX +phY5Z1uubCtarVFOUthiUTYzHpby/DHcZltMC5+kOxMJZO8fFUI8ZaVaeVGBzoXYWurkq2s3 wv0D1udlLoQdDK+0KXtGPsnXfHnnA== X-Archives-Salt: 2443e9f1-a457-45c0-ba47-ff0b390d90b3 X-Archives-Hash: ec43c16ece8ae758e760fe1f7a2dd22c --nextPart3237776.naWBnLPt3h Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Am Samstag, 3. Februar 2018, 18:34:11 CET schrieb Helmut Jarausch: > 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 > > > > 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". > > High Marc, > I think I need the opposite : > only update files which are newer on the receiver Ah, sorry, I misread that (in your case it wouldn't make any sense, either). Although in that case, shouldn't normal rsync do what you want? It won't update files that haven't changed since the backup (determined by default by comparing file size and mtime, see rsync(1)). > Thanks, > Helmut HTH -- Marc Joliet -- "People who think they know everything really annoy those of us who know we don't" - Bjarne Stroustrup --nextPart3237776.naWBnLPt3h Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEax7Ya5gDQFOJHKGQv9DmhiyIePQFAlp198wACgkQv9DmhiyI ePTjGhAAszQGE+jAymX+3lyuncLd4bgLgEu5Ch8YbzyZHkQDQ0tHLPgu10Vhqe8r xe33JGiusBDtmXB51/jzpyPBOP14/FKENEYcYndOo9Pl/U3Y9g8JRK3A6T4iwMuh uePA4gCRMt62rxm1pVPRoqPnEJ/ycY5oy5qv3AHsBeBhTeO9/rWOQftJuSjpNN7t Q/QZlyjR5cA+YI3jr9Qxkp0sg81v2GwaVC2pBpFhS86AnP7Wbenybn8B79kR5eO2 7JzzvrNqkbtPaXkMu50fW2a3EqBH+DVLB97whMZq1TrCnbxBFcOeZa/+anzEIA4Q b78DP/SPSUcnsg0mC6tVnjzLxjTvBZMF9L6zT8tjrPok4BDIIkkHUYSgP/U4J9xd kimbykj0nlP6ZES4YfEtRSuERk/Otp/7xtvjq9uhitFVhIppF65THBd4DGUl9Klv KCc0jylOY4/XQTH1e0kSBf2cGwR0ufpIvqPWkrYvIqkvcP978TWle/9bu5YMUxWU qd5AakQi4JHTHtV15CGJuz02tMj0hIKKFex7NwVyDpzndr0H/mqCfauHrv4lMqch gUayVYyT6YMQFfkFKyJ7Kl3rMwVVPuu5vRzxjgYBsb6hLv052VSuZLMzp9LCOOXn Y9akHdbiWh3agLQW4DDmEbE8ie8edpARpmR98Tgfy6PhvZJdY64= =eLQI -----END PGP SIGNATURE----- --nextPart3237776.naWBnLPt3h--