[Pkg-Cyrus-imapd-Debian-devel] Hosting again

[Henrique de Moraes Holschuh]

On Sun, Jun 19, 2005 at 08:04:27AM +0200, Sven Mueller wrote:
> Just wanted to let you all know that my servers are now located at their
>  intended final location which also means that from now on (given
> nothing totally unexpected happens), the repository is hosted on a
> high-volume (allowing me about 10G/day of traffic without any additional
> fee) redundant (3 uplinks) link on a hot-standby High Availability system.
> 
> So all that is needed now is someone else (or some other people) to step
> forward and actually work on cyrus22-imapd packages. I know I should

Ok. I will be getting my laptop (finally!) at debconf5 in one week or
so, and I will get to work on cyrus 2.2 then.  I promisse to somehow get
one upload done during debconf5.  After the first big cleanup, it is my
experience that futher work on Cyrus becomes far easier and faster, so
the other uploads won't be this difficult. Heck, we can even have an
automated weekly one to experimental if there is a need.

Drop me an email with everything you got on your TODO list, I will do a
general cleanup, and upload directly to unstable.  If there's a need, we
simply block the move to etch with a RC bug.

> 1) modify the package to make further use of dpatch, creating a final
>    package version with a .diff.gz which only touches debian/*

Indeed. Will do.

> 3) check wether all files are installed at the right location and with
>    correct permissions

Will also do it.

> 4) Rework update documentation to be easier to understand and more
>    clearly laid out

Err, that I won't promise I will do right now :)

> 5) Check differences between pristine upstream source tarball and my
>    debianized/cleaned up "upstream" tarball. Check which modifications
>    should be done to any upstream tarball ("none" should be the goal)
>    and which should better be integrated into the debian build process
>    instead (like move config.guess aside before built and back in place
>    during "debian/rules clean".

Will do.  I will switch back to the symlink method or a variant for
this, there is no reason to carry around the build process the crap
upstream uses, and no, it won't leak to the diff :)

> 6) Check my editsieve script (which uses sieveshell to fetch a user's
>    sieve script, edit it, check for correct syntax and upload if it
>    changed and is syntactically OK) and make it suitable for
>    distribution as a sample/tool script and addon.

Seems nice, will play with it later.

> 7) Rewrite the add-cyrus-user script from scratch (as the version I
>    added to SVN has no clear license and is therefor considered
>    non-free)

Urk. I have one here, I will have to check.  This needs to be done in
perl, which I am not that well versed in right now.

We also need to get SASL2 in shape, as Cyrus is it main user, and the
maintainer *is* MIA for all intened purposes. I can take SASL over at
any time, but there is no point in doing so unless I am going to have
the time to work in it, is there? :)

I hope to get permission to work in Cyrus 2.2 during work hours again
next month, pending a deal of an extra several thousand users at my work
place which would really benefit from newer cyrus.