Lou Losee said: > The posts that arrive from the Debian Security list show package updates > for Woody. How does one ensure that these same updates are applied when > running a mixed system (testing & stable)?
As long as there aren't people working to put security updates into testing, you won't see any 'security team' updates to testing. http://www.debian.org/releases/ (read the testing section) So you have to wait for the package maintainer to fix it, release the fix into unstable (which if you've been following the lists you'll notice it hasn't happened for the ssh package as of last night but the ssh update has been in stable for a couple of days.) Then you'll need to wait for the unstable update to pass the gates of testing. Once all that's happened you'll have an updated mysql. (I'm probably missing some conditions that someone may comment on.) > > For instance: > Recently a post for mysql-common indicated an update was available. If > I run apt-cache policy mysql-common I get the following output: > > mysql-common: > Installed: 4.0.13-3 > Candidate: 4.0.13-3 > Version Table: > 4.0.14-1 0 > 500 http://ftp.de.debian.org unstable/main Packages > *** 4.0.13-3 0 > 990 http://ftp.de.debian.org testing/main Packages > 100 /var/lib/dpkg/status > 3.23.49-8.5 0 > 500 http://security.debian.org stable/updates/main Packages > 3.23.49-8 0 > 500 http://ftp.de.debian.org stable/main Packages > > So, I have the latest version installed from testing. Does that include > the changes from security.debian.org? > I don't know the answer to that, sorry. Most likely it doesn't. -- Jacob Trying out SquirrelMail -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]