[Pkg-Cyrus-imapd-Debian-devel] Upload to debian/experimental?

[Sven Mueller]

Henrique de Moraes Holschuh wrote on 28/04/2005 22:26:
> On Thu, 28 Apr 2005, Sven Mueller wrote:
> 
>>Since the package is now pretty well tested, at least as far as I'm
>>concerned, I would like to reach a wider audience and get the package(s)
>>into experimental.
> 
> Go ahead!

Would love to do so, but I'm not yet accepted as a DD, so as far as I
can tell, I can't. Right?

>>to the libcyrus-imap-perl22 package. Actually, I've already done so and
>>websieve still works perfectly fine. I also checked the API of both perl
>>bindings, and the cyrus22 version seems 100% backward compatible.
> 
> 
> If the API is 100% compatible (and I believe perl has no such a thing as an
> ABI problem in this matter. Is that correct?) then yes, we might as well
> provide the old API with a provides: header.

Well, in theory, Perl _could_ have ABI problems, but in practice, this
could only happen if the binary perl module and its non-binary interface
module get out of sync (and I have never heard of that happening since
they are built at the same time). websieve is the only program (outside
the cyrus22-imapd source) which uses libcyrus-imap-perl21. It works
perfectly well with libcyrus-imap-perl22. I was also unable to find any
change in behaviour of the existing functions from cyrus21 to cyrus22,
no function was dropped either. So as far as I can tell,
libcyrus-imap-perl22 is indeed 100% compatible with any script written
for libcyrus-imap-perl21.

>>We could also supply dummy packages for the cyrus21 series which pull a
>>cyrus21 installation up into a cyrus22 installation. I did so on my test
> 
> No.  Cyrus21 will remain in sarge and sid for a while...

Fine, I already though so, but I wanted to try wether it would work
nonetheless, and it did.

What do you think: Should we provide an automatic update of all relevant
database files? It should be easy to do. So if anyone uninstalls cyrus21
packages and installs their cyrus22 counterpart, he shouldn't need to do
anything except if he uses/used virtual domains before. But as we know,
he would be out of luck then anyway.

>>PS: For my taste, the cyrus22 packages already seem stable enough to
>>even go into sarge, but since Henrique already expressed that he doesn't
>>want them to go into sarge, I guess I can't get my wish here ;-)
> 
> Please, let's leave it out of official sarge, there are some... issues
> upstream that, when fixed, will cause us to *really* want to get everyone to
> use such packages.  So, I'd rather we fully support sarge users thorugh an
> outside apt repository and mailinglist in alioth...
> 
> Examples of such issues: murder mupdate troubles, 8192-char linewrapping
> bug, some suspicious segfaults here and there.

Yeah, I know. Oh well, it would be so cool to get cyrus22 shipped with
sarge, but on the other hand, you are of course right that it just isn't
worth the pain (from which we would suffer later).

cu,
sven