Package Details: joplin 2.14.20-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 - CLI App
Upstream URL: https://joplinapp.org/
Keywords: markdown note notetaking productivity
Licenses: MIT
Groups: joplin
Submitter: masterkorp
Maintainer: masterkorp
Last Packager: masterkorp
Votes: 256
Popularity: 2.11
First Submitted: 2018-04-18 16:33 (UTC)
Last Updated: 2024-04-06 17:49 (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

1 2 3 4 5 6 .. 53 Next › Last »

zangoku commented on 2024-04-22 22:13 (UTC)

No longer builds since last update:

➤ YN0007: │ husky@patch:husky@npm%3A3.1.0#./.yarn/patches/husky-npm-3.1.0-5cc13e4e34.patch::version=3.1.0&hash=d9603f&locator=root%40workspace%3A. must be built because it never has been before or the last one failed
➤ YN0007: │ keytar@npm:7.9.0 must be built because it never has been before or the last one failed
➤ YN0007: │ sharp@npm:0.33.2 must be built because it never has been before or the last one failed
➤ YN0007: │ sqlite3@npm:5.1.6 [ea905] must be built because it never has been before or the last one failed
➤ YN0007: │ canvas@npm:2.11.2 must be built because it never has been before or the last one failed
➤ YN0007: │ tesseract.js@npm:5.0.4 must be built because it never has been before or the last one failed
➤ YN0007: │ core-js@npm:3.33.1 must be built because it never has been before or the last one failed
➤ YN0007: │ core-js-pure@npm:3.33.1 must be built because it never has been before or the last one failed
➤ YN0007: │ @fortawesome/fontawesome-free@npm:5.15.4 must be built because it never has been before or the last one failed
➤ YN0007: │ electron@npm:26.5.0 must be built because it never has been before or the last one failed
➤ YN0007: │ @fortawesome/fontawesome-common-types@npm:0.2.36 must be built because it never has been before or the last one failed
➤ YN0007: │ @fortawesome/fontawesome-common-types@npm:6.4.2 must be built because it never has been before or the last one failed
➤ YN0007: │ @fortawesome/fontawesome-common-types@npm:6.1.2 must be built because it never has been before or the last one failed
➤ YN0007: │ root@workspace:. must be built because it never has been before or the last one failed
➤ YN0007: │ @fortawesome/fontawesome-svg-core@npm:1.2.36 must be built because it never has been before or the last one failed
➤ YN0007: │ @fortawesome/free-regular-svg-icons@npm:5.15.4 must be built because it never has been before or the last one failed
➤ YN0007: │ @fortawesome/free-solid-svg-icons@npm:5.15.4 must be built because it never has been before or the last one failed
➤ YN0007: │ @fortawesome/fontawesome-svg-core@npm:6.4.2 must be built because it never has been before or the last one failed
➤ YN0007: │ @fortawesome/free-brands-svg-icons@npm:6.4.2 must be built because it never has been before or the last one failed
➤ YN0007: │ @fortawesome/free-regular-svg-icons@npm:6.4.2 must be built because it never has been before or the last one failed
➤ YN0007: │ @fortawesome/free-solid-svg-icons@npm:6.4.2 must be built because it never has been before or the last one failed
➤ YN0007: │ @fortawesome/fontawesome-svg-core@npm:6.1.2 must be built because it never has been before or the last one failed
➤ YN0007: │ @fortawesome/free-solid-svg-icons@npm:6.1.2 must be built because it never has been before or the last one failed
➤ YN0009: │ root@workspace:. couldn't be built successfully (exit code 1, logs can be found here: /tmp/xfs-d9e20c07/build.log)
➤ YN0000: └ Completed in 42s 582ms
➤ YN0000: Failed with errors in 44s 593ms
==> ERROR: A failure occurred in build().

tomacrisan commented on 2024-04-16 22:32 (UTC) (edited on 2024-04-16 22:36 (UTC) by tomacrisan)

Sorry to bother everyone, I'm encountering this error during the build and have no idea how to proceed.

➤ YN0000: [@joplin/app-desktop]: Process exited (exit code 1), completed in 16s 783ms
➤ YN0000: The command failed for workspaces that are depended upon by other workspaces; can't satisfy the dependency graph
➤ YN0000: Failed with errors in 35s 928ms
at makeError (/home/tom/.cache/yay/joplin/src/joplin-2.14.20/node_modules/execa/lib/error.js:60:11)
at handlePromise (/home/tom/.cache/yay/joplin/src/joplin-2.14.20/node_modules/execa/index.js:118:26)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async execCommand (/home/tom/.cache/yay/joplin/src/joplin-2.14.20/gulpfile.js:27:17)
at async fn (/home/tom/.cache/yay/joplin/src/joplin-2.14.20/gulpfile.js:64:5)

joow commented on 2024-04-12 05:50 (UTC)

Hello @masterkorp

I also have the same issue regarding GPG private key access.

It looks like the build is trying to sign a commit (my gitconfig turns on Git commit signing) :

➤ YN0000: [@joplin/app-desktop]: > git clone -- https://github.com/JackGruber/joplin-plugin-backup.git /home/###/aur/joplin/src/joplin-2.14.20/packages/default-plugins/plugin-sources/io.github.jackgruber.backup
➤ YN0000: [@joplin/app-desktop]: Cloning into '/home/###/aur/joplin/src/joplin-2.14.20/packages/default-plugins/plugin-sources/io.github.jackgruber.backup'...
➤ YN0000: [@joplin/app-desktop]:  Switching to commit 2d814a5466604daced108331d14aedf8e8414d62
➤ YN0000: [@joplin/app-desktop]: > git switch master
➤ YN0000: [@joplin/app-desktop]: Already on 'master'
➤ YN0000: [@joplin/app-desktop]: Your branch is up to date with 'origin/master'.
➤ YN0000: [@joplin/app-desktop]: > git checkout 2d814a5466604daced108331d14aedf8e8414d62
➤ YN0000: [@joplin/app-desktop]: Note: switching to '2d814a5466604daced108331d14aedf8e8414d62'.
➤ YN0000: [@joplin/app-desktop]:
➤ YN0000: [@joplin/app-desktop]: You are in 'detached HEAD' state. You can look around, make experimental
➤ YN0000: [@joplin/app-desktop]: changes and commit them, and you can discard any commits you make in this
➤ YN0000: [@joplin/app-desktop]: state without impacting any branches by switching back to a branch.
➤ YN0000: [@joplin/app-desktop]:
➤ YN0000: [@joplin/app-desktop]: If you want to create a new branch to retain commits you create, you may
➤ YN0000: [@joplin/app-desktop]: do so (now or later) by using -c with the switch command. Example:
➤ YN0000: [@joplin/app-desktop]:
➤ YN0000: [@joplin/app-desktop]:   git switch -c <new-branch-name>
➤ YN0000: [@joplin/app-desktop]:
➤ YN0000: [@joplin/app-desktop]: Or undo this operation with:
➤ YN0000: [@joplin/app-desktop]:
➤ YN0000: [@joplin/app-desktop]:   git switch -
➤ YN0000: [@joplin/app-desktop]:
➤ YN0000: [@joplin/app-desktop]: Turn off this advice by setting config variable advice.detachedHead to false
➤ YN0000: [@joplin/app-desktop]:
➤ YN0000: [@joplin/app-desktop]: HEAD is now at 2d814a5 Remove wrong section
➤ YN0000: [@joplin/app-desktop]: > git rev-parse --verify HEAD^{commit}
➤ YN0000: [@joplin/app-desktop]: 2d814a5466604daced108331d14aedf8e8414d62
➤ YN0000: [@joplin/app-desktop]:  Copying repository files...
➤ YN0000: [@joplin/app-desktop]:  Initializing repository.
➤ YN0000: [@joplin/app-desktop]: > git init . -b main
➤ YN0000: [@joplin/app-desktop]: Initialized empty Git repository in /tmp/default-plugin-buildqUQ6kM/.git/
➤ YN0000: [@joplin/app-desktop]:  Creating initial commit.
➤ YN0000: [@joplin/app-desktop]: > git add .
➤ YN0000: [@joplin/app-desktop]: > git config user.name "Build script"
➤ YN0000: [@joplin/app-desktop]: > git config user.email
➤ YN0000: [@joplin/app-desktop]: > git commit -m "Initial commit"
➤ YN0000: [@joplin/app-desktop]: error: Signing file /tmp/.git_signing_buffer_tmpS3jv5V
➤ YN0000: [@joplin/app-desktop]: Couldn't sign message (signer): agent refused operation?
➤ YN0000: [@joplin/app-desktop]: Signing /tmp/.git_signing_buffer_tmpS3jv5V failed: agent refused operation?
➤ YN0000: [@joplin/app-desktop]:
➤ YN0000: [@joplin/app-desktop]: fatal: failed to write commit object

masterkorp commented on 2024-04-08 08:25 (UTC)

hello @iyanmv build() does not access your keys in any way? Can you please explain more how is that accessing your system ?

iyanmv commented on 2024-04-08 01:13 (UTC)

Why does build() need to access my gpg private key?

brunofontes commented on 2024-04-01 12:21 (UTC)

Hello,

I went on this thread and tried to remove cache, then reinstalled the npm package. It worked for me.

phonemic commented on 2024-03-30 13:39 (UTC)

Getting this build error.

error This project's package.json defines "packageManager": "yarn@3.3.1". However the current global version of Yarn is 1.22.22.

Presence of the "packageManager" field indicates that the project is meant to be used with Corepack, a tool included by default with all official Node.js distributions starting from 16.9 and 14.19.
Corepack must currently be enabled by running corepack enable in your terminal. For more information, check out https://yarnpkg.com/corepack

proledatarian commented on 2024-03-26 23:20 (UTC)

Please either update the package or accept the help offered by @cuihao.

cuihao commented on 2024-03-18 22:41 (UTC)

Hi masterkorp, thank you for maintaining the package so far. I'm the maintainer of the joplin(-desktop) packages in the archlinuxcn repo. I have been using my version of PKGBUILD that at least builds so far with the latest version.

What do you think of using it? If you don't mind, I can help maintain the AUR package.

letscho commented on 2024-02-17 18:09 (UTC)

After installing this package I get this message: Cannot find /usr/share/joplin/node_modules/joplin/app/

I tried both sudo corepack enable and npm cache clean --force, but it didn't help.

In the folder /usr/share/joplin there is only: package.json package.tgz README.md yarn.lock