Running update terminal per usual, running into this error:
The next patch would create the file yarn.lock,
which already exists! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
==> ERROR: A failure occurred in prepare().
Aborting…
→ error making: joplin (joplin joplin-desktop)
I have tried yes/no and Enter, error persists. What am I overlooking?
I switched to the joplin-appimage package as it was being updated more frequently; never had this problem.
I may need to move to that. No issues with current until now.
Moving my Nextcloud also, once I can sync I may try your recommendation.
Try cleanbuilding it.
Yes, I always have and did this time as well. Thanks for the feedback
Just moved over with data intact, thanks for the heads up and guidance.
How do I clean this up? I deleted the joplin.desktop but it reappeared after appimage install. Keeps throwing this error dialogue.
That looks like appimagelauncher getting in the way. Do you have that installed from AUR?
I just yay -S joplin-appimage after I deleted the other install/repo
What does pacman -Qs appimage show?
[username@user ~]$ pacman -Qs appimage
local/appimagelauncher 2.2.0-5
A Helper application for running and integrating AppImages.
local/joplin-appimage 2.6.10-1
The latest stable AppImage of Joplin - a cross-platform note taking and to-do app
local/libappimage 1.0.3-5
Reference implementation of the AppImage specification
See…you have appimagelauncher installed. It was probably already installed.
It is an application that makes it easier to work with appimages but it gets in the way in cases like this.
I would either remove appimagelauncher or just use the appimage directly from the joplin page and let appimagelauncher manage it for you.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.