On Friday 25 May 2012 18:23:37 Tom H wrote:
> On Fri, May 25, 2012 at 11:53 AM, Mika Suomalainen
>
> <mika.henrik.mai...@hotmail.com> wrote:
> > On 25.05.2012 15:49, Ralf Mardorf wrote:
> >> On Fri, 2012-05-25 at 17:37 +0500, Muhammad Yousuf Khan wrote:
> >>> deb http://security.debian.org/ squeeze/updates main
> >>> deb-src http://security.debian.org/ squeeze/updates main
> >>> deb http://backports.debian.org/debian-backports squeeze-backports main
> >>> deb http://ftp.de.debian.org/debian sid main
> >>
> >> You're issue is related to the sid repository. If you need something
> >> from sid, then uncomment it and after that comment it. Don't feel secure
> >> using pinning.
> >>
> >> You can name the repositories "stable" instead of "squeeze", so it will
> >> use "stable" what ever Debian "stable" is named.
> >
> > Is it safe to use "stable" instead of "squeeze"? Are there usually any
> > conflicts or anything what would need "full-upgrade" whenever new
> > "stable" is named?
>
> No.
>
> No need for "aptitude full-upgrade", even "apt-get upgrade"/"aptitude
> safe-upgrade" will pull in wheezy (partially) when it becomes
> "stable".

I prefer to use aptitude full-upgrade routinely - but I have the code name in 
my sources.list, not stable or testing.  I then change the code name when I 
want to get the more recent version.  So, Squeeze not stable, Muhammad.  you 
could get in quite a mess at the changeover point from Squeeze to Wheezy if 
you have stable in your sources.list, as several people have pointed out.

I can't comment on your Windows analogies as I don't use Windows.  I think 
that you need to expect that Linux will be different from whatever you used 
in Windows.  They are very different OSs.

FWIW, I do most of my admin from the CLI, including updating and upgrading.  
So yes, it can be done from the CLI.

Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201205252130.54213.lisi.re...@gmail.com

Reply via email to