From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1PA99V-0003kd-Ft for garchives@archives.gentoo.org; Sun, 24 Oct 2010 22:34:58 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A5C8DE05A4; Sun, 24 Oct 2010 22:34:27 +0000 (UTC) Received: from mail-ew0-f53.google.com (mail-ew0-f53.google.com [209.85.215.53]) by pigeon.gentoo.org (Postfix) with ESMTP id 649E2E05A4 for ; Sun, 24 Oct 2010 22:34:27 +0000 (UTC) Received: by ewy10 with SMTP id 10so1556978ewy.40 for ; Sun, 24 Oct 2010 15:34:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :user-agent:references:in-reply-to:mime-version:content-type :content-transfer-encoding:message-id; bh=EoyGG98d28GZ3SLH0V+qfC/VxiXJ9K3/UU7JqAD6D98=; b=BwbLDj1vr1oyKjBeyuvhrUrCnNTs4vSW6qcOs24Z12I3AkkEQ3/Cv6pjkdQAUjVqib S+0O254aOLDtddxNA/gwL/ipwfEHfmR3AeYaQBPKnBq2HWL709bo0WEBHf/zWoQz+aOg jaiu9MPglJvHm0vpCe1uMPne7jgK6hkqLtrpY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:references:in-reply-to:mime-version :content-type:content-transfer-encoding:message-id; b=bI1bx4wPruXZOWXAndJh55Rto1YsKjzMG0TMFHzu8ru67Xy68y/XszZ9gMOdmjmWsG E6NEMfnQJ0wxhAI4MyTHN25rARU42gUm++H/ljIeMYGNFrTGMh9kwneHdgsxy9fTU8/7 hP2N4zP6tJ6n/kCBBvacw7r4mBpT+yeJayueg= Received: by 10.213.14.83 with SMTP id f19mr1351141eba.57.1287959666811; Sun, 24 Oct 2010 15:34:26 -0700 (PDT) Received: from nazgul.localnet (196-215-2-42.dynamic.isadsl.co.za [196.215.2.42]) by mx.google.com with ESMTPS id q58sm6622869eeh.21.2010.10.24.15.34.24 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 24 Oct 2010 15:34:25 -0700 (PDT) From: Alan McKinnon To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Preventing a package from being updated Date: Mon, 25 Oct 2010 00:34:59 +0200 User-Agent: KMail/1.13.5 (Linux/2.6.35-ck-r4; KDE/4.5.2; x86_64; ; ) References: <4CBC1C21.2020202@taydin.org> <201010222244.02415.alan.mckinnon@gmail.com> In-Reply-To: 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: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201010250034.59403.alan.mckinnon@gmail.com> X-Archives-Salt: 5b56cd32-b5f4-4e19-9832-3a180da133b0 X-Archives-Hash: eca6dd0533cc7e710dbc827993410753 Apparently, though unproven, at 13:50 on Saturday 23 October 2010, daid kahl did opine thusly: > > Don't worry about it. I'm not sure if portage-2.1.9.20 will deal with > > this automagically (I *think* it does these days and 2.2 definitely > > does) but if not just > > > > emerge -C shadow ; emerge -1 shadow > > > > then emerge -avuND world. > > > > No good technical reason for doing shadow first apart from getting it > > over and done with while you watch and confirm it works fine. Then do > > world and wander over to the kettle letting portage go on with doing > > it's thing unattended > > For my own comfort, on a case like this, if I didn't have the portage > FEATURE buildpkg or buildsyspkg turned on, I'd make sure that was on > and that I had a functional backup of shadow to install from binary, > in case something went very wrong. But I tend to be extremely > cautious in terms of how I maintain my system, and a lot of that > caution is just paranoia. Just because you're paranoid doesn't mean they're NOT out to get you :-) Or in this case, it doesn't mean it's not justified. I now have buildpkg enabled for @system - everything else I can re-run emerge to fix. After watching portage break python *twice* exactly a year apart, watching the exciting developments in python-3, after some horrendous shadow breakage 3 years ago and the convoluted upgrade path for bash 2 years ago, and someone's b0rked commit of glibc-2.12 to the tree quite recently, I feel entirely justified in keeping binary copies of @system around. It long ago stopped being paranoia and started being good old common sense (right up there with backups). -- alan dot mckinnon at gmail dot com