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 7B87013838B for ; Tue, 16 Sep 2014 18:06:03 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 028ABE0B5F; Tue, 16 Sep 2014 18:05:57 +0000 (UTC) Received: from mail143c7.megamailservers.com (mail121c7-2520.megamailservers.com [69.49.98.23]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id DBC2AE0B1A for ; Tue, 16 Sep 2014 18:05:55 +0000 (UTC) X-POP-User: admin@sys-concept.com X-VIP: 69.49.109.100 Received: from syscon7.localdomain (S01060050da7ae68c.ed.shawcable.net [68.149.90.13]) by mail143c7.megamailservers.com (8.13.6/8.13.1) with ESMTP id s8GI5rTZ018721 for ; Tue, 16 Sep 2014 14:05:55 -0400 Received: by syscon7.localdomain (Postfix, from userid 1000) id CCDEF200280; Tue, 16 Sep 2014 12:05:55 -0600 (MDT) Date: Tue, 16 Sep 2014 12:05:55 -0600 From: Joseph To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: gentoo Message-ID: <20140916180555.GE26321@syscon7> References: <20140916042924.GA26321@syscon7> <20140916150243.GD26321@syscon7> 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; format=flowed Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.22 (2013-10-16) X-CTCH-RefID: str=0001.0A02020A.54187C03.004A,ss=1,re=0.000,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0 X-CTCH-VOD: Unknown X-CTCH-Spam: Unknown X-CTCH-Score: 0.000 X-CTCH-Rules: X-CTCH-Flags: 0 X-CTCH-ScoreCust: 0.000 X-CSC: 0 X-CHA: v=2.1 cv=cZDr8BzM c=1 sm=1 tr=0 a=C3ZDv51cNVt4vJz/79I2xQ==:117 a=C3ZDv51cNVt4vJz/79I2xQ==:17 a=SDcUNfBxAAAA:8 a=BDKbP5mgAAAA:8 a=Unq3plm5DvEA:10 a=M1kyBYkWWGkA:10 a=m5wF0CZtLr4A:10 a=nDghuxUhq_wA:10 a=8nJEP1OIZ-IA:10 a=pGLkceISAAAA:8 a=p7E_tW9oKueKJzLEuLoA:9 a=wPNLvfGTeEIA:10 X-Origin-Country: CA X-Archives-Salt: 589cde48-94ec-4996-9196-033ef41b444d X-Archives-Hash: 04d3b5bc2852e163c034a80dce9158f1 On 09/16/14 17:57, J. Roeleveld wrote: [snip] >> >>solved all the problems. >>I was at python:3.3 but for some reason or another (mostly my fault) I >>did not unmerged python:3.1 >> >>When it comes to upgrading be-weekly maybe but from my experience, when >>I was doing it more often, occasionally, I ended up with a broken >>system that was caused by new >>packages. >>I have 4-boxes at home and two boxes at a remote location. So the >>boxes at home get upgraded first, I wait a week, just to make sure >>every program works and >>then I upgrade one box on a remote location, wait one week again and >>upgrade the second box (the backup) in the remote location. >>So doing it even every second week would be too often for this routine. >> >>The boxes are "rsync" to one local box. > >I am starting to wonder. >How exactly do you upgrade the other machines? >Copying the entire filesystem? I rsync one local server and all other machine are rsync to it. My main idea is trying not to introduce to many newer versions packages as in the past I've notice that that could cause the problem. The is no need for sarcasm. I basically do what works and I do learn from my experience (sometimes :-/). -- Joseph