Package Details: neomutt-git 20220429.r89.g5dfb39759-1

Git Clone URL: (read-only, click to copy)
Package Base: neomutt-git
Description: A version of mutt with added features - development branch
Upstream URL:
Licenses: GPL
Conflicts: neomutt
Provides: neomutt
Submitter: shioyama
Maintainer: Farzat
Last Packager: Farzat
Votes: 20
Popularity: 0.24
First Submitted: 2016-05-02 13:41 (UTC)
Last Updated: 2022-05-28 00:51 (UTC)

Latest Comments

flatcap commented on 2022-04-19 10:04 (UTC)

@Farzat Thanks for taking over.

Recently, I've been doing some major refactoring of NeoMutt's code. There's much more to come, but hopefully the worst is over.

If you have any questions, or discover something that's not-quite-right, please let me know.

I'm always on IRC: #neomutt on

afwlehmann commented on 2021-02-05 05:11 (UTC)

Thanks for the heads-up!

Rhinoceros commented on 2021-02-05 04:58 (UTC)

Oh, I realised I was the sole maintainer of this package. I didn't add myself, and I don't even use this package. I've disowned it now.

FWIW gnutls 3.7.0-1 works fine for me with the stable neomutt 20201127-1 (from the official repos). Maybe ask upstream or in the Arch forums.

afwlehmann commented on 2021-02-05 04:51 (UTC) (edited on 2021-02-05 04:51 (UTC) by afwlehmann)

Hi, it seems that 20201127-1 doesn't play well with gnutls later than 3.6.15-1. Maybe we need to update some neomutt dependencies here (I may be mistaken)?

Rhinoceros commented on 2018-08-13 02:07 (UTC)

Thanks for sorting that @Alad

Alad commented on 2018-08-12 13:46 (UTC)

Fixed and added Rhinoceros as comaintainer.

Alad commented on 2018-08-12 12:50 (UTC)

Sorry about that, I haven't had much time for packaging lately. I'll fix the package in the next few days.

shioyama commented on 2018-08-11 00:27 (UTC)

I was also witness to the friction and didn't really understand it. As I was trying to hand over this project, I added another potential maintainer who was eager to help in a similar situation where the package had not been updated. This was the spark that resulted in the argument below. But clearly the situation has not changed since then.

Rhinoceros commented on 2018-08-10 23:33 (UTC)

Hi @Alad. I'm not sure what's happening with this package, and I don't really understand what the friction in the comments below related to. However, it's been three weeks since I informed you of the broken package, with no response from you. It's a very simple fix, and upstream had promptly clarified that it was necessary. I'll give it a few more days, but otherwise I'm going to submit an orphan request. Just a heads-up for you.

(Also, there's already a pending request from someone else, but I'm not sure what that is.)

Rhinoceros commented on 2018-07-23 23:54 (UTC)

@Alad I'm also happy to help co-maintain this package if you like. I'm also a member of the Arch Users NeoMutt Team on GitHub.

Rhinoceros commented on 2018-07-20 11:59 (UTC)

Currently, sending encrypted mail (and possibly other things) is broken. More information here [a], but essentially, removing line 31 of the PKGBUILD fixes it for me. i.e. this line:

        --libexecdir=/usr/lib \


Alad commented on 2018-02-03 07:30 (UTC) (edited on 2018-02-03 08:36 (UTC) by Alad)

I may not be the most diplomatic at times, but I haven't escalated to personal attacks either, nor have I tried pinning comments in the sole purpose of shaming other users. It needn't be said that such course of action is not acceptable.

In any event, the 2 week period must be followed. Either "move on" or file an orphan request.

edit: since I can't reply to aur-requests at the moment, here's my response to the new orphan request:

commented on 2018-02-02 23:36 (UTC)

Re-opening an orphan request with malicious intent is melodrama. You could have asked me directly instead of making the request or commenting here; my email is on my account page. Let's not get confused about where the melodrama is coming from.

Why would I want your help, since you are a) being very rude and b) not competent (see my previous comment)?

Unless a TU wants to step in and let you have your way it is a definite no for me. Zero interest in working with you. The package is fixed so I'm going to move on with my life now. Sorry you're feeling small.

Alad commented on 2018-02-02 23:06 (UTC) (edited on 2018-02-02 23:07 (UTC) by Alad)

gemaputr, please spare me of your melodrama. Fact is that any maintainer gets a 2-week grace period on orphan requests, so it makes more than sense that the same counts for comaintainers. That's all there is to add here.

shioyama commented on 2018-02-02 22:59 (UTC)

@Alad Sorry I just wanted to leave the project to anyone who wanted to pick it up, so thought this made sense.

commented on 2018-02-02 21:14 (UTC)

@Alad, I apologize if my actions caused you distress. The comment from BlackLotus was posted 2 weeks ago and no action was taken during that time.

I think it is justifiable to assume that the package has been abandoned if it has been broken for an extended length of time and no action is taken by the maintainers, particularly if a resolution has been provided. I hope you can understand that my intent was not to harm you.

Normally I would have no issues, but I see that you have re-submitted an orphan request... That is intellectually dishonest. You have neglected a duty that you volunteered to undertake for over 2 weeks. And now you're behaving maliciously. Not cool.

Alad commented on 2018-02-02 17:08 (UTC)

You know, you could give someone more than 1 day time before messing with the maintainer list... especially when you're a new maintainer in name only and have yet to fix anything.

