RE: testing vs stable (was Re: broadcom drivers debian (was RE: Debian Installer - Problems Partitioning))
There you go again (nod to the late Ronnie, not that I would have voted
As promised, after my success with the DL140, I popped a sarge CD into
my beloved old Alpha 4100s and the previously dormant StorageWorks 800
array lit up like a Christmas tree for the first time for over a year.
It will be a couple of days before I can spend some more time on it, but
I was jubilant. Until you guys started bickering, hinting that it's
"not secure" or something. You guys need a good PR agent. Just
kidding. Or am I?
Next I will put the dreaded DAC960s back and see if they work on sarge.
More news soon.
From: Steve Langasek [mailto:email@example.com]
Sent: Monday, June 07, 2004 9:51 PM
Subject: Re: testing vs stable (was Re: broadcom drivers debian (was RE:
Debian Installer - Problems Partitioning))
On Mon, Jun 07, 2004 at 08:37:46PM -0400, Dan M. MacNeil wrote:
> Q: How is security handled for testing and unstable?
> A: The short answer is: it's not. Testing and unstable are rapidly
> targets and the security team does not have the resources needed to
> properly support those. If you want to have a secure (and stable)
> you are strongly encouraged to stay with stable. However, the security
> secretaries will try to fix problems in testing and unstable after
> are fixed in the stable release.
> It is my subjective experience that the security team is actually
> good about updating testing. For example the postgresql update
> both testing & stable.
This would be very subjective indeed, because the security team does
nothing to directly address security holes in testing. The most they do
is to document whether the bug affects testing.
Please note that this e-mail and any files transmitted with it may be
privileged, confidential, and protected from disclosure under
applicable law. If the reader of this message is not the intended
recipient, or an employee or agent responsible for delivering this
message to the intended recipient, you are hereby notified that any
reading, dissemination, distribution, copying, or other use of this
communication or any of its attachments is strictly prohibited. If
you have received this communication in error, please notify the
sender immediately by replying to this message and deleting this
message, any attachments, and all copies and backups from your