Author: geissert
Date: 2011-02-14 02:39:45 +0000 (Mon, 14 Feb 2011)
New Revision: 16141
Modified:
Makefile
Log:
fix volatile target
OTOH: why do we have it at all?
Modified: Makefile
==================================================================--- Makefile
2011-02-14 02:19:07 UTC (rev 16140)
+++ Makefile 2011-02-14 02:39:45 UTC (rev 16141)
@@ -155,7 +155,7 @@
VOLATILE_MIRROR = http://volatile.debian.org/debian-volatile/dists
update-volatile:
- set -e && for archive in $(STABLE) ; do \
+ set -e && for archive in lenny ; do \
for arch in $(LENNY_ARCHS) ; do \
$(PYTHON) bin/apt-update-file \
$(VOLATILE_MIRROR)/$${archive}/volatile/main/binary-$$arch/Packages \
On Mon, 14 Feb 2011 02:39:46 +0000 Raphael Geissert wrote:> Author: geissert > Date: 2011-02-14 02:39:45 +0000 (Mon, 14 Feb 2011) > New Revision: 16141 > > Modified: > Makefile > Log: > fix volatile target > OTOH: why do we have it at all?Since the only thing volatile ever really had were clamav definition and timezone data updates, which don''t have security issues, there really is no reason. I''d say just get rid of it. Mike
On Sun, Feb 13, 2011 at 09:48:26PM -0500, Michael Gilbert wrote:> On Mon, 14 Feb 2011 02:39:46 +0000 Raphael Geissert wrote: > > > Author: geissert > > Date: 2011-02-14 02:39:45 +0000 (Mon, 14 Feb 2011) > > New Revision: 16141 > > > > Modified: > > Makefile > > Log: > > fix volatile target > > OTOH: why do we have it at all? > > Since the only thing volatile ever really had were clamav definition and > timezone data updates, which don''t have security issues, there really > is no reason. I''d say just get rid of it.No, the actual clamav engine is still provided through lenny-volatile. Cheers, Moritz