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

Hi, as of 1.0.233, joplin builds fine. The GUI works well. However, on launching the cli version, it throws this error:

internal/modules/cjs/loader.js:1033
  throw err;
  ^

Error: Cannot find module 'immer'
Require stack:
- /usr/share/joplin-cli/lib/services/ResourceEditWatcher/reducer.js
- /usr/share/joplin-cli/lib/reducer.js
- /usr/share/joplin-cli/lib/BaseApplication.js
- /usr/share/joplin-cli/app.js
- /usr/share/joplin-cli/main.js
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:1030:15)
    at Function.Module._load (internal/modules/cjs/loader.js:899:27)
    at Module.require (internal/modules/cjs/loader.js:1090:19)
    at require (internal/modules/cjs/helpers.js:75:18)
    at Object.<anonymous> (/usr/share/joplin-cli/lib/services/ResourceEditWatcher/reducer.js:3:17)
    at Module._compile (internal/modules/cjs/loader.js:1201:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1221:10)
    at Module.load (internal/modules/cjs/loader.js:1050:32)
    at Function.Module._load (internal/modules/cjs/loader.js:938:14)
    at Module.require (internal/modules/cjs/loader.js:1090:19) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/usr/share/joplin-cli/lib/services/ResourceEditWatcher/reducer.js',
    '/usr/share/joplin-cli/lib/reducer.js',
    '/usr/share/joplin-cli/lib/BaseApplication.js',
    '/usr/share/joplin-cli/app.js',
    '/usr/share/joplin-cli/main.js'
  ]
}

I would like to remmind that this package does not update to pre-releases

Can you copy the application icon to /usr/share/pixmaps/joplin.png and update the line 6 of the joplin.desktop to:

Icon=joplin

This will make it possible to customize it in icon themes.

Build as of June 15 is failing. Failure starts at

/bin/sh: pkg-config: command not found gyp: Call to 'pkg-config --cflags libsecret-1' returned exit status 127 while in binding.gyp. while trying to load binding.gyp

with multiple gyp ERR! following. For what its worth, I am running Manjaro.

It’s not Zemoose’s fault. To keep certain packages from breaking and bugs from arising, Joplin’s main team is locking in specific versions. The dependencies have gotten managed better than they used to be but the whole “use new libraries where able to save time and code maintenance” approach is a bit problematic at times.

I wouldn’t recommend updating most packages if you can avoid it because of this.

@ZeMoose, just to be on the safe side, you should periodically check for npm update and resolve those security vulnerabilities by running npm audit fix.

this version is very outdated. please do something

Hey, all. My name is Brandon and I'm a member of the Joplin Team. I'm not one of the core devs but instead primarily am focused on Linux support and research.

Here's my credentials on the Forums: https://discourse.joplinapp.org/g/Team

Here's my main contribution to the project so far: https://github.com/laurent22/joplin/issues/3114

@ZeMoose, the dependencies of Joplin do concern me quite a bit myself. I'd love to hear which ones concern you the most.

If confronted with a 'fatal error: unknown table: settings' it helped me to rm -rf ~/.config/Joplin/ ~/.config/joplin-desktop/ and reinstall joplin from the already compiled package.

Such was suggested here: https://discourse.joplinapp.org/t/solved-linux-fatal-error-unknown-table-settings/6253

Should I be concerned about the hundreds of low and moderate severity vulnerabilities reported by npm during the build process?