Package Details: cyrus-imapd-docs 3.0.9-2

Git Clone URL: https://aur.archlinux.org/cyrus-imapd.git (read-only)
Package Base: cyrus-imapd
Description: Documentation for the Cyrus IMAP server
Upstream URL: https://www.cyrusimap.org/
Licenses: BSD
Submitter: ryanc
Maintainer: J5lx
Last Packager: J5lx
Votes: 20
Popularity: 0.650647
First Submitted: 2007-10-14 08:22
Last Updated: 2019-03-20 13:52

Pinned Comments

J5lx commented on 2019-03-16 02:24

I just updated this package to Cyrus 3.0.9 and will push that update in a moment. Since Cyrus 3.0 is a major new version to begin with, I also used the opportunity to make some major changes to this package as well, mostly in order to adhere to certain conventions or as a matter of housekeeping. In doing so I have tried to bring the package back into a good shape after that long-time lack of maintenance, but if there’s something you are unhappy with or if you have further suggestions for improvement, please let me know. Since the changes are so unusually extensive, here’s a rundown of them, how they impact the upgrade procedure (if so) and some reasoning behind them.

  • The most important bit first: Please stop Cyrus before upgrading – there are changes in both this package and Cyrus itself that could otherwise prevent a clean upgrade.
  • Please also read through the upgrade guide before performing the upgrade.
  • Before 3.0, the Cyrus documentation suggested using /var/imap and /var/spool/imap as the config directory and location for partitions, respectively. In 3.0, most materials, including the example config files, point to /var/lib/cyrus and /var/spool/cyrus instead. Therefore, I have changed the default paths in this package as well, however there is no automatic migration, so if you want to migrate to the new directories you will have to do so manually. Of course you can keep using the previous directories as well if you want.
  • Previously, the cyrus user was assigned a random non-system uid (>=1000). Now, it uses a fixed uid and gid of 70, which has been assigned to it for a long time. The id is updated automatically, however you will have to adjust the permissions of paths owned by that user manually, including the previously mentioned /var/imap and /var/spool/imap.
  • The systemd unit has been renamed from cyrus-master.service to cyrus-imapd.service, to make the name more predictable and consistent with other services. cyrus-imapd.service is also the name used by every other distribution I could find, and is even referred to in Cyrus’s own documentation. However this change means that you will have to re-enable the service if it was enabled before.

Additionally, the following changes have also been made, but usually these should not impact the upgrade procedure:

  • The /etc/conf.d/cyrus-master configuration file has been removed. It wasn’t even being used before, and I believe most people won’t need to adjust the command-line parameters anyway. If you still need to do so, you can create a drop-in file for the systemd unit.
  • I’ve completely overhauled the build configuration. In the process, I’ve decided to enable a number of features which weren’t enabled by default. This means that the package has now more dependencies than before, however many of them are likely to be installed on a (mail) server anyway – for example, sqlite, postgresql-libs and mariadb-libs are also needed for postfix and opendkim, among others, while libnghttp2, krb5 and libldap are directly or indirectly required by the ubiquitous curl package. I tried to make a sensible selection, but I’m open to suggestions. I decided against splitting individual components out, but I’m also open to discussing this decision as well.
  • Speaking of split packages, there is now one containing the Cyrus documentation, which was completely overhauled in 3.0.
  • The package no longer conflicts with imap-server and pop3-server. I believe all files which could warrant such a conflict (particularly imapd and pop3d) currently reside in Cyrus’s own libexec directory, but let me know if I overlooked something.
  • !makeflags has been removed from options. I tried building with multiple simultaneous jobs and couldn’t find any problems. Again, let me know if I was mistaken.
  • The install file has been rewritten from scratch. User creation is now handled by systemd-sysusers. The state directories are no longer initialised automatically – this should now be done manually by running mkimap as cyrus:mail (invoke it as sudo -u cyrus -g mail mkimap /etc/cyrus/imapd.conf, for example – requires appropriate sudo configuration). They are also no longer set to update synchronously on ext[234] file systems, since this was only ever meant for systems using ext2 which is so ancient that I’m not going to explicitly support it. The configuration files are no longer chowned to cyrus and made read-only to everyone else, as is normally the case for such configuration files.
  • Perl files are now installed into vendor_perl rather than site_perl, as per Perl package guidelines.

