[FFe] General FF exception for clamav-data for hardy

[Michael Bienia]

Binary package hint: clamav-data

clamav-data contains the data files with signatures for clamav. If we ship this package in hardy (we did it in the older releases) then it should be IMHO as recent as possible.

This package contains only two data files below /var/lib/clamav-data and a cron.daily file to check if the data files are to old. The package gets regularly uploaded to etch-volatile and once a month also to unstable.

Currently hardy is in sync with unstable. But how to proceed after FF?
Some proposals:
1) Grant a FF exception to sync clamav-data till hardy release.
2) Ask for a FF exception for every sync.
3) Remove the package from hardy as the package gets outdated quickly after release anyways and is of no much use and people should use clamav-freshclam instead to get data files.

[StefanPotyra (sistpoty)]

Hi,

Am Mittwoch, 13. Februar 2008 12:51 schrieb Michael Bienia:
>
> Currently hardy is in sync with unstable. But how to proceed after FF?
> Some proposals:
> 1) Grant a FF exception to sync clamav-data till hardy release.
> 2) Ask for a FF exception for every sync.
> 3) Remove the package from hardy as the package gets outdated quickly after
> release anyways and is of no much use and people should use
> clamav-freshclam instead to get data files.

hm... I'm in favour of 1), together with regular SRU's. 3) would also make
some sense for me. Other opinions?

Cheers,
      Stefan.

[Cesare Tirabassi (norsetto)]

Whats the point of 1) if we stop anyhow updating the package once hardy is released?
IMHO it would make more sense to go for 1) if we keep doing it after release too.
If the purpose is to release hardy with the latest possible clamav-data package, than why not just a single exception for the latest possible package?

[Michael Bienia (geser)]

One can of course only sync once short before final freeze. But I don't know when the next package get uploaded and given that currently the package gets uploaded once monthly, I only expect 2 or 3 syncs till then. Filing requests for an FF exception every time isn't much work, as the bug looks always the same (see bug 136436 or bug 150679).

I didn't check yet if the package matches the SRU requirements and if an update once a month is really helpful to the clamav users.

[Scott Kitterman (kitterman)]

We've done a blanket exception for this in the past and I think it was just fine. We should do it again here too. Actually I think post-release updates would be more suited to backports, but we should still release with the latest we can.

[Scott Kitterman (kitterman)]

Marking approved based on upchecks from sistpoty and myself.

[Sarah Kowalik (hobbsee-deactivatedaccount)]

blanket exception would be fine by me, too.