BlackLotus89 commented on 2018-01-16 12:48 (UTC) (edited on 2018-01-16 12:50 (UTC) by BlackLotus89)

cf3e8ff350796165d20cd7078d2048ee82e850cb removed autotools (and with it ./prepare)

So now the prepare statement is something like

./configure \
--prefix=/usr \
--sysconfdir=/etc \
--enable-debug \
--enable-pgp \
--enable-gpgme \
--enable-notmuch \
--with-gss=/usr \
--with-ssl=/usr \
--with-sasl=/usr \
--with-idn=/usr \

With optional --enable-lua

shioyama commented on 2017-10-24 14:10 (UTC)

Hi Alad, I've just added you as co-maintainer, thanks! I'm personally using neomutt from community so not really invested in keeping this up-to-date anymore. Chris

Alad commented on 2017-10-24 08:27 (UTC)

Hi shioyama, besides the below comment on mime.types, this package no longer conflicts with mutt since upstream changed all references to "neomutt". It does however conflict with neomutt in community. I'm happy to (co)maintain this package if you don't have the time to make the necessary changes. Best, Alad

tpreissler commented on 2017-10-10 09:24 (UTC)

Building NeoMutt 20171006-5-c1eb1e today failed with rm: cannot remove '/tmp/yaourt-tmp-tomtom/aur-neomutt-git/pkg/neomutt-git/etc/mime.types': No such file or directory rm: cannot remove '/tmp/yaourt-tmp-tomtom/aur-neomutt-git/pkg/neomutt-git/etc/mime.types.dist': No such file or directory ==> ERROR: A failure occurred in package(). Aborting... ==> ERROR: Makepkg was unable to build neomutt-git. Commenting out line 61 in the PKGBUILD 60 # Cruft we don't want. 61 # rm "${pkgdir}"/etc/mime.types{,.dist} fixed this issue and Neomutt is packaged just fine. Thanks for providing this package.

Chinggis6 commented on 2017-02-28 00:41 (UTC)

I can't build it (and neomutt as well). I have mutt installed. I tried building with makepkg and yaourt (both from AUR and locally). It has `configure: error: Compiler not ANSI compliant` as error. I have gdbm installed (gcc, as well as all optional dependencies). I build it `yaourt -S --m-arg "with-gdbm"`. Where am I being wrong? Please help. "compiler not ANSI compliant" is the last line in the output checking minix/config.h usability... no checking minix/config.h presence... no checking for minix/config.h... no result of `configure -help` after `autoreconf -i` (when directly attempting to build from its source code): checking whether it is safe to define __EXTENSIONS__... yes checking build system type... Invalid configuration `–help': machine `–help' not recognized configure: error: /bin/sh ./config.sub –help failed

shioyama commented on 2017-02-25 12:50 (UTC)

@sangy Thanks, updated to use master.

sangy commented on 2017-02-23 16:35 (UTC)

Hi, it seems that the neomutt branch is gone now. You may want to clone from master instead. Thanks!

shioyama commented on 2016-11-28 12:07 (UTC)

I've added --with-gdbm since we have gdbm in the depends list now, and it compiles correctly.

shioyama commented on 2016-11-28 12:07 (UTC)

I've added --with-gdbm since we have gdbm in the depends list now, and it compiles correctly.

flatcap commented on 2016-11-26 12:02 (UTC)

@qwence: aha! neomutt-git is the latest (unreleased/undocumented) source. You've discovered one of our new features -- multiple hcache backends. Along with --enable-hcache you will now need to select one (or more) of --with-bdb --with-gdbm --with-kyotocabinet --with-lmdb --with-qdbm --with-tokyocabinet If you have multiple backends installed you can select one with, e.g. $header_cache_backend = kyotocabinet

qwence commented on 2016-11-26 02:07 (UTC)

I have qdbm installed, and I had to add --with-qdbm to the PKGBUILD to avoid the error message configure: error: You need Tokyo Cabinet, Kyoto Cabinet, QDBM, GDBM, Berkeley DB or LMDB for hcache

Rhinoceros commented on 2016-08-12 00:00 (UTC)

Thanks @shioyama.

shioyama commented on 2016-08-11 07:15 (UTC)

@Rhinoceros Oops, reverted the last commit, should fix that.

Rhinoceros commented on 2016-08-11 04:56 (UTC)

The new package won't install. It tries to install `/etc/mime.types`, which already exists, and is owned by the package mime-types… which is a dependency of neomutt-git.

shioyama commented on 2016-08-11 04:14 (UTC)

Fixed the PKGBUILD, should work now.

jakkin commented on 2016-08-11 03:42 (UTC)

I was able to get it to compile by removing everything below the "#Cruft we don't want." line.

shioyama commented on 2016-08-08 07:37 (UTC)

@danir I'll check up on fixing the build, I'm using neomutt not this one so hadn't really noticed any issues. > Also, why is there a PKGBUILD_gold file in the committed repo? Looks like something you added by mistake Sorry don't know what you're talking about. There is only a PKGBUILD and a .SRCINFO.

darnir commented on 2016-08-07 23:21 (UTC)

P.S.: Can we not have debug enabled by default? I'm not sure what it does, but I doubt normal users want it. Anyone building the git version can enable it manually should they need to

darnir commented on 2016-08-07 23:18 (UTC)

Build is currently broken since NeoMutt removed muttbug and flea. Also, why is there a PKGBUILD_gold file in the committed repo? Looks like something you added by mistake