Hi everyone,

> [...]
> > 
> > > - Which distributions are we going to upload to? unstable? volatile?
> > >   stable-security? There is a recent thread on {-security,-volatile} 
> > > about that
> > >   [1], but I don't think that any conclusion has been reached. I think 
> > > I'll also
> > >   post to that one to get some more input.
> > 
> > I think if we're planning an upload of an rc candidate, experimental is
> > probably the most suitable place for it.
> > 
> 
> Oh, there's one more reason to do so: We'll need to check all the rdepends,
> libclamav has seen a SONAME bump and several interfaces have changed.
> 
> > > - clamav-milter has been rewritten from scratch and our scripts and 
> > > example
> > >   configs might need some loving care. Quite a bit of information is 
> > > provided at
> > >   [2], but I've never used clamav-milter myself and I'm not sure whether 
> > > we need
> > >   to change anything in our packaging or not.
> > 
> > We're going to need to do quite a bit of shuffling around.  It used to
> > be that clamav-milter read clamd.conf, so the file had to be in -base.
> > Now that it will read it's own file, it will need to ship with the
> > milter.  This means nothing else needs clamd.conf besides clamd, so the
> > file should be moved over to the -daemon package.  I'll take a look this
> > weekend and see what can be done.
> > 
> 

Just to make sure I don't duplicate any ongoing work: Did anybody already start
working on this? Otherwise I'd at least start the preparations of the Debconf
stuff.

Thanks,
Michael

Attachment: pgpNpzKZY1dJl.pgp
Description: PGP signature

_______________________________________________
Pkg-clamav-devel mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/pkg-clamav-devel

Reply via email to