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.
If your sources.list file already says "lenny" then you're safe and you've already made the change (assuming you've been doing any security updates).
If your sources.list says "testing" and you've been doing updates, you can't go back to stable.
If your sources.list says "testing" but you haven't done any updates since Lenny became stable, you should be able to just change "testing" to "lenny" and then do an upgrade.
Upgrades are always a risk to production environments. Make sure you have a good backup handy before you start.
Hi
I want to upgrade lenny testing to lenny stable,May this upgrade risk my enterprise server ??
thanks for any help or guidance
Could you paste a copy of your /etc/apt/sources.list ?
In all likelihood if you specified lenny directly and have been updating software, you ARE running lenny stable.
If you specified testing and have been updating, you're not running lenny anymore you're running squeeze (if memory serves me) and attempting to downgrade from squeeze to lenny would probably not be a pleasant experience.
IMO you really shouldn't use the non-distribution specific monikers in a production environment.
dear pljvaldez,is there anyway to find that any update have been done??
Does not apt have any history ??
I think,history is necessary for apt,Do not you think? if so suggest to developer of apt
You can try looking at /var/log/dpkg.log and see if there has been any activity since February 14, 2009 (when lenny was released as stable). If there has, you're probably stuck and have to use squeeze (current testing).
Hi Nima,
UDo you recall executing such a command in the last 4 months?
jdk
unfortunately I was not admin for this server,because I remember executed commands
if I change source.list to lenny and update repository package and after that I run upgrade,Is determined which packages will be updated or upgraded ?? Is prompt me for accept that??
Yes, if you use aptitude it will always tell you want it is going to do and ask if you agree before doing it. If there are dependency problems, aptitude will alert you and even offer solutions. I would avoid using a gui for updating/ugrading packages. You get much more information using the CLI and aptitude.
cheers,
jdk
dear pljvaldez,is there anyway to find that any update have been done??
Does not apt have any history ??
I think,history is necessary for apt,Do not you think? if so suggest to developer of apt
thanks for any guide or instruction
If you didn't have a broken system and you updated with that sources list you may now.
Code:
# Main Debian Mirror
deb http://ftp.us.debian.org/debian/ lenny main contrib non-free
#deb-src http://ftp.us.debian.org/debian/ lenny main contrib non-free
# Security Updates Mirror
deb http://security.debian.org/ lenny/updates main contrib non-free
#deb-src http://security.debian.org/ lenny/updates main contrib non-free
What you want is something like this.
You're actually referencing two different distributions... squeeze and lenny.
They should both specify lenny or both specify testing/stable/unstable. They should never reference different versions.
# Main Debian Mirror
deb http://ftp.us.debian.org/debian/ lenny main contrib non-free
#deb-src http://ftp.us.debian.org/debian/ lenny main contrib non-free
# Security Updates Mirror
deb http://security.debian.org/ lenny/updates main contrib non-free
#deb-src http://security.debian.org/ lenny/updates main contrib non-free
What you want is something like this.
You're actually referencing two different distributions... squeeze and lenny.
They should both specify lenny or both specify testing/stable/unstable. They should never reference different versions.
If I want to install squeeze now, and have my source list file as
Code:
# Main Debian Mirror
deb http://ftp.us.debian.org/debian/ squeeze main contrib non-free
#deb-src http://ftp.us.debian.org/debian/ squeeze main contrib non-free
# Security Updates Mirror
deb http://security.debian.org/ squeeze/updates main contrib non-free
#deb-src http://security.debian.org/ squeeze/updates main contrib non-free
Then, when squeeze becomes stable, will I have to do any changes ?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.