Package Details: joplin-desktop 3.0.14-1

Git Clone URL: https://aur.archlinux.org/joplin.git (read-only, click to copy)
Package Base: joplin
Description: A note taking and to-do application with synchronization capabilities - Desktop
Upstream URL: https://joplinapp.org/
Keywords: markdown note notetaking productivity
Licenses: MIT
Groups: joplin
Conflicts: joplin-desktop-electron
Submitter: masterkorp
Maintainer: masterkorp
Last Packager: masterkorp
Votes: 264
Popularity: 2.56
First Submitted: 2018-04-18 16:33 (UTC)
Last Updated: 2024-07-29 19:54 (UTC)

Pinned Comments

masterkorp commented on 2021-12-27 11:30 (UTC) (edited on 2021-12-27 11:32 (UTC) by masterkorp)

Hello everyone,

There was been several difficulties upgrading the Joplin due to major changes in the build system upstream.

I have finnally got version 2.6.10 working with pacthes, but remenber:

  • You may need to remove your src/ folder before using this version

  • The patches are still not perfect, you must say yes to a prompt

I will continue working on this later today, but its usable and stable, please remenber you can always report issues on the github repository.

Regards, Alfredo Palhares

masterkorp commented on 2020-12-24 19:58 (UTC) (edited on 2020-12-24 20:00 (UTC) by masterkorp)

Hello everyone,

I will be renaming the packages to its final form.

  • joplin will contain the CLI application
  • joplin-desktop will contain the Desktop version

Also, please for problems with the package, please open an issue on the Github repo, its really hard to provide support on the comments section, you can also email me.

If you have problems with the check() function, just run makepkg with the --nocheck flag.

Thank you for your patience. Regards, Alfredo Palhares

Latest Comments

« First ‹ Previous 1 .. 22 23 24 25 26 27 28 29 30 31 32 .. 54 Next › Last »

paro commented on 2020-12-23 13:21 (UTC)

I opened an issue on maintainer github (https://github.com/alfredopalhares/arch-pkgbuilds/issues/66) with various notes and comments. I'm fixing the pkgbuild and willing to share my solution if maintainer doesn't show up. For the time being, I'd suggest to simply compile the packages with makepkg and then install the joplin package alone (with pacman -U).

Entrust0398 commented on 2020-12-23 12:00 (UTC)

Hi all, I'm having problems with the current build I don't understand, hoping for some help. I first tried to update a few days ago and I got this error message:


joplin on  master [?]
➜  makepkg -si
==> WARNING: The package group has already been built, installing existing packages...
==> Installing joplin package group with pacman -U...
loading packages...
resolving dependencies...
looking for conflicting packages...
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: joplin and joplin-desktop-electron are in conflict
==> WARNING: Failed to install built package(s).
makepkg -si  6.68s user 2.74s system 109% cpu 8.598 total

I have tried uninstalling the previous packages and pulled the latest version each time one has become available over the past few days but to no avail. Any help would be greatly appreciated.

maciex commented on 2020-12-22 19:57 (UTC) (edited on 2020-12-22 19:57 (UTC) by maciex)

Hello, I'm trying to install this package but i have:

rror: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: joplin and joplin-desktop-electron are in conflict

I do not have joplin-desktop-electron installed.

greve commented on 2020-12-22 10:30 (UTC) (edited on 2020-12-22 11:24 (UTC) by greve)

When starting joplin-desktop:

./@joplinapp-desktop: error while loading shared libraries: libicui18n.so.67: cannot open shared object file: No such file or directory

I cannot recall when the last time was it worked, I completely lost track of what is going on with this package ...

EDIT: (Re)Did yay -S --mflags="--nocheck" joplin and it works again.

phonemic commented on 2020-12-21 13:08 (UTC)

@masterkorp --nocheck is still needed for the build to succeed. I agree, it would be great if you could test locally then push one commit when ready.

figue commented on 2020-12-21 11:50 (UTC)

with "makepkg -f" you can force the build. No need to bump if not necessary. Is better to make changes locally and, at the end, push the update to AUR, as Rhinoceros suggest.

Rhinoceros commented on 2020-12-21 11:07 (UTC) (edited on 2020-12-21 12:57 (UTC) by Rhinoceros)

@masterkorp Oh okay. Maybe I missed something. Can't you just makepkg locally without pushing changes? What else does the AUR do exactly?

masterkorp commented on 2020-12-21 10:40 (UTC)

@Rhinocerors

I need to test the releases, I absolutely no other way to test the releases and the multiple package integration of the AUR

Also, `--nocheck`` is not needed anymore even, the check function is a force pass.

Rhinoceros commented on 2020-12-20 22:38 (UTC) (edited on 2020-12-20 22:39 (UTC) by Rhinoceros)

@masterkorp Could you please stop pushing multiple updates? I've had to rebuild this so many times in the last few weeks. Can you please just put all your changes in one $pkgrel bump? There really shouldn't be any need for 12 bumps. Also, since the PKGBUILD is broken (check() still fails), it's quite annoying to re-install the same version 13 times.

EDIT: it's also worth pinning one of the comments about building with --nocheck

« First ‹ Previous 1 .. 22 23 24 25 26 27 28 29 30 31 32 .. 54 Next › Last »