On Fri, Jan 24, 2014 at 1:06 PM, Brian a...@cityscape.co.uk wrote:
On Fri 24 Jan 2014 at 12:52:05 -0500, Tom H wrote:
On Thu, Jan 23, 2014 at 6:47 PM, Brian a...@cityscape.co.uk wrote:
On Thu 23 Jan 2014 at 17:52:00 -0500, Bob Bernstein wrote:
At any rate, to move from, say, squeeze, to
On Sun 02 Feb 2014 at 15:22:44 -0500, Tom H wrote:
You hadn't specified from squeeze to qheezy and you were therefore
implying that it was a general approach.
In my own mind I thought I was responding to the previous post:
At any rate, to move from, say, squeeze, to wheezy, my approach
On Sb, 25 ian 14, 15:25:18, Brian wrote:
On Sat 25 Jan 2014 at 20:51:46 +0900, Osamu Aoki wrote:
I think we are doing our best avoid complications but the canonical
place for the recommended way is the Release Notes. Nothing else.
So as a baseline, process you described is fine. But
Hi,
On Fri, Jan 24, 2014 at 10:25:01AM +, Brian wrote:
On Fri 24 Jan 2014 at 11:54:12 +0200, Andrei POPESCU wrote:
The recommended way is specific to each release and thoroughly
documented in the Release Notes.
Which is where I got what I wrote from:
I bet it was only for the
On Sat 25 Jan 2014 at 20:51:46 +0900, Osamu Aoki wrote:
Hi,
On Fri, Jan 24, 2014 at 10:25:01AM +, Brian wrote:
On Fri 24 Jan 2014 at 11:54:12 +0200, Andrei POPESCU wrote:
The recommended way is specific to each release and thoroughly
documented in the Release Notes.
Which
On Jo, 23 ian 14, 23:47:11, Brian wrote:
On Thu 23 Jan 2014 at 17:52:00 -0500, Bob Bernstein wrote:
At any rate, to move from, say, squeeze, to wheezy, my approach
would be to edit my sources.list, replacing all instances of
squeeze with wheezy, and then running
# apt-get update
#
On Fri 24 Jan 2014 at 11:54:12 +0200, Andrei POPESCU wrote:
The recommended way is specific to each release and thoroughly
documented in the Release Notes.
Which is where I got what I wrote from:
If the system being upgraded provides critical services for your
users or the network[2],
On Thu, Jan 23, 2014 at 6:47 PM, Brian a...@cityscape.co.uk wrote:
On Thu 23 Jan 2014 at 17:52:00 -0500, Bob Bernstein wrote:
At any rate, to move from, say, squeeze, to wheezy, my approach
would be to edit my sources.list, replacing all instances of
squeeze with wheezy, and then running
#
On Fri 24 Jan 2014 at 12:52:05 -0500, Tom H wrote:
On Thu, Jan 23, 2014 at 6:47 PM, Brian a...@cityscape.co.uk wrote:
On Thu 23 Jan 2014 at 17:52:00 -0500, Bob Bernstein wrote:
At any rate, to move from, say, squeeze, to wheezy, my approach
would be to edit my sources.list, replacing all
On Thu, Jan 23, 2014 at 4:31 PM, Robin rc.rattusrat...@gmail.com wrote:
Were those users using Debian stable? I use Sid so I usually
dist-upgrade as long it isn't going obviously affect my system, i.e
removing applications I want to keep.
My process on sid is
apt-get update apt-get
A thread about dist-upgrade has me confused. In my experience
I have only ever run 'apt-get dist-upgrade' when I wanted to move
from one release to the next, say, from squeeze to wheezy.
Similarly, if I wanted to insure I had the latest versions of
packages already installed (and any/all
Bob,
It was my understanding that dist-upgrade was only needed to resolve issues
that couldn't be resolved by upgrade. I have moved from wheezy to jessie
with a simple aptitude update and didn't need the dist-upgrade. If this is
incorrect I would love to know cause I ran into some issues with my
On 23 January 2014 20:51, Bob Bernstein poo...@ruptured-duck.com wrote:
A thread about dist-upgrade has me confused. In my experience I have only
ever run 'apt-get dist-upgrade' when I wanted to move from one release to
the next, say, from squeeze to wheezy.
Similarly, if I wanted to insure
On 23/01/14 20:51, Bob Bernstein wrote:
A thread about dist-upgrade has me confused. In my experience I have
only ever run 'apt-get dist-upgrade' when I wanted to move from one
release to the next, say, from squeeze to wheezy.
Similarly, if I wanted to insure I had the latest versions of
Bob Bernstein:
But the thread currently underway about dist-upgrade suggests that
users are running it rather routinely, and not at all necessarily to
move from one release to the next.
Can someone please point out what I am missing?
What you are doing is generally the safe way. apt-get
Thanks to all who have chimed in!
On Thu, 23 Jan 2014, Klaus wrote:
When for instance a new version of an already installed package
depends on a previously not installed library, then apt-get
update cannot update this pkg. You need dist-upgrade for that
job.
Aha. Thx for the RTFM; I had
On Thu 23 Jan 2014 at 17:52:00 -0500, Bob Bernstein wrote:
At any rate, to move from, say, squeeze, to wheezy, my approach
would be to edit my sources.list, replacing all instances of
squeeze with wheezy, and then running
# apt-get update
# apt-get dist-upgrade
That as far as memory
At any rate, to move from, say, squeeze, to wheezy, my approach would
be to edit my sources.list, replacing all instances of squeeze with
wheezy, and then running
# apt-get update
# apt-get dist-upgrade
It's not always that straightforward for upgrades between major
releases. You might
18 matches
Mail list logo
