2.3.16 code drop action?

Sven Mueller sven at incase.de
Tue May 4 10:21:15 UTC 2010


Henrique de Moraes Holschuh schrieb:
> On Wed, 20 Jan 2010, Henrique de Moraes Holschuh wrote:
>> Well, it is not a the state I'd like, but its best I at least commit
>> something instead of taking more time.  The changelog needs more love, and I
>> want to clean up more stuff before I even consider putting it forward as a
>> candidate for an experimental or unstable upload.
> 
> I had the opportunity and drive to clean it up further.  debian/rules is
> a lot more sleek now, and I switched from dpatch to quilt for a number
> of reasons.  The two main ones are: quilt is less prone to leaking cruft
> or misapplying patches, and dpkg-source format 3.0.
> 
> Please comment on the packaging changes.  There is also a README.source
> to help...

I only had a glance at your changes, but they look good to me.

>> I have gone over all the debian patches, and cleaned them up for 2.3.16.  I
>> will go over them again, many of those need a bit more care, and the ones
>> which will be thruly useless when I am done with, need to be removed.
> 
> This still needs to be done.

So true, I'm sorry I don't currently have any time to spare for working
on cyrus-imapd packaging.

>> The tree I am using is based on upstream tarball releases.  I will keep an
>> eye on the incremental work being done on the other cyrus 2.3 working
>> branch (no, it is not entirely up-to-date yet).
> 
> Merging all improvements from the other branches is next, so that I can
> use this thing at work :-)

Yeah, needing to use the stuff at work is certainly is a large
incentive. Unfortunately, I can't currently use cyrus-imapd at work, so
I also can't spend time at work on cyrus-imapd.

Regards,
Sven



More information about the Pkg-Cyrus-imapd-Debian-devel mailing list