From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id C687E1381F3 for ; Wed, 12 Dec 2012 15:11:56 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D378921C0A4; Wed, 12 Dec 2012 15:11:42 +0000 (UTC) Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 9693621C06B for ; Wed, 12 Dec 2012 15:10:33 +0000 (UTC) Received: from localhost (66-208-231-133.ubr01a.rte20201.pa.hfc.comcastbusiness.net [66.208.231.133]) by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis) id 0MIL1r-1TiW2T3dR1-00480B; Wed, 12 Dec 2012 10:10:32 -0500 Date: Wed, 12 Dec 2012 09:10:30 -0600 From: Bruce Hill To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] System maintenance procedure? Message-ID: <20121212151029.GY8486@server> References: <20121208220616.44fb92ae@khamul.example.com> <20121208232507.6f348f86@khamul.example.com> <20121208224950.40759f8e@digimed.co.uk> <50C3CB44.7070307@gmail.com> <20121209131841.GX23914@server> <20121209164824.18b9f563@digimed.co.uk> <20121211133610.GL8486@server> <20121212080524.2364bbed@khamul.example.com> 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=us-ascii Content-Disposition: inline In-Reply-To: <20121212080524.2364bbed@khamul.example.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Provags-ID: V02:K0:2e5UZp841gfAUXLXEoQ2ovEPnwKmayL0Szkmcf9mBPo tylJoMjitk956/UtqxFdzZ8SpoT/727Pplx4vJ+OCDilOEvukv 8sfaExda1Kj6Ag3CJ8H5CbrjUPLAlsZB9qa0mpl2H+GkzYfTDS r6vUTvxX0qK5fqzdCdcWtrMK2BXwh3/S8Ovv+k1ZTVObeZbKPo b1s462FF4/1mSj+MSilWIQwJ6PMVTUWC5n6PyKsXGIsFqQt5P1 WMNksUBUpmPoGksCMn/XG7o705yMNaWYqxgBkYKipPbneshv6F +W9qvrdmTrjUBHCHs34C6CiS1ZLv6zhB5uHNluR89kFYPXfSak /vOptE1UrlpnVDFCZ+o0= X-Archives-Salt: 329bc8e4-73fa-46cf-92f1-f0304e53117d X-Archives-Hash: 0feee2d113b8e2a15b9ad46cc61a313a On Wed, Dec 12, 2012 at 08:05:24AM +0200, Alan McKinnon wrote: > > Of course, all this assumes that your version of portage supports > @preserved-rebuild > > To use it, you simply notice the portage message right at the end of an > emerge and run "emerge @preserved-rebuild" - it's just a regular emerge > using a particular built-in set that has a defined purpose Perhaps no one ever bothered to mention which version of portage DOES support @preserved-rebuild (not mentioned in the ChangeLog until portage-2.2.0_alpha47 When fielding support questions it's proper to ask what version of the particular software in question is being used. -- Happy Penguin Computers >') 126 Fenco Drive ( \ Tupelo, MS 38801 ^^ support@happypenguincomputers.com 662-269-2706 662-205-6424 http://happypenguincomputers.com/ Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting