Is clamav-data for etch (not etch-volatile) still needed?

[Marc Haber-17]

Hi,

the clamav-data database is growing and growing. The clamav-data build
mechanism works like this:

  - download clamav-data (on plain etch) (3 mins)
  - test clamav-data databases (on plain etch) (13 mins)
  - build package (1 min)
  - test package on plain etch (13 mins)
  - test package on etch+volatile (1 min)
  - test package on lenny (1 min)
  - test package on sid (1 min)
  - upload package to volatile (4 mins)

We see that testing the database on etch takes quite a long time,
which drives the build time over the magic 30 minutes level.

This can be verified on a different system - as soon as the clamav
from etch is in the game, things are _slooooooow_.

I am therefore pondering to drop plain etch support for clamav-data,
which would mean building them on etch+volatile and not testing the
resulting package on plain etch any more. The package is likely to
continue working on plain etch without being tested there, but testing
just takes too much time.

What do you think about that?

Greetings
Marc

--
-----------------------------------------------------------------------------
Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany  |  lose things."    Winona Ryder | Fon: *49 621 72739834
Nordisch by Nature |  How to make an American Quilt | Fax: *49 3221 2323190


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

[Stephen Gran]

This one time, at band camp, Marc Haber said:

> Hi,
>
> the clamav-data database is growing and growing. The clamav-data build
> mechanism works like this:
>
>   - download clamav-data (on plain etch) (3 mins)
>   - test clamav-data databases (on plain etch) (13 mins)
>   - build package (1 min)
>   - test package on plain etch (13 mins)
>   - test package on etch+volatile (1 min)
>   - test package on lenny (1 min)
>   - test package on sid (1 min)
>   - upload package to volatile (4 mins)
>
> We see that testing the database on etch takes quite a long time,
> which drives the build time over the magic 30 minutes level.
>
> This can be verified on a different system - as soon as the clamav
> from etch is in the game, things are _slooooooow_.
>
> I am therefore pondering to drop plain etch support for clamav-data,
> which would mean building them on etch+volatile and not testing the
> resulting package on plain etch any more. The package is likely to
> continue working on plain etch without being tested there, but testing
> just takes too much time.
>
> What do you think about that?

I would be very surprised if someone was using clamav-data from volatile
without also using clamav from volatile.
--
 -----------------------------------------------------------------
|   ,''`.                                            Stephen Gran |
|  : :' :                                        sgran@... |
|  `. `'                        Debian user, admin, and developer |
|    `-                                     http://www.debian.org |
 -----------------------------------------------------------------