Package Details: neomutt-git 20191025.r59.g3cd616659-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: Rhinoceros
Last Packager: Alad
Votes: 18
Popularity: 0.20
First Submitted: 2016-05-02 13:41
Last Updated: 2019-10-31 21:48

Latest Comments

1 2 3 4 Next › Last »

Rhinoceros commented on 2018-08-13 02:07

Thanks for sorting that @Alad

Alad commented on 2018-08-12 13:46

Fixed and added Rhinoceros as comaintainer.

Alad commented on 2018-08-12 12:50

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

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

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

@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

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

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:

Anonymous comment on 2018-02-02 23:36

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

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.