Arch Linux User Repository

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

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

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

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

Hello,

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

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

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

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.

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

I followed the suggestion of running sudo corepack enable but I have the habit of uninstalling build dependencies after building, so yarn was uninstalled. After I enabled corepack, installing yarn was failing because yarn already existed. I had to disable corepack, install yarn explicitly (yuck), and reenable corepack. then the build worked.

If the project can only be built with corepack, can we get rid of the build dependency on yarn? otherwise, is there a way to get yarn 3.3.1 globally? why is version from pacman 1.x?

I had the following error during joplin-desktop update:

  -> Installing package
{
  name: 'joplin',
  packageManager: 'yarn@3.3.1'
}
error This project's package.json defines "packageManager": "yarn@3.3.1". However the current global version of Yarn is 1.22.21.

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.

I successfully fixed the error by running:

$ sudo corepack enable