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.
There have been some updates to Sarge from the Security Team, but what about Firefox and Thunderbird for example? Bugreports have been filed against these two addressing the recent security updates from Mozilla, but it seems to take a long time to get into Sarge.
Firefox has 1.0.6 in unstable, but also has dependencies unsuitable for Sarge (e.g. libxinerama1). Thunderbird has a 1.0.6 version for Sarge, but not in the official archive (get it here).
I've been noticing it for sometime (I'm using "testing") and there has been a definite slowdown in updating repositories with the latest packages for a few weeks now. I don't know why, but I guess some of the package maintainers are on holiday this time of the year.
The Debian project confirms that the security infrastructure for both the current release Debian GNU/Linux 3.1 (alias sarge) and the former release 3.0 (alias woody) is working again. The security team is now able to provide updates on a regular basis again.
There were several issues with the security infrastructure after the release of sarge, that lead to the Debian security team being unable to issue updates to vulnerable packages. These issues have been fully resolved, and the infrastructure is working correctly again.
The Debian project further strongly advises users to not install packages from the sarge-proposed-updates suite as has been advocated by some websites. Those packages are currently under development and may not work properly. In addition, those packages may not provide users with timely security fixes.
The security team will continue to support Debian GNU/Linux 3.0 alias woody until May 2006, or if the security support for the next release, codenamed etch, starts, whatever happens first.
why does that mean ??
Is sarge not supposed to be the current stable which means that it should be safe to upgrade to and it should get security fixes ??
The Debian project further strongly advises users to not install packages from the sarge-proposed-updates suite as has been advocated by some websites. Those packages are currently under development and may not work properly. In addition, those packages may not provide users with timely security fixes.
The security team will continue to support Debian GNU/Linux 3.0 alias woody until May 2006, or if the security support for the next release, codenamed etch, starts, whatever happens first.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.