Package Details: pantheon-mail-git r2876.e1bb88dc-1

Git Clone URL: (read-only)
Package Base: pantheon-mail-git
Description: The Pantheon Mail Client
Upstream URL:
Licenses: GPL3
Conflicts: pantheon-mail
Provides: pantheon-mail
Replaces: pantheon-mail-bzr
Submitter: alucryd
Maintainer: alucryd
Last Packager: alucryd
Votes: 9
Popularity: 0.083419
First Submitted: 2017-05-01 14:36
Last Updated: 2017-05-01 14:36

Latest Comments

1 2 3 4 Next › Last »

FFY00 commented on 2018-06-22 19:44

Thanks. I was just wondering because I was able to build it with stable granite. I didn't know about the level of unstability in granite. Thanks anyway :)

alucryd commented on 2018-06-21 08:34

Development obviously happens on granite HEAD, and packages often break with satble granite.

FFY00 commented on 2018-06-20 22:57

Is there any reason to depend on 'granite-git' instead of 'granite'?

alucryd commented on 2017-12-27 21:01

You need to rebuild webkitgtk.

spacekookie commented on 2017-11-19 23:53

The software doesn't compile for me anymore but it doesn't seem to be the packages fault (manually doesn't work either).

Still, anyone got an idea what to do to make it work?


Shatur commented on 2017-07-17 21:58

Can you add gnome-keyring to tepends? Without it I can't login into account after program reload.

90torf commented on 2016-10-05 19:42

To fix PKGBUILD, to depends add:

depends=(... 'libaccounts-glib' 'libgsignon-glib')

Works for me.

alucryd commented on 2016-09-12 15:58

@asonix: Thanks for the kind words, I may come up a bit heavy sometimes, but I particularly dislike when people assume they can wing something that requires at least some reading beforehand.

I did see your comment and already added the deps on my github repo, but mail still doesn't build, saying it doesn't find the libgsignon-glib vapi even though it's there. I need to investigate before I can upload something that works here.

asonix commented on 2016-09-12 15:45

killua99, the contributors comment is not for the developers of the package, but the past maintainers. Removing alucryd from the comment is rude.

I'm not exactly sure, but it seems like you wanted alucryd to use your changes from a stable build of pantheon mail. -bzr packages are inherently unstable since they pull from a vcs upstream. If you want a stable package in addition to the -bzr package, you can release it as 'pantheon-mail.'

Personally, I have been guilty of maintaining -bzr and -git packages without rtfm (including this one, check the # contributors in the PKGBUILD). But it is always better to let experienced maintainers handle things.

alucryd may come off as rude sometimes (ex. earlier in this thread "This package has so many wrong deps, among other things, I don't know where to start. Please disown so I can maintain it along the rest of Pantheon."), but it isn't hard to just assume people mean well.

If you're new to packaging, I'd suggest you give value to the input of someone experienced in the area. This package is in a much better place than it was when I was maintaining it.

P.S. Hey alucryd, did you see my comment about the missing libraries?

alucryd commented on 2016-09-12 15:35

I believe you should look up the word insult then.

Anyway, stop trying to victimize yourself, you are clearly in the wrong. You contacted me about granite-bzr being out of date because you don't know that a VCS package's pkgver on AUR means nothing, never about this one not building. I just came back from my vacation and had more importatnt things to do than update this package first thing in the morning, some people go to work.

Moreover, if you had read the wiki page on AUR, you would have understood that names in a PKGBUILD have nothing to do with upstream contributors, and the rules state that you should not delete them, period. Well even without reading, it's called common sense, really.

Oh, FTR, I contribute to upstream Pantheon, sorry to disappoint you there mate.