[SOLVED] Upgraded to Wheezy; Now what with the repositories?
DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Upgraded to Wheezy; Now what with the repositories?
Hello,
Had the day off and decided to include the testing repositories in my sources.list to upgrade to Wheezy, but now have these two questions;
Would the safest thing now be to exclude the stable / squeeze repositories from my sources list and just stick with the testing ones (ie; untill wheezy becomes the "stable one)?
What would you recommend? (yes, I did set /etc/apt/preferences to prioritize squeeze, BTW, which would also be part of the question. Should I now prioritize testing?)
I know it sounds noobish to ask, but that's what I am!
Here's my sources.list, anyway, as is;
Code:
## Debian security updates:
deb http://security.debian.org/ squeeze/updates main contrib non-free
deb-src http://security.debian.org/ squeeze/updates main contrib non-free
## Debian.org:
deb http://ftp.debian.org/debian/ squeeze main contrib non-free
deb-src http://ftp.debian.org/debian/ squeeze main contrib non-free
## Debian US mirror:
deb ftp://ftp.us.debian.org/debian/ squeeze main contrib non-free
deb-src ftp://ftp.us.debian.org/debian/ squeeze main contrib non-free
## WINE
deb http://www.lamaresh.net/apt squeeze main
## SKYPE
deb http://download.skype.com/linux/repos/debian/ stable non-free
## Google
deb http://dl.google.com/linux/deb/ stable non-free
## Multimedia stable
deb http://www.debian-multimedia.org stable main non-free
deb-src http://www.debian-multimedia.org stable main non-free
#This one was working, so I am leaving it be...
deb http://ftp.br.debian.org/debian-multimedia stable main
deb-src http://ftp.br.debian.org/debian-multimedia stable main
## Debian Multimedia squeeze:
deb http://mirror.home-dn.net/debian-multimedia squeeze main non-free
deb-src http://mirror.home-dn.net/debian-multimedia squeeze main non-free
################################################################
##TESTING
## Debian.org testing:
deb ftp://ftp.debian.org/debian testing main contrib non-free
deb-src ftp://ftp.debian.org/debian testing main contrib non-free
## Debian Multimedia testing:
deb http://mirror.home-dn.net/debian-multimedia testing main
deb-src http://mirror.home-dn.net/debian-multimedia testing main
Copy the sources.list to a backup file (like: cp sources.list sources.list.bak) then comment out all lines referring to squeeze and/or adjust said lines to get the appropriate packages from Testing in the original file. Do the required apt* update && apt* dist-upgrade and you should see the system working its way towards a full Testing.
(apt* means either apt-get or aptitude, whatever you prefer )
Distribution: Debian Testing, Stable, Sid and Manjaro, Mageia 3, LMDE
Posts: 2,628
Rep:
You have all the repos you need under your testing header. There is no sense in having stable repos enabled at all.
Apt-get is the recommended way to upgrade since Squeeze was released. Aptitude is not going to mess anything up though.
Aptitude has always been the recommended upgrade tool and I have always used apt-get because I like it better. Never had any problems.
I suspect the same would be true now of Aptitude.
You will see the difference in package versions between stable and testing and realize that the stable repo is of no use to you. You do have a big upgrade/dist-upgrade headed your way. Having weird things in your sources list is not going to help dpkg get the upgrade straight.
Do not mess with what is the "favored" version. Just one versions repo. Any thing else can wait until you have an upgraded OS.
Advice taken, thanks. Only the repositories under TESTING heading were kept, plus I added one (well two, technically, I suppose) additional repsoitory, as it did not seem to complain when tried. This is despite my being led to believe there are no security updates for testing (?)
Code:
deb http://security.debian.org/ wheezy/updates main contrib non-free
deb-src http://security.debian.org/ wheezy/updates main contrib non-free
Indeed, it was a big apt-get dist-upgrade. It has all gone without major problems (so far). I am happy. Thanks again.
Last edited by feeblebrain; 08-06-2011 at 11:55 PM.
(yes, I did set /etc/apt/preferences to prioritize squeeze, BTW, which would also be part of the question. Should I now prioritize testing?)
If I understand what you're trying to do now, I don't think you need a preferences file any more unless you want to do some alt-pinning with unstable (sid).
ciao,
jdk
Distribution: Debian Testing, Stable, Sid and Manjaro, Mageia 3, LMDE
Posts: 2,628
Rep:
Security updates in Testing and Sid are handled by the package maintainers not the security folks. That is why those repos do not exist in Testing or Sid.
I would *not* comment out the security entries.
They are used occasionally if a bug of sufficient severity is found.
I have seen this happen myself running Testing.
There is no security entry used for Unstable.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.