[Pkg-clamav-devel] Starting preparations for 0.95rc1+dfsg-1

[Michael Tautschnig]

> This one time, at band camp, Michael Tautschnig said:
> > 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.
> > > 

The rdepends check/rebuild is still not to be forgotten ...

> > > > > - 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.
> 
> It's on my list, but I haven't had a chance to start looking yet (I'm
> out of town for now, so I'm moving slowly).
> 

Ok, I've just commited what I'd hope to be a starting point, but I'm still
seeking help. So what's the status:

- clamav-milter.config.in is prepared, but any kind of review is appreciated.
  I'd hope that this one at least is complete, but we might actually even want
  to drop some of the configuration options (to enforce some sane Debian defaults).
- clamav-milter.templates requires a thorough review. Thus far I've only copied
  the information from upstream's commented config file. It requires a review of
  the wording and the default values and of course must be updated if
  clamav-milter.config.in is updated.
- Coordination with translators: I have never done that before, but once our
  internal review of the above file is done, we need to get updated
  translations.
- clamav-milter.postinst.in lacks all the code to get from debconf data to real
  config files + ucf, etc.
- Previously we had /etc/default/clamav-milter; I haven't even checked where
  that is managed, but we definitely need to change some stuff over there. We
  should also think about migration paths.
- Lots of logic of clamav-base should probably be moved over to clamav-daemon.

Well, and probably some more work that I don't even know about yet. I'm actively
seeking help on all of those issues because of a lack of time on my side, but
also in terms of native speakers to provide as-good-as-possible query templates.

Best,
Michael

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-clamav-devel/attachments/20090323/dbc293d0/attachment.pgp