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 via email to