AUR (en)

Search Criteria

Package Details: mu 1.14.1-2

Git Clone URL:	https://aur.archlinux.org/mu.git (read-only, click to copy)
Package Base:	mu
Description:	Maildir indexer/searcher and Emacs client (mu4e)
Upstream URL:	http://www.djcbsoftware.nl/code/mu
Licenses:	GPL-3.0-or-later
Submitter:	xyproto
Maintainer:	mroethke
Last Packager:	mroethke
Votes:	47
Popularity:	0.47
First Submitted:	2019-03-27 09:21 (UTC)
Last Updated:	2026-05-02 18:36 (UTC)

Git Clone URL:

https://aur.archlinux.org/mu.git (read-only, click to copy)

Package Base:

Description:

Maildir indexer/searcher and Emacs client (mu4e)

Upstream URL:

http://www.djcbsoftware.nl/code/mu

Licenses:

GPL-3.0-or-later

Submitter:

xyproto

Maintainer:

mroethke

Last Packager:

mroethke

Votes:

Popularity:

0.47

First Submitted:

2019-03-27 09:21 (UTC)

Last Updated:

2026-05-02 18:36 (UTC)

Latest Comments

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

ggnoredo commented on 2026-05-02 16:21 (UTC)

@onodrim thank you!

dordow commented on 2026-05-02 16:05 (UTC) (edited on 2026-05-02 16:13 (UTC) by dordow)

Yes, the trouble was that I could not build the latest version, the test failed. What now seems to work is

pkgctl build makepkg -si

It is now working. Thanks for assistance

onodrim commented on 2026-05-02 15:11 (UTC)

@ggnoredo The xapian-core package was recently updated. Re-building mu against the updated version should resolve that error (it did for me at least).

dordow commented on 2026-05-02 13:35 (UTC) (edited on 2026-05-02 13:40 (UTC) by dordow)

I got my hopes up too soon. When calling mu from command line, I get the same error as ggnoredo. When calling mu4e in Emacs, I get

mu4e-error: [mu4e] Found mu version nil, but mu4e needs version 1.12.14; please set mu4e-mu-binary' accordingly

ggnoredo commented on 2026-05-02 09:56 (UTC)

mu: error while loading shared libraries: libxapian.so.30: cannot open shared object file: No such file or directory

dordow commented on 2026-05-01 21:01 (UTC)

Thank you for the link. I normally use makeplg -si, today I tried 'pkgctl build' which seems to have worked.

mroethke commented on 2026-04-27 18:50 (UTC)

I want to know if you are following this wiki article when building the package.

dordow commented on 2026-04-26 12:09 (UTC)

I am sorry but I do not know how to check cleanliness of chroot. I have asked AI, but according to it I need to know the path to chroot. Where is that in the installation directory? Or elsewhere?

mroethke commented on 2026-04-25 21:22 (UTC)

@dordow are you building in a clean chroot?

@Frestein thanks for the hint!