Package Details: mailspring 1.9.2-2

Git Clone URL: (read-only, click to copy)
Package Base: mailspring
Description: A beautiful, fast and maintained fork of Nylas Mail by one of the original authors.
Upstream URL:
Keywords: email mail multiple-accounts nylas
Licenses: custom: GPL3 and (C) 2016-2019 Foundry 376, LLC.
Submitter: jnylen
Maintainer: slondr (mandeepsan)
Last Packager: mandeepsan
Votes: 193
Popularity: 5.95
First Submitted: 2017-10-06 10:00
Last Updated: 2021-09-29 10:02

Latest Comments

« First ‹ Previous ... 8 9 10 11 12 13 14 15 16 17 18 ... Next › Last »

ulgens commented on 2019-10-15 07:29

For release 1.7.1, change pkgver to 1.7.1 and sha256sum to 7f9bea33834494e019e6c1e451583a218e340c6c9cfc043c35e40fe6726e9e11

AK4EVA commented on 2019-10-14 18:52

I'm not sure when this will be updated, but in the meantime, you can do the following when trying to install this package:

-Modify the pkgbuild file (usually your program of choice will give you an option to view the file, select yes)

CHANGE THE FOLLOWING: - pkgver to 1.7.0 - SHA256SUM to f70bf76692991a70887fec815672503de312a6126ba84bbe18bde921301ac811

Save and continue with build, ENJOY! :)

tasty213 commented on 2019-07-24 17:21

I just installed mailspring and it didn't install or at libsecret at all i've had to manually install it, i will try and reinstall looking at the package as i go

mrueg commented on 2019-07-20 12:00

Just tried installing mailspring with the new libsecret-only dependency. Something else that was provided by gnome-keyring seems to be missing now, as I got an error saying that libsecret was missing (which it wasn't) and the problem disappeared when I installed gnome-keyring.

jnylen commented on 2019-03-23 14:38

@flying-sheep, I can look into it when a new release comes if you don't mind.

flying-sheep commented on 2019-03-22 14:32

Hi! mailspring uses the keytar npm package, which uses libsecret, not directly gnome-keyring.

could you please make the libgnome-keyring and gnome-keyring deps optional?

friday commented on 2019-03-20 14:35

@jnylen: It seems to be possible, but you would need asar as a build dependency and it's a bit quirky. The built output also includes 65mb of files which the original build step excludes. It might be possible build it with grunt too, but that would add another dependency. From the directory app.asar is in: asar extract app.asar app; sed -i 's/updater.getState()/0/g' app/internal_packages/notifications/lib/items/update-notification.js; asar pack app app.asar; rm -rf app;

Not sure if it's fully safe. Trying it out now (notification is gone and it works).

Edit: Commented at the github issue instead since code formatting is not very readable here.

Edit 2: While it worked I found a simpler way compatible with this package: echo -e '\n127.0.0.1' | sudo tee -a /etc/hosts

rashintha commented on 2019-03-20 12:49

@ilyes24 please check releases at before flagging the package.

jnylen commented on 2019-03-18 17:58

Updated it to 1.6.0. Thanks for notifying me.

@friday, Problem here is we are using the .deb file. Which means it's already compiled and built for us. So we can't really patch the binary (if you know a way do tell me). We could move to the git repo but that will make it a messy aur build.

I wrote a comment on the issue asking if there was a safe way to disable it.

friday commented on 2019-02-12 20:39

Suggestion: Add a patch to disable or hide the update notification: The dev doesn't seem to care much about "third-party distribution that lags behind releases". I think you just need to change this line to const updateAvailable = false or something similar: