On Sun, Apr 07, 2002 at 11:25:54PM +0200, Christophe Courtois wrote:
Anyhow, woody will be released Real Soon Now(tm), and then the
security policy will be the same as it was for potato.
Does it mean too that I must update from potato rather quickly after
Woody's release if I want all
Anyhow, woody will be released Real Soon Now(tm), and then the
security policy will be the same as it was for potato.
Does it mean too that I must update from potato rather quickly after
Woody's release if I want all security releases ? Is the maintenance of
potato totally stopped after 1st
On Fri, Apr 05, 2002 at 09:40:41AM +0200, Hanspeter Roth wrote:
On Apr 04 at 18:08, John Hasler spoke:
Andrew writes:
Don't security updates also go to unstable?
No. Security updates are almost always done by backporting the fix to the
version of the package that is in stable.
On Apr 04 at 18:08, John Hasler spoke:
Andrew writes:
Don't security updates also go to unstable?
No. Security updates are almost always done by backporting the fix to the
version of the package that is in stable. The version in unstable is
almost always a more recent one. If it is
Can one switch back to stable without reinstalling the whole?
Probably not. But you don't want to, woody will be soon!
Just keep saying it, woody will be soon...
woody will be soon...
eventually, we'll convince ourselves that it is true ;-)
Seriously --- we now have under 100 RC bugs in
On Apr 05 at 04:31, Anthony DeRobertis spoke:
Just change the 'testing' to 'woody' in your sources, then you
will stay with woody. Which will be stable soon. But after that
happens, change it back to stable
[ And, btw, getting security fixes into testing is now very important,
begin quoting what Anthony DeRobertis said on Fri, Apr 05, 2002 at 04:31:35AM
-0500:
Just change the 'testing' to 'woody' in your sources, then you
will stay with woody. Which will be stable soon. But after that
happens, change it back to stable
Just to head off the next question:
as
Hanspeter Roth writes:
But what about the testing distribution? Does it also get `implicit'
security fixes by new versions?
Or is it safer to stick with stable?
Well, it follows the usual rules, so eventually things will filter
down. In the meantime, I believe you have to grab things from
On Fri, Apr 05, 2002 at 07:28:54AM -0800, Andrew Agno wrote:
Hanspeter Roth writes:
But what about the testing distribution? Does it also get `implicit'
security fixes by new versions?
Or is it safer to stick with stable?
Well, it follows the usual rules, so eventually things will
Can one get security updates for the testing distribution?
I have
deb http://security.debian.org stable/updates main contrib non-free
deb http://http.us.debian.org/debian testing main contrib non-free
in sources.list.
Or sould it be
deb http://security.debian.org testing/updates main
On Thu, Apr 04, 2002 at 10:53:52PM +0200, Hanspeter Roth wrote:
Can one get security updates for the testing distribution?
No. There is no such thing.
--
Note that I use Debian version 3.0
Linux emac140 2.4.17 #1 sön feb 10 20:21:22 CET 2002 i686 unknown
Hans Ekbrand
pgp0sfSbtZ3Nj.pgp
On Apr 04 at 22:57, Hans Ekbrand spoke:
On Thu, Apr 04, 2002 at 10:53:52PM +0200, Hanspeter Roth wrote:
Can one get security updates for the testing distribution?
No. There is no such thing.
Can one switch back to stable without reinstalling the whole?
-Hanspeter
--
To UNSUBSCRIBE,
* Hanspeter Roth ([EMAIL PROTECTED]) spake thusly:
On Apr 04 at 22:57, Hans Ekbrand spoke:
On Thu, Apr 04, 2002 at 10:53:52PM +0200, Hanspeter Roth wrote:
Can one get security updates for the testing distribution?
No. There is no such thing.
Can one switch back to stable without
Andrew writes:
Don't security updates also go to unstable?
No. Security updates are almost always done by backporting the fix to the
version of the package that is in stable. The version in unstable is
almost always a more recent one. If it is vulnerable it will be fixed when
the maintainer
John Hasler writes:
Andrew writes:
Don't security updates also go to unstable?
No. Security updates are almost always done by backporting the fix to the
version of the package that is in stable. The version in unstable is
almost always a more recent one. If it is vulnerable it will
15 matches
Mail list logo
