Search Criteria
Package Details: cyrus-imapd-docs 3.8.4-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/cyrus-imapd.git (read-only, click to copy) |
---|---|
Package Base: | cyrus-imapd |
Description: | Documentation for the Cyrus IMAP server |
Upstream URL: | https://www.cyrusimap.org/ |
Licenses: | BSD-Attribution-HPND-disclaimer |
Submitter: | ryanc |
Maintainer: | J5lx |
Last Packager: | J5lx |
Votes: | 27 |
Popularity: | 0.000012 |
First Submitted: | 2007-10-14 08:22 (UTC) |
Last Updated: | 2024-08-04 01:38 (UTC) |
Dependencies (21)
- brotli (brotli-gitAUR) (make)
- clamav (make)
- icu (icu-gitAUR) (make)
- jansson (jansson-gitAUR) (make)
- krb5 (krb5-gitAUR) (make)
- libcap (make)
- libchardet (make)
- libical (make)
- libldap (make)
- libnghttp2 (libnghttp2-gitAUR) (make)
- libsasl (make)
- libxml2 (libxml2-gitAUR, libxml2-2.9AUR) (make)
- mariadb-libs (mariadb-libs-gitAUR, libmysqlclient81AUR, libmysqlclient80AUR, libmysqlclientAUR, mariadb-lts-libs) (make)
- pcre (make)
- perl (perl-gitAUR) (make)
- postgresql-libs (postgresql-libs-12AUR, postgresql13-libsAUR, postgresql-libs-gitAUR) (make)
- rsync (rsync-gitAUR, rsync-reflinkAUR, rsync-reflink-gitAUR) (make)
- shapelib (make)
- sqlite (sqlite-fossilAUR) (make)
- xapian-core (xapian-core-gitAUR) (make)
- zstd (zstd-gitAUR, zstd-staticAUR) (make)
Required by (1)
- cyrus-imapd (optional)
Sources (7)
- cyrus-imapd.service
- cyrus-imapd.sysusers.conf
- cyrus-imapd.tmpfiles.conf
- https://github.com/cyrusimap/cyrus-imapd/releases/download/cyrus-imapd-3.8.4/cyrus-imapd-3.8.4.tar.gz
- https://github.com/cyrusimap/cyrus-imapd/releases/download/cyrus-imapd-3.8.4/cyrus-imapd-3.8.4.tar.gz.sig
- https://src.fedoraproject.org/rpms/cyrus-imapd/raw/4176c0e5983b3d19752f2db3860c33bafa7c259b/f/patch-cyrus-remove-always-inline-for-buf-len
- imapd.conf.patch
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 12 Next › Last »
J5lx commented on 2020-02-15 18:32 (UTC)
Should be fixed now, I’ve submitted a patch to upstream. Thanks for reporting!
a2h commented on 2020-02-07 08:17 (UTC) (edited on 2020-02-07 08:51 (UTC) by a2h)
Hi. I was getting a cap_setuid erroR when building Cyrus.
It looks like it was flagged here: https://www.bountysource.com/issues/87238742-3-0-13-build-fails-with-libcap-2-29
I fixed it by adding this to the prepare() section after the change of directory
egrep -lRZ 'cap_setuid' . | xargs -0 -l sed -i -e 's/cap_setuid/cap_setuid_fixed/g'
J5lx commented on 2019-11-20 19:27 (UTC)
Damn, I forgot to update the checksum. I’ll fix that immediately, sorry about that!
J5lx commented on 2019-09-10 01:31 (UTC)
Small update: I finally figured out how to make the documentation build with Sphinx 2, so the dependency on Sphinx 1 is now gone and there is no longer any need for that virtualenv hack either. I’m sorry that I could’t get it done any earlier.
J5lx commented on 2019-06-21 21:50 (UTC) (edited on 2019-06-22 06:56 (UTC) by J5lx)
guygma: Thanks for the submission. It’s not my way of doing things (I’d rather do it the way it is now or come up with a patch to make it work with Sphinx 2) but I’ll pin a link to it for those who prefer your solution (I don’t want to pin the PKGBUILD itself because that’d push the upgrade note down by a lot). My primary reason for this is that with your solution, the use of pip will result in lots of downloads during the build phase, and this means that if you’re building packages in a clean environment like a chroot (as you have done yourself), those dependencies can’t be cached and will have to be re-downloaded for every package build that needs them. The way it is now, you might have to install “over 200MB” (according to zork, haven’t checked myself) of python2-sphinx dependencies in whatever your build environment is, however those only need to be downloaded once and can then be re-used for every build that needs them. Using pip, on the other hand, these dependencies will have to be re-downloaded on every build, e.g. (presumably) for the next version or (especially important for me) when implementing and testing changes to the packaging process.
Edit: While I won’t be incorporating this change, I do see that it makes the build process more tedious and I’ll give patching for version 2 another try when I find some time for it next week.
Also, on a different note, if you’re here for JMAP support, I’m afraid you’ll have to be a little more patient, since experimental JMAP support was removed in version 3.0.6 and is now planned to have its full release in a later version. Alternatively, if you can’t stand the wait, you could try an unstable version (3.1.x) or the latest code from the master branch. Right now the --enable-jmap option is simply ignored (as you’ll see in build output:
configure: WARNING: unrecognized options: --enable-jmap
).zork commented on 2019-06-21 19:16 (UTC)
guygma: Many thanks for your work! It is great that I do not have to install over 200Mb of python2-sphinx dependencies just to build cyrus. Thanks again!
guygma commented on 2019-06-21 12:59 (UTC) (edited on 2019-06-21 13:14 (UTC) by guygma)
OK, so I have updated the PKGBUILD and managed to build in a clean chroot with all of the options enabled (including xapian). I have included the PKGBUILD below in the hopes it makes it easy for the maintainer to update it if they see fit. Also, those who take care to read it may input the edits themselves on their local copy if they had trouble with the previous version as I did.
I believe I have incorporated the suggestions made by all the recent comments in this thread.
EDIT: I can also confirm that
--enable-jmap
builds properly, which is fantastic as JMAP functionality was the main reason I am moving from Dovecot to Cyrus.J5lx commented on 2019-06-17 20:22 (UTC) (edited on 2019-06-17 20:24 (UTC) by J5lx)
Yes, it should, but sometimes dependencies get overlooked. As you can see, both I and another user already noted the missing dependency in the comment section of perl-pod-pom back in march, however the maintainer still hasn’t taken action.
On another note, please make sure you have a basic understanding of how installing packages from AUR works. Since you seemingly weren’t aware of the issue with perl-pod-pom and thought it was a problem with this package, I’m suspecting you are using some AUR helper to install these packages. However, it is pretty dangerous to use those tools without an understanding of what exactly they are doing, since the packages on the AUR are created by other users and there is no guarantee they won’t do malicious things to your system. The AUR wiki article should be a good starting point for learning more. If you do know all that already, though, I guess you’ll be safe; I’m just trying to be helpful :)
Edit: Well, looks like someone was faster than me. I shouldn’t try to work on too many things at the same time I guess ^^
« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 12 Next › Last »