[Pkg-clamav-devel] clamav backport?

[Sebastian Andrzej Siewior]

On 2019-01-22 09:14:38 [+0100], Rhonda D'Vine wrote:
> * Harald Dunkel <harald.dunkel at aixigo.de> [2019-01-22 08:51:12 CET]:
> > using Stretch clamav spams the log file with messages
> > 
> > clamav 0.101.1 builds and works fine for stretch-backports
> > without modifications (AFAICT), so I would suggest to add it
> > to the backports repository.

where did you get 0.101.1 from?

>  While it might be nice to offer that through backports, that doesn't
> fix the warning for users of stable.  Personally I think that should get
> addressed in stable directly, not through the use of backports.  This
> isn't so much about offering new features for stable users but
> addressing issues with the packages in stable, which primarily needs to
> get addressed there, if possible.
> 
>  I think stretch-updates might be the option to go here, as it's said to
> have replaced -volatile which was the pocket formerly for such updates?

earlier we (team clamav) handled it via -updates for all supported
releases. I hope that it continues the same path this time.

>  Also, not regarding to this, but in general it might be wise to Cc your
> mails to the regular maintainer of the package so that they know about
> the interest of having an update available, as they are the ones who
> best know their package.

and such let me draft you a roadmap:
- ensure all r-deps build[0] against libclamav9. c-icap-modules does
  since yesterday in unstable. We have havp, dansguardian, and
  python-clamav to deal with. And libclamunrar which is non-free but
  still.
- cuddle with the release team and ask them nicely for a transition
  slot.
- once everything is in unstable and nobody is screaming wait for it to
  migrate to testing (and still nobody is screaming).
- cuddle with the release team once again. This time for a transition in
  stable.

[0] The word 'build' is a synonym for working in this context.

>  Thanks,
> Rhonda

Sebastian