
sublimepua wrote:I am coming to LMDE from a year or so of gentoo. My poor laptop can't handle the breakages or power drain of compiling anymore. That said, I don't like the idea of out of date software. Is moving from testing to unstable as simple as changing one word in /etc/apt/sources.list?
Is there a process that you would recommend to best handle the change?

sublimepua wrote:Is moving from testing to unstable as simple as changing one word in /etc/apt/sources.list?
Is there a process that you would recommend to best handle the change?







sublimepua wrote:I'm getting errors:
W: GPG error: http://deb.opera.com stable Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A2019EA84E7532C8
W: Failed to fetch http://security.debian.org/dists/unstab ... 6/Packages 404 Not Found [IP: 128.31.0.36 80]
W: Failed to fetch http://security.debian.org/dists/unstab ... 6/Packages 404 Not Found [IP: 128.31.0.36 80]
W: Failed to fetch http://security.debian.org/dists/unstab ... 6/Packages 404 Not Found [IP: 128.31.0.36 80]
E: Some index files failed to download. They have been ignored, or old ones used instead.
my /etc/apt/sources.list is:
deb http://packages.linuxmint.com/ debian main upstream import
deb http://ftp.debian.org/debian unstable main contrib non-free
deb http://security.debian.org/ unstable/updates main contrib non-free
deb http://www.debian-multimedia.org unstable main non-free
Do I omit the security.debian.org source?
sudo apt-key adv --keyserver keyring.debian.org --recv-keys A2019EA84E7532C8


deb http://packages.linuxmint.com/ debian main upstream import
deb http://http.us.debian.org/debian/ unstable main contrib non-free
deb-src http://http.us.debian.org/debian/ unstable main contrib non-free
deb http://www.debian-multimedia.org sid main non-free



Does sid have security updates?
Not in the same sense that stable does. If the maintainer of a package fixes a security bug and uploads the package, it'll go into sid by the normal means. If the maintainer doesn't do that, then it won't. The security team only covers stable (and possibly testing... there's a pending issue for that case).
Sid users (hell, all Debian users!) are strongly urged to subscribe to the Debian security announce mailing list. And while you're at it, you should also be on the Debian devel announce list.
3.1.5 Could you tell me whether to install testing or unstable?
This is a rather subjective issue. There is no perfect answer but only a "wise guess" could be made while deciding between unstable and testing. My personal order of preference is Stable, Unstable and Testing. The issue is like this:
Stable is rock solid. It does not break.
Testing breaks less often than Unstable. But when it breaks, it takes a long time for things to get rectified. Sometimes this could be days and it could be months at times.
Unstable changes a lot, and it can break at any point. However, fixes get rectified in many occasions in a couple of days and it always has the latest releases of software packaged for Debian.
But there are times when tracking testing would be beneficial as opposed to unstable. The author such situation due to the gcc transition from gcc3 to gcc4. He was trying to install the labplot package on a machine tracking unstable and it could not be installed in unstable as some of its dependencies have undergone gcc4 transition and some have not. But the package in testing was installable on a testing machine as the gcc4 transitioned packages had not "trickled down" to testing.
APT::Default-Release "testing"; apt-get install -t sid iceweasel
Users browsing this forum: No registered users and 5 guests