public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joseph <syscon780@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: gentoo
Date: Tue, 16 Sep 2014 12:05:55 -0600	[thread overview]
Message-ID: <20140916180555.GE26321@syscon7> (raw)
In-Reply-To: <d3bff769-cd11-4168-ae0a-d47e3eecfe10@email.android.com>

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


  reply	other threads:[~2014-09-16 18:06 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-16  4:29 [gentoo-user] gentoo Joseph
2014-09-16  5:23 ` [gentoo-user] removing preserve rebuild Joseph
2014-09-16 10:45   ` Tomas Mozes
2014-09-16 12:01   ` Neil Bothwick
2014-09-16 12:20   ` Alan McKinnon
2014-09-16 13:52     ` Joseph
2014-09-16 14:44       ` Alan McKinnon
2014-09-16 14:18 ` [gentoo-user] Re: gentoo James
2014-09-16 15:02   ` Joseph
2014-09-16 15:57     ` J. Roeleveld
2014-09-16 18:05       ` Joseph [this message]
2014-09-16 19:11         ` Alan McKinnon
2014-09-16 19:38           ` Joseph
2014-09-16 19:58         ` James
2014-09-16 20:23           ` Joseph
2014-09-16 20:42             ` Alan McKinnon
2014-09-16 21:28             ` James
     [not found] <200412051508.59017.dlw@hei.net>
2004-12-06  0:24 ` Gabriel M. Beddingfield
2004-12-06  5:14   ` Ow Mun Heng

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=20140916180555.GE26321@syscon7 \
    --to=syscon780@gmail.com \
    --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