Package Details: joplin-appimage 2.14.20-2

Git Clone URL: https://aur.archlinux.org/joplin-appimage.git (read-only, click to copy)
Package Base: joplin-appimage
Description: The latest stable AppImage of Joplin - a cross-platform note taking and to-do app
Upstream URL: https://github.com/laurent22/joplin
Keywords: appimage joplin markdown note notetaking productivity
Licenses: MIT
Conflicts: joplin-desktop
Submitter: icefox
Maintainer: thynkon
Last Packager: thynkon
Votes: 86
Popularity: 2.50
First Submitted: 2020-06-19 14:03 (UTC)
Last Updated: 2024-03-19 21:34 (UTC)

Pinned Comments

thynkon commented on 2021-06-16 20:49 (UTC)

Attention

From now, this package will only track stable releases of Joplin.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »

Zodiac commented on 2021-07-15 15:04 (UTC)

I switched over this package (previously i was using joplin-desktop) because its updated more frequently, faster, and It Just Works (tm). No problems so far, good job to the maintainer/s

thynkon commented on 2021-06-16 20:49 (UTC)

Attention

From now, this package will only track stable releases of Joplin.

thynkon commented on 2021-06-05 12:14 (UTC) (edited on 2021-06-05 12:14 (UTC) by thynkon)

Attention

This package was not updated to v2.0.4 because the checksum of the appimage file provided by the upstream is not correct. It will be fixed in the next Joplin's release. Github issue link

thynkon commented on 2021-05-19 18:33 (UTC)

Hi @FillFeile, since more people are using this package and there is no other AUR package that keeps up with the stable release of Joplin, I will do it.

I'm just waiting for the next stable release so I can update the description of this package.

Again, thanks for your feedback and feel free to contact me if you have any questions or suggestions.

FillFeile commented on 2021-05-18 06:55 (UTC)

Hi @thynkon, thanks for your fast reply.

Sorry for that.. a proper read might have clarified things in the first place.

I think what derailed me is the pinned comment which (also with a picture) refers to the latest release. Maybe if this is inaccurate one can remove it.

thynkon commented on 2021-05-17 19:38 (UTC)

Hi @FillFeile, thanks for your remarks. As you can see from the description of this package, I only package the Joplin pre-releases.

So yes, this is intentional. But, if most of the users of this package are only interested in the stable releases, I might start using this package to track the stable releases of Joplin.

If you still have questions, please let me know.

FillFeile commented on 2021-05-17 16:21 (UTC)

Dear @thynkon, thanks for maintaining this one.

I noticed that you recently packaged v2.0.1 of Joplin which is (as stated on GitHub and the project website) still a pre-release version.

The latest stable version at time of writing seems to be v1.8.5.

Is this intentional?

Cheers, FillFeile

thynkon commented on 2021-04-05 05:09 (UTC)

Hi @ocelotsloth, thanks for your feedback. I don't know how I missed that. fuse2 has been added to the PKGBUILD file as a runtime dependency.

If you still have problems building the package, feel free to contact me.

ocelotsloth commented on 2021-04-04 23:52 (UTC)

Looks like fuse2 is a runtime dependency.

❯ /opt/appimages/Joplin.AppImage 
dlopen(): error loading libfuse.so.2

AppImages require FUSE to run. 
You might still be able to extract the contents of this AppImage 
if you run it with the --appimage-extract option. 
See https://github.com/AppImage/AppImageKit/wiki/FUSE 
for more information

Can you update the PKGBUILD to add fuse2 as a runtime dependency? Thanks!

thynkon commented on 2020-12-30 12:38 (UTC)

Usually this package tracks the highest/latest version but v1.5.14 fixed some errors that I thought that could be useful for everyone who uses this package. As you said, the upstream is tagging versions out of order and I don't know if they are working on a new version or if it was a mistake.

For now, the latest version of this package will remain "v1.5.14" for the reason I mentioned above and I will keep monitoring the upstream tags.

Thanks for your feedback @vith.