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

[Sven Mueller]

Michael Liebl wrote on 29/04/2005 19:41:

> Hello Sven Mueller,
>
> on 29.04.2005 13:15 you wrote:
>
>>Ooops, right. I just committed a change which includes the necessary
>>masssievec (well, you could to what massievec does manually) in
>>cyrus22-common and included a small piece of information about that
>>in UPGRADE.Debian. However, any additional (or better) documentation
>>of the upgrade process is really welcomed.
>
>>>UPGRADE.Debian.gz but there is no word of bytecode. Simply a note
>>>to run /usr/lib/cyrus/upgrade which did not worked for me. None of
>>>my scripts were updated. I think the script did not dive into the
>>>subdirs [a-z]*.
>
>>Well, I think the existing upgrade scripts simply don't compile
>>sieve scripts. Don't have much time to check that though, any
>>assistance highly appreciated there.
>
> Oops. I had mistaken here something. I ran
> /usr/lib/cyrus/upgrade/upgradesieve one month ago. Not the
> /usr/lib/cyrus/upgrade/masssievec. Maybe it wasn't there?
> (2.2.12-0.2)

I think it wasn't actually, I'm not even sure it is there with 0.4, I
only added it to debian/rules for 0.5 (not yet tagged).

> Just tested from the Trunk, updating for all sieve-scripts into
> bytecode incl. deleting the old symlinks works nicely.

Good.

> Should this done automagically?

Don't think so.

> The script won't run if sieve-scripts
> are in the users home.

You mean if you use Unix-Users as Cyrus-Users and let timsieved look for
the scripts in the users' home directories? Not a very common setup AFAICT.

> The command should be (not as root, as user cyrus)
> "/usr/lib/cyrus/upgrade/masssievec /usr/lib/cyrus/bin/sievec
> /etc/imapd.conf" for Debian. Maybe you include this into
> UPGRADE.Debian.gz.

Added it to UPGRADE.Debian. Thanks for testing it.

> Also the new UPGRADE.Debian.gz now is articulate.   :-)

I take that as a compliment   ;-)

cu,
sven