Arch Linux User Repository

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

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

I noticed a comment in the PKGBUILD about electron breaking the interface (# FIXME: Using packaged electron breaks the interface on line 168). According to @masterkorp's pinned comment, the package is "usable and stable", so I wonder if the editor issues we're having might be because of different electron versions?

I've got electron16, electron13, and electron11 installed. I didn't check which one was used when the package was built, but I might rebuild and check. @maderios, @gwenlune, @Darkmind2007, what electon versions have you got installed?

Build needs nodejs 16, 'nodejs-lts-gallium'. Then, same issue with editor than other users. I don't think it's upstream bug because appimage version works fine.

Please remove --user root in PKGBUILD. Since npm 7, the --user option is no longer available. --user root not only doesn't fix the permission problem, but also installs the package called "root", which conflicts with other packages that also have the --user root option.

Yes, I'm having the same problems as @Darkmind2007, @gwenlune, and others -- at least the inability to edit and garbage in the editor. (I haven't used joplin much in the past day, so I don't know if lines from the editor are being rendered in the wrong area.)

I've assumed it was an upstream issue but haven't had a chance to look into it. I've also got joplin 2.6.10 installed on an Ubuntu 21.04 machine. I'm very busy today, but when I have some time I'll check if the same problems show up there -- that might help narrow down the problem.

same issue here, no solution found!

@thurisaz, thanks for the update! I managed to build and install the package. However, I seem to experience the same issues with the editor that other people were mentioning here:

• I cannot edit anything

• The lines from editor sometimes are rendered even outside of the editor area

• There's often garbage in the editor like "xxxxx"

Have you experienced the same issues? If so, did you manage to fix them?

Like several others posting here, I had trouble upgrading to 2.6.10. Since I've got it installed now, I wanted to share what worked for me in case that helps.

• The build initially failed with an error about lerna not building. I didn't save the exact error message, but it was similar to what @Darkmind2007 reported in this comment or what @zangoku reported in another comment. It turned out this was because I hadn't updated in a while. Updating my installation fixed the lerna-related error.

• However, the build still failed with an error about the version of node -- the same one @maderios has here. I had nodejs-lts-erbium installed, which provides version 12.22.8-1, as reported in the error message. Upgrading to a more recent version of nodejs is the solution, as the error message states. I upgraded to nodejs-lts-gallium (v. 16.13.1-1) and then the build worked fine, but according to the error message nodejs-lts-fermium (v. 14.18.2-1) should also provide a recent enough version.

In a nutshell, the build worked fine for me with:

1. pacman -Syu
2. pacman -S nodejs-lts-gallium
3. makepkg -Cs and respond yes to the prompt.

I hope that's helpful to someone. Thanks for the package, @masterkorp! I'm happier using this than an AppImage, and I appreciate the effort you've put in to maintain it.

For 2.6.10 you actually have to confirm the yarn.lock warning with the string "yes". "Y" or "y" is not sufficient here.

Hi,

I have removed the cache/yay/joplin/src folder and answered yes to the prompt, but the update is still failing:

Run `npm audit` for details.
  -> Rearranging directory tree
  -> Fixing Directories Permissions
  -> Removing References to $pkgdir
  -> Removing References to $srcdir
  -> Fixing Permissions set by npm
  -> Installing LICENSE
  -> Installing Startup Script
==> Tidying install...
  -> Removing libtool files...
  -> Purging unwanted files...
  -> Removing static library files...
  -> Stripping unneeded symbols from binaries and libraries...
strip: Unable to recognise the format of the input file `./usr/share/joplin/node_modules/aws-crt/dist/bin/linux-arm64/aws-crt-nodejs.node'
  -> Compressing man and info pages...
==> Checking for packaging issues...
==> WARNING: Package contains reference to $srcdir
usr/share/joplin/node_modules/sharp/build/config.gypi
==> WARNING: Package contains reference to $pkgdir
usr/share/joplin/node_modules/sharp/build/config.gypi
usr/share/joplin/node_modules/sharp/build/Makefile
usr/share/joplin/node_modules/node-gyp/gyp/pylib/gyp/generator/__init__.pyc
usr/share/joplin/node_modules/node-gyp/gyp/pylib/gyp/generator/make.pyc
usr/share/joplin/node_modules/node-gyp/gyp/pylib/gyp/__init__.pyc
usr/share/joplin/node_modules/node-gyp/gyp/pylib/gyp/input.pyc
usr/share/joplin/node_modules/node-gyp/gyp/pylib/gyp/common.pyc
usr/share/joplin/node_modules/node-gyp/gyp/pylib/gyp/simple_copy.pyc
usr/share/joplin/node_modules/node-gyp/gyp/pylib/gyp/xcode_emulation.pyc
==> Creating package "joplin"...
  -> Generating .PKGINFO file...
  -> Generating .BUILDINFO file...
  -> Adding install file...
  -> Generating .MTREE file...
  -> Compressing package...
==> Starting package_joplin-desktop()...
  -> Building Desktop with packaged Electron...
  -> Using Electron Version 16.0.6
yarn run v1.22.17
warning From Yarn 1.0 onwards, scripts don't require "--" for options to be forwarded. In a future version, any explicit "--" will be forwarded as-is to the scripts.
$ npm run electronRebuild && npx electron-builder --publish=never --linux --x64 --dir=dist/

> @joplin/app-desktop@2.6.10 electronRebuild
> gulp electronRebuild

[11:28:19] Using gulpfile ~/.cache/yay/joplin/src/joplin-2.6.10/packages/app-desktop/gulpfile.js
[11:28:19] Starting 'electronRebuild'...
Running: yarn run electron-rebuild --force-abi 89
[11:28:19] 'electronRebuild' errored after 251 ms
[11:28:19] RangeError [ERR_CHILD_PROCESS_STDIO_MAXBUFFER]: stdout maxBuffer length exceeded
    at new NodeError (node:internal/errors:371:5)
    at Socket.onChildStdout (node:child_process:459:14)
    at Socket.emit (node:events:390:28)
    at Socket.emit (node:domain:537:15)
    at addChunk (node:internal/streams/readable:324:12)
    at readableAddChunk (node:internal/streams/readable:293:11)
    at Socket.Readable.push (node:internal/streams/readable:234:10)
    at Pipe.onStreamRead (node:internal/stream_base_commons:190:23)
    at Pipe.callbackTrampoline (node:internal/async_hooks:130:17)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
==> ERROR: A failure occurred in package_joplin-desktop().
    Aborting...
 -> error making: joplin (joplin-desktop)