Latest Comments

1 2 3 4 5 6 ... Next › Last »

TheGoliath commented on 2019-03-29 11:46

==> Starting build()... Can't locate inc/Module/Install.pm in @INC (you may need to install the inc::Module::Install module) (@INC contains: /usr/lib/perl5/5.28/site_perl /usr/share/perl5/site_perl /usr/lib/perl5/5.28/vendor_perl /usr/share/perl5/vendor_perl /usr/lib/perl5/5.28/core_perl /usr/share/perl5/core_perl) at Makefile.PL line 2. BEGIN failed--compilation aborted at Makefile.PL line 2. ==> ERROR: A failure occurred in build(). Aborting...

This even occurs while having perl-inc-latest installed

EDIT.: Add perl-module-install as dependency (https://www.archlinux.org/packages/community/any/perl-module-install/)

EDIT. #2: Can't load '/usr/lib/perl5/5.28/vendor_perl/auto/Cyrus/IMAP/IMAP.so' for module Cyrus::IMAP: /usr/lib/perl5/5.28/vendor_perl/auto/Cyrus/IMAP/IMAP.so: undefined symbol: cap_set_proc at /usr/lib/perl5/5.28/core_perl/DynaLoader.pm line 193. at /usr/lib/perl5/5.28/vendor_perl/Cyrus/IMAP/Admin.pm line 43. Compilation failed in require at /usr/lib/perl5/5.28/vendor_perl/Cyrus/IMAP/Admin.pm line 43. BEGIN failed--compilation aborted at /usr/lib/perl5/5.28/vendor_perl/Cyrus/IMAP/Admin.pm line 43. Compilation failed in require at /usr/lib/perl5/5.28/vendor_perl/Cyrus/IMAP/Shell.pm line 59. BEGIN failed--compilation aborted at /usr/lib/perl5/5.28/vendor_perl/Cyrus/IMAP/Shell.pm line 59. Compilation failed in require at /usr/bin/vendor_perl/cyradm line 65. BEGIN failed--compilation aborted at /usr/bin/vendor_perl/cyradm line 65.

When executing cyradm

J5lx commented on 2019-03-16 02:24

I just updated this package to Cyrus 3.0.9 and will push that update in a moment. Since Cyrus 3.0 is a major new version to begin with, I also used the opportunity to make some major changes to this package as well, mostly in order to adhere to certain conventions or as a matter of housekeeping. In doing so I have tried to bring the package back into a good shape after that long-time lack of maintenance, but if there’s something you are unhappy with or if you have further suggestions for improvement, please let me know. Since the changes are so unusually extensive, here’s a rundown of them, how they impact the upgrade procedure (if so) and some reasoning behind them.

  • The most important bit first: Please stop Cyrus before upgrading – there are changes in both this package and Cyrus itself that could otherwise prevent a clean upgrade.
  • Please also read through the upgrade guide before performing the upgrade.
  • Before 3.0, the Cyrus documentation suggested using /var/imap and /var/spool/imap as the config directory and location for partitions, respectively. In 3.0, most materials, including the example config files, point to /var/lib/cyrus and /var/spool/cyrus instead. Therefore, I have changed the default paths in this package as well, however there is no automatic migration, so if you want to migrate to the new directories you will have to do so manually. Of course you can keep using the previous directories as well if you want.
  • Previously, the cyrus user was assigned a random non-system uid (>=1000). Now, it uses a fixed uid and gid of 70, which has been assigned to it for a long time. The id is updated automatically, however you will have to adjust the permissions of paths owned by that user manually, including the previously mentioned /var/imap and /var/spool/imap.
  • The systemd unit has been renamed from cyrus-master.service to cyrus-imapd.service, to make the name more predictable and consistent with other services. cyrus-imapd.service is also the name used by every other distribution I could find, and is even referred to in Cyrus’s own documentation. However this change means that you will have to re-enable the service if it was enabled before.

Additionally, the following changes have also been made, but usually these should not impact the upgrade procedure:

  • The /etc/conf.d/cyrus-master configuration file has been removed. It wasn’t even being used before, and I believe most people won’t need to adjust the command-line parameters anyway. If you still need to do so, you can create a drop-in file for the systemd unit.
  • I’ve completely overhauled the build configuration. In the process, I’ve decided to enable a number of features which weren’t enabled by default. This means that the package has now more dependencies than before, however many of them are likely to be installed on a (mail) server anyway – for example, sqlite, postgresql-libs and mariadb-libs are also needed for postfix and opendkim, among others, while libnghttp2, krb5 and libldap are directly or indirectly required by the ubiquitous curl package. I tried to make a sensible selection, but I’m open to suggestions. I decided against splitting individual components out, but I’m also open to discussing this decision as well.
  • Speaking of split packages, there is now one containing the Cyrus documentation, which was completely overhauled in 3.0.
  • The package no longer conflicts with imap-server and pop3-server. I believe all files which could warrant such a conflict (particularly imapd and pop3d) currently reside in Cyrus’s own libexec directory, but let me know if I overlooked something.
  • !makeflags has been removed from options. I tried building with multiple simultaneous jobs and couldn’t find any problems. Again, let me know if I was mistaken.
  • The install file has been rewritten from scratch. User creation is now handled by systemd-sysusers. The state directories are no longer initialised automatically – this should now be done manually by running mkimap as cyrus:mail (invoke it as sudo -u cyrus -g mail mkimap /etc/cyrus/imapd.conf, for example – requires appropriate sudo configuration). They are also no longer set to update synchronously on ext[234] file systems, since this was only ever meant for systems using ext2 which is so ancient that I’m not going to explicitly support it. The configuration files are no longer chowned to cyrus and made read-only to everyone else, as is normally the case for such configuration files.
  • Perl files are now installed into vendor_perl rather than site_perl, as per Perl package guidelines.

jcelerier commented on 2019-01-02 11:38

hi, here (and also according to https://downforeveryoneorjustme.com/cyrusimap.org) the website is down. Anyone else has a mirror ?

cptr13 commented on 2018-12-16 21:50

FTp address needs to be edited, OLD-VERSIONS/ needs to be added to the ftp URL

pgoetz commented on 2018-10-27 13:32

@TheGoliath

Hi -

Sure, you can take it. At first I was waiting for the 3.x series to stabilize, but lately I just haven't had time, and I agree that it desperately needs to get done. The only reason I took it over was the last package maintainer dropped the ball on keeping it Arch compatible (just like I have <:( ).

How do I hand it over to you? Just disown and let you grab it?

TheGoliath commented on 2018-10-27 12:36

@pgoetz @CarstenF I'd like to maintain this package (it is out of date for quite a while) and needs the new release series imho.

cheers

bluntroller commented on 2018-09-30 00:08

@pgoetz: Just drop it - it doesn't compile at all.

pgoetz commented on 2017-09-23 16:44

Yep. I've been monitoring the 3.x releases closely via the cyrus-devel and info-cyrus lists, and all the releases so far have been a bit too unstable for my tastes; especially given that I would likely be testing the release on my production IMAP server. 3.0.4 is probably ready for prime time, though. Need to get on the ASAP or turn the package maintenance over to someone else.

aspeer commented on 2017-09-23 13:30

This should be updated to the latest stable version 3.0.4. Here is a patch : https://pastebin.com/6X7XaWUw (edit: it breaks the systemd service though, may need a bit more work to put everything where it should be)

pgoetz commented on 2017-05-26 22:08

Hi Markus -

It sounds like you've tested this, so I can certainly make this change. When I checked with the cyrus mailing list about this issue the answer I got was that cyrus 2.5.x is incompatible with openssl 1.1, and I didn't pursue it further, since installing the compatibility openssl 1.0 package solves the problem without violating the Arch rule of not modifying upstream if at all avoidable.

Question: Are you (100% - epsilon) certain there are no other compatibility problems, and if so, where does this certainty come from? Seems more prudent to just get 3.0.1 packaged as soon as possible.