AUR package [Results in SSL errors] about mailspring HOT 26 CLOSED

Hey! How do folks feel about snapcraft.io? The current plan is to release a single "containerized" Snap package for all linux distros, because it makes things easy for developers and supports autoupdate (which is fairly challenging to do across distros on Linux). I've been talking with a few folks at Canonical and the Snap should be ready by the end of the week.

Also working on that libicuuc issue—I've changed the app to statically link against most of it's library dependencies, and for the handful left (like libicuuc), I'm hoping to package them into the app so you don't need to install them separately (total, they're only ~3MB)

from mailspring.

I'd prefer a flatpak http://flatpak.org/ since I'm not an Ubuntu user (I'm on Fedora). I know a snap technically should work too. I dont know what the status for snaps vs flatpaks is today, which is easier, more popular, etc. but I think flatpaks are available in more distributions than Ubuntu's snaps.

from mailspring.

Ok. Prototype PKGBUILD for you: https://gist.github.com/ConorIA/b8c7c3ef6d70902dff169afbbbff7d2b
Build with makepkg.

I do not plan to submit this to the AUR until there is clarity over whether or not @bengotow will continue to provide .debs or just snaps. There is also a nasty shared library workaround that is probably not allowed for AUR standards (see the end of the PKGBUILD). Please comment on the gist if depends should be added and/or removed. Let's also not annoy @bengotow about bugs/issues unless we're sure they are in Mailspring and not in this PKGBUILD.

from mailspring.

Hey folks—the libsasl2 should be fixed in the next release. It'll definitely be nice to have the Snap build, but in 1.0.3 (coming later today) it should at least be possible to build a working AUR!

from mailspring.

@ConorIA Yeah, I'm getting those SSL errors as well. For now I checked the 'insecure stmp/imap' boxes.

from mailspring.

@ConorIA Very true. The AppImage devs say that is by design (offer pre-packaged apps and let users decide where to install, whether to update, etc.). I seem to have glossed over that requirement. Thanks. And I, too, would prefer an AUR package.

from mailspring.

A snap would be great for us Solus users.

from mailspring.

I'm using the newest AUR package and I got this error:

Waiting for Account JSON:
Waiting for Identity JSON:
{"error":"Identity is missing required fields."}

Just this, nothing else. Anybody knows why?

from mailspring.

I have the same problem like @JunnanZ with AUR package

from mailspring.

That would be icu52 from the AUR, I think.
Also, if you haven't seen this (I only learned about it recently), the -Fs pacman flag is awesome:

> sudo pacman -Fy 
> sudo pacman -Fs libicuuc.so     
core/icu 59.1-2
    usr/lib/libicuuc.so
multilib/lib32-icu 59.1-1
    usr/lib32/libicuuc.so

from mailspring.

AppImage is nice for those who don't want the extra overhead. It doesn't check off @bengotow's autoupdate requirement though. I'd personally just prefer a .Deb for someone on the AUR to tear open and package up nice and clean for Arch(-derivs).

from mailspring.

@ConorIA Thank you so much! Much appreciated. Getting those SSL errors as well, but until I investigate further I'm following @b0o's lead in allowing insecure connections. Thanks.

from mailspring.

I think this issue can be closed. The AUR package is working just fine with the 1.0.3 release. :)

from mailspring.

I have the same problem as @JunnanZ but with the .deb package (version 1.0.3 on Ubuntu 17.04).

from mailspring.

I also have the same problem. Not sure if we should create a separate issue or piggyback on the end of this one though

I already tried reinstalling twice, both time clearing out ~/.config/Mailspring so as not to have older configs conflict

from mailspring.

@ConorIA

Thanks! The icu52 package solved that error, but now I'm getting this:

libcurl.so.4: version 'CURL_OPENSSL_3' not found

Searching for that error, I found this thread: https://bbs.archlinux.org/viewtopic.php?id=187871

If that's correct, Mailspring is requiring an old version of libcurl? I'd rather not have to install an old version just for one application to work.

For some other libraries I've installed (like libtidy and libctemplate), I couldn't find the exact same version, so I tried to just symlink Mailspring's expected version to the closest version I could find, just to see if I could get things to work at all.

I'm curious to know if you're able to get Mailspring running on Arch?

from mailspring.

Personally, I'd lean more towards flatpak...but that's ONLY because I'm more familiar with it. Though, it looks like Snap is pretty widely available.

Install docs indicate:

• Arch Linux
• Debian
• Fedora
• Gentoo
• OpenEmbedded/Yocto
• openSUSE
• OpenWrt
• Solus
• Ubuntu

shrug I'm just looking forward to getting it installed!

from mailspring.

And/or would AppImage meet your needs? I've had great success with them as a user on different systems, though I've never developed for it.

Can't wait for this!

from mailspring.

@ConorIA

You're a badass. That worked PKGBUILD flawlessly, thank you!

from mailspring.

@b0o, just make sure you have gnome-keyring installed. I got my depend wrong!
Also, I'm gettting SSL errors trying to add accounts! 😢

from mailspring.

+1 for deb or snap. Flatpak might work too but please no AppImage. It is just like one big blob lying around randomly in your filesystem, that even hast be made executable manually ^^ (I'm also fine with just running it from the github source, if I can tell it where the sync engine is)

from mailspring.

FYI: Somebody has created an AUR package: https://aur.archlinux.org/packages/mailspring/
Sadly, I'm getting SSL errors as well 😕

from mailspring.

@kolletzki, thanks for the link. Interesting. I tried symlinking libsasl2.so.2 to libsasl2.so.3, but I still got errors, it seems to have worked for this guy on the AUR though. My only other changes were mostly personal preference about how I like to have my filesystem organized, so my PKGBUILD above really offers no advantage (that I can see) over the current AUR package.

from mailspring.

Hey folks! Please do not replace libsasl2.so with a different version - you'll get SSL errors, certificate problems authenticating with SMTP, etc., or it just won't run at all. The .deb package should contain the correct version of libsasl2 already alongside the mailsync.bin file!

from mailspring.

@bengotow, if we don't link libsasl2.so.2, Mailspring complains about the missing library and doesn't launch. I wonder why it doesn't know to look in the correct folder.

I've tried linking to /usr/share/mailspring/resources/app.asar.unpacked/libsasl2.so.2, but this didn't solve the issue either. I guess I'm really looking forward to the snap! 😛 Thanks for your work on Mailspring!

Really though, my main barrier to usage right now is that on my laptop (dual core), Mailspring completely maxes my CPU and then dies. This does not, however, happen on my desktop (quad-core).

from mailspring.

@ZakharH you are right; we should create a new issue as this is apparently not specific to the AUR package. See #123.

from mailspring.