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

Stephen Gran sgran at debian.org
Fri Mar 13 14:36:55 UTC 2009


This one time, at band camp, Michael Tautschnig said:
> Hi again,
> 
> > I'm just pushing the initial merge of upstream's 0.95rc1 tag to our git
> > repository. I guess you'll see the commit mails flood your mailbox soon. All
> > I've done so far is merging the upstream changes into debian/unstable, added the
> > approprate branches, the changes from the tarball and the pristine-tar. I've
> > also added a dummy debian/changelog entry, but that still has to be filled. I
> > have not made any attempt to compile and build the package or the like.
> > 
> > I'll most likely also be too busy with real life to do anything of that sort
> > during the next week, so any help is greatly appreciated. I think there are
> > quite a few bugs to be closed by upstream's changes, and maybe we can also close
> > some Debian-specific ones.
> > 
> 
> As you might have noticed I started doing some house keeping. I think I can get
> most of the stuff done, but a few issues remain where I'd need a helping hand:
> 
> - The versioning: Is +dfsg-<Debian version> a suffix that is acceptable to
>   everyone? I think (and I hope not to have missed something in my tests using
>   dpkg --compare-versions) that this should fix our problem of getting some odd
>   version numbering once 0.95.x is released.

I think it's fine, but I've messed it up before :)

> - 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.

> - 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.

One last thing (easthetic only): when you mention bugs in the BTS closed
with new usptream release, can you have a short bullet list like:

  - New upstream release (closes: #1234) # this bug only asked for upload
    Fixes: 
      rm -rf / (closes: #2345)
      allows root execution of arbitrary code (closes: #3456)
      written in php (closes: #4567)

Or whatever format makes you happy?  It just makes it easier for me to
mentally map what issues are now on the 'dealt with' list.

Cheers,
-- 
 -----------------------------------------------------------------
|   ,''`.                                            Stephen Gran |
|  : :' :                                        sgran at debian.org |
|  `. `'                        Debian user, admin, and developer |
|    `-                                     http://www.debian.org |
 -----------------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-clamav-devel/attachments/20090313/96fed7ff/attachment.pgp 


More information about the Pkg-clamav-devel mailing list