Re: End of life for Sarge

View: New views
3 Messages — Rating Filter:   Alert me  

Re: End of life for Sarge

by Sebastian-66 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hey,

Thank you for the announcement.
Will this become effective immediately ?

I've still got a server or 20~30 running Sarge (with ignoring expired
key's), which can not yet be upgraded to Etch at the moment.

Thank you,

Best regards,
Sebastian Berm


--
To UNSUBSCRIBE, email to debian-volatile-request@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...


Re: End of life for Sarge

by Stephen Gran :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

This one time, at band camp, Sebastian said:
> Hey,
>
> Thank you for the announcement.
> Will this become effective immediately ?

What this announcement means is that volatile.debian.org has stopped
supporting sarge.  Regular security support from security.debian.org
will continue as before.

Take care,
--
 -----------------------------------------------------------------
|   ,''`.                                            Stephen Gran |
|  : :' :                                        sgran@... |
|  `. `'                        Debian user, admin, and developer |
|    `-                                     http://www.debian.org |
 -----------------------------------------------------------------


signature.asc (196 bytes) Download Attachment

Re: End of life for Sarge

by Chr. v. Stuckrad :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Wed, 13 Feb 2008, Stephen Gran wrote:

> > Thank you for the announcement.
> > Will this become effective immediately ?
>
> What this announcement means is that volatile.debian.org has stopped
> supporting sarge.  Regular security support from security.debian.org
> will continue as before.

OK, but since e.g. clamav or spamassassin are 'frozen in sarge' and
after having installed newer versions via volatile to keep them
usable, the next security-fix (without volatile) means downgrading
to the last sarge-frozen package.
So after next security-problem (by the way just a day or two ago
clamav announced such a fix) you'll be simply FORCED to upgrade to
etch or loose functionality i.e the virus-scanner-engine.

Wasn't such a situation just the definition of a 'CATCH22'?
Without 'etch' you're lost for security-reasons either way,
either you'll compromise the server by keeping insecure software,
or the users by insecure working of the older software.

So the question, 'when is the exact deadline' might be VERY
interesting (it might even come to late for clamav though,
I just dropped clamav from the old sarge server and have to use
another filter -- just luck, that we have one)...

Stucki