Paul Johnson wrote:
On Wednesday June 8 2005 1:32 pm, Jim Hall wrote:
Sounds good. Next link in the chain, will I have to use
'dist-upgrade'?
Yes, though you might find visual representation of what you're doing
helpful. You might want to do this instead:
apt-get install aptitude
Then,
Paul Johnson wrote:
On Wednesday June 8 2005 12:17 pm, Jim Hall wrote:
Now that Sarge is released, do I need to point 'update' 'upgrade'
to stable, or leave Sarge as the target?
It depends. Do you want to track Sarge or stable? Stable is always
the current release, Sarge is always
Now that Sarge is released, do I need to point 'update' 'upgrade' to
stable, or leave Sarge as the target?
Jim
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Wednesday 08 Jun 2005 20:17, Jim Hall wrote:
Now that Sarge is released, do I need to point 'update' 'upgrade' to
stable, or leave Sarge as the target?
No, you can do nothing, if you like.
Pointing it to stable would only do something once the next release happens.
Then, the new stable
Lee Braiden wrote:
On Wednesday 08 Jun 2005 20:17, Jim Hall wrote:
Now that Sarge is released, do I need to point 'update' 'upgrade' to
stable, or leave Sarge as the target?
No, you can do nothing, if you like.
Pointing it to stable would only do something once the next release happens.
On Wed, Jun 08, 2005 at 08:45:45PM +0100, Lee Braiden wrote:
On Wednesday 08 Jun 2005 20:17, Jim Hall wrote:
Now that Sarge is released, do I need to point 'update' 'upgrade' to
stable, or leave Sarge as the target?
No, you can do nothing, if you like.
Pointing it to stable would only
On Wed, Jun 08, 2005 at 03:32:31PM -0500, Jim Hall wrote:
Sounds good. Next link in the chain, will I have to use 'dist-upgrade'?
Those times I've used it have usually had bad results. If I can continue
to manually repair what's 'held back', that seems safer to me.
A dist-upgrade should be
Jim Hall wrote:
Lee Braiden wrote:
On Wednesday 08 Jun 2005 20:17, Jim Hall wrote:
Now that Sarge is released, do I need to point 'update' 'upgrade' to
stable, or leave Sarge as the target?
No, you can do nothing, if you like.
Pointing it to stable would only do something once the next
On Wed, Jun 08, 2005 at 08:27:55PM -0400, Tom Allison wrote:
Jim Hall wrote:
Lee Braiden wrote:
On Wednesday 08 Jun 2005 20:17, Jim Hall wrote:
Now that Sarge is released, do I need to point 'update' 'upgrade' to
stable, or leave Sarge as the target?
No, you can do nothing, if you
On Wed, Jun 08, 2005 at 09:08:20PM -0600, Paul E Condon wrote:
I strongly suspect that this is pure BS. I have never had a problem with
conflict resolution with either flavors of dist-upgrade, namely
apt-get dist-upgrade and
aptitude dist-upgrage. Both work for me.
Furthermore, the code for
On Wednesday June 8 2005 12:17 pm, Jim Hall wrote:
Now that Sarge is released, do I need to point 'update' 'upgrade'
to stable, or leave Sarge as the target?
It depends. Do you want to track Sarge or stable? Stable is always
the current release, Sarge is always Sarge.
--
Paul Johnson
On Wednesday June 8 2005 1:32 pm, Jim Hall wrote:
Sounds good. Next link in the chain, will I have to use
'dist-upgrade'?
Yes, though you might find visual representation of what you're doing
helpful. You might want to do this instead:
apt-get install aptitude
Then, once that is installed,
On Wednesday June 8 2005 5:27 pm, Tom Allison wrote:
Yesterday on the chat rooms it was claimed that using aptitude was
more successful and effective than using apt-get dist-upgrade.
Apparently aptitude is supposed to do the conflict resolution
better than dist-upgrade or apt-get.
apt is
On Wed, Jun 08, 2005 at 09:08:20PM -0600, Paul E Condon wrote:
On Wed, Jun 08, 2005 at 08:27:55PM -0400, Tom Allison wrote:
Yesterday on the chat rooms it was claimed that using aptitude was more
successful and effective than using apt-get dist-upgrade. Apparently
aptitude is supposed to
14 matches
Mail list logo
