Package Base Details: cyrus-imapd

Git Clone URL: https://aur.archlinux.org/cyrus-imapd.git (read-only, click to copy)
Submitter: ryanc
Maintainer: J5lx
Last Packager: J5lx
Votes: 27
Popularity: 0.001267
First Submitted: 2007-10-14 08:22 (UTC)
Last Updated: 2024-03-24 14:57 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 Next › Last »

cptr13 commented on 2018-12-16 21:50 (UTC)

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

pgoetz commented on 2018-10-27 13:32 (UTC)

@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?

bluntroller commented on 2018-09-30 00:08 (UTC)

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

pgoetz commented on 2017-09-23 16:44 (UTC)

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 (UTC) (edited on 2017-09-26 16:13 (UTC) by aspeer)

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 (UTC)

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.

markuschaaf commented on 2017-05-26 21:38 (UTC)

I don't see why I have to ask this, but would you be so very kind to just modify PKGBUILD? There is AFAIK no incompatibility between openssl-1.1 and cyrus-imap-2.5. Openssl now happens to include <sched.h> (a posix system header), which creates a name clash with an unlucky chosen identifier in some cyrus files. Renaming that identifier (that has no external visibility) solves the problem without collateral damage. How is installing an older version of openssl better advise? If the upstream maintainers eventually fix this, the sed command will do nothing.

pgoetz commented on 2017-05-26 13:35 (UTC) (edited on 2017-05-26 13:37 (UTC) by pgoetz)

Hi - Sorry, I just took over maintenance of this package, but haven't had time to build a new version yet -- will try and so that in the next couple of days. Meanwhile, here is the very simple fix for this issue for the time being. After upgrading your system and before rebooting (if you run a firewall, you generally must reboot every time the kernel is upgraded or weird things will start to happen), install this package: # pacman -S openssl-1.0 Your cyrus install will continue to work with no interruptions or further intervention. I've tested this on 2 different mail servers. If you've already rebooted and your cyrus install is now broken, no worries. Just install the openssl-1.0 package and restart cyrus-master. Everything should be in order again.