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.
Upgrade question.
I have been running Sarge (testing) for about a year, running an occasional apt-get update/upgrade. When the big release occurred a few weeks ago, I stopped doing this because I didn't know if I needed to change anything to get the new version of testing.
Last night I read a few posts which said that apt-get update && apt-get upgrade would be ok if repositories pointed to 'testing'. Mine did, so I ran the upgrade.
Everything seems ok afterwards.
How can I verify the upgrade got the new 'testing' branch?
Is there a command that will display something like " ... running Sarge ..." or " ... running Etch ..." ?
Distribution: debian, gentoo, os x (darwin), ubuntu
Posts: 940
Rep:
the directory 'testing' within the repository of apt, always points to the current testing version of debian (basically a symlink)
as long as it says 'testing' in you apt sources file, you are fine.
sarge and etch are just codenames. the packages in those directoruies is what you should be interested in. it does not matter if packages are available under a different codename. the important part is, which packages (or which package versions) are installed on you computer.
as you wrote that you souces file does point to testing on not to sarge, you are fine... for you, nothing has ever changed, appart from the fact that you no longer run debian sarge but debian etch... everything else is still the same.
Originally posted by rip When the big release occurred a few weeks ago, (...) I didn't know if I needed to change anything to get the new version of testing.
---That reminds me of the sarge/testing/etch jam that arised when the first netintall cd was released buggy just the day Sarge became 'stable'....because the /etc/apt/sources.list that used to write was still pointing to 'testing' ...So when you went for a Sarge installation you ended up installing Etch if you were not aware
At work I run Fedora core 3 and 'cat /etc/redhat-release' shows "Fedora Core release 3 (Heidelberg)" .
On Debian, there is less info. Before I upgraded, a 'cat /etc/debian_version' showed just "3.1" and nothing else. Afterwards it showed "testing/unstable" . Not as informative as Fedora. I just thought that more info could be found.
Oh well, just being curious...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.