[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#470188: new milter-greylist package



This has been sitting forgotten in my 'drafts' folder for a long while
now.  I might as well hit "send" and let you see it.  As you might
imagine, I don't have much by way of free time, but small tasks are
easy enough.  I keep meaning to look into the formalities of becoming
a Debian maintainer, but I never have the time.

Cord Beermann wrote:
> As you pointed me out that there is v4 available now, so the next
> Package-release should be also v4, so maybe some of the patches
> provided by Michael in #470188 don't apply anymore, or are not needed
> at all anymore?

Okay, I hadn't seen those patches.  Everything I did was based on the
3.0-3 source package.  Easily rectified:

I just integrated the control patch.

The milter-greylist.default patch, designed to address bugs #465260
and #460314, adds an extra bit of complication to the defaults file
that I think is better implemented in the init script, so I'll ignore
that patch.

The rules patch also overlaps things I've done.  I dislike the sed
call, preferring to adjust the init script itself.  I'll talk to
Emmanuel about pushing that into the upstream.

The watch patch dramatically changes things ... I'm content with
Michael's version.

The changelog will be interesting ... we've both independently
addressed all of the bugs, so credit should be shared.  Michael's
changelog entries mentioned altering the debian/copyright file, but I
don't see his diff for it.  My modifications there simply update the
copyright to the year 4.0 was released.

> As far as i can see, you both aren't Debian Developers (is anyone
> of you interested in becoming one?) so the way to get the updated
> package in, would be that you provide me the files for download
> somehow, and i check, sign and upload it. 
> 
> If you wish I add your name and address to the Package, so your work
> can be recognized.

I'd like that opportunity, yes (especially if it will give me an
@debian.org forwarding address).  The website is a bit questionable
about that process.

> There are some pages out there 
> 
> http://www.us.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Uploaders
> http://wiki.debian.org/CollaborativeMaintenance
> http://mentors.debian.net/
> 
> that describe how multiple Maintainers for a Package could be handled.
> Maybe this is a way to go?

Michael noted he is not interested in co-maintaining.  I am.

-Adam

Attachment: milter-greylist_4.0-1.diff.gz
Description: GNU Zip compressed data

Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: