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

[Sven Mueller]

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigB5084CBBEA59C839D89A28ED
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Henrique de Moraes Holschuh wrote on 29/06/2005 15:25:
> 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. 

Sounds cool. BTW: I will also be at DebConf5 if nothing unexpected happens.

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

Yes, could be done without any problem. Might even be desirable. Let's
see. I will definately do a backport to sarge (or help Norbert
Tretkowski do one) on a regular basis.

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

I don't expect any such thing to occure, but let's see.

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

Fine. Otherwise I would have done that immediately before or during
DebConf5.

>>3) check wether all files are installed at the right location and with
>>   correct permissions
> 
> Will also do it.

I already checked the cyrus22-admin and cyrus22-clients packages. They
are OK. The -common package contains a few things I'm not sure about:

- /usr/lib/cyrus/get-backtrace.gdb
  Do we need to include that?
- /usr/lib/cyrus/bin/quota and /usr/lib/cyrus/bin/reconstruct
  IMHO, these should be named cyrquota and cyrreconstruct like
  the binaries those links point to. However I didn't even find
  out where those links are created.

>>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 :)

Me neither :-)

>>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 :)

I would say: go ahead. And maybe explain to me how your approach works ;-)

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

Sounds familiar :-/

> 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? :)

Not really, I must (unwillingly) admit ;-)

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

That's similar to how I got the first huge bunch of work done on cyrus
2.2. We simply needed virtual domains work correctly (and this can only
really be done in Cyrus 2.2 IMNSHO). Now that Cyrus2.2 works as it
should (at least to 98% I would say), I can't do that anymore. Too bad
(really).

cu,
Sven

--------------enigB5084CBBEA59C839D89A28ED
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (Cygwin)

iD8DBQFCwrhVg3izVowCbSERAiAwAJ4mb4HzSlHcbUcdFnsIHX25wwHFuACfW3Kn
61U2gLRpTnfznwMLjT/dtdw=
=lnq3
-----END PGP SIGNATURE-----

--------------enigB5084CBBEA59C839D89A28ED--