AUR (en) - joplin

Search Criteria

Enter search criteria

Search by

Keywords

Out of Date

Sort by

Sort order

Per page

Package Details: joplin-desktop 3.0.14-1

Package Actions

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 - Desktop
Upstream URL:	https://joplinapp.org/
Keywords:	markdown note notetaking productivity
Licenses:	MIT
Groups:	joplin
Conflicts:	joplin-desktop-electron
Submitter:	masterkorp
Maintainer:	masterkorp
Last Packager:	masterkorp
Votes:	263
Popularity:	1.77
First Submitted:	2018-04-18 16:33 (UTC)
Last Updated:	2024-07-29 19:54 (UTC)

Dependencies (22)

electron (electron-bin^AUR)
gtk3 (gtk3-no_deadkeys_underline^AUR, gtk3-classic^AUR, gtk3-classic-xfce^AUR, gtk3-patched-filechooser-icon-view^AUR)
libexif (libexif-git^AUR)
libgsf (libgsf-git^AUR)
libjpeg-turbo (mozjpeg-git^AUR, libjpeg-turbo-git^AUR, mozjpeg^AUR)
libwebp (libwebp-git^AUR)
libxss
nodejs (nodejs-lts-fermium^AUR, nodejs-git^AUR, python-nodejs-wheel^AUR, nodejs-lts-hydrogen, nodejs-lts-iron)
nss (nss-hg^AUR)
orc
electron (electron-bin^AUR) (make)
git (git-git^AUR, git-gl^AUR) (make)
jq (jq-git^AUR) (make)
libgsf (libgsf-git^AUR) (make)
node-gyp (corepacker^AUR) (make)
npm (corepacker^AUR, python-nodejs-wheel^AUR) (make)
python (python37^AUR, python311^AUR, python310^AUR) (make)
python-setuptools (make)
rsync (rsync-git^AUR, rsync-reflink^AUR, rsync-reflink-git^AUR) (make)
yarn (yarn-pnpm-corepack^AUR, corepacker^AUR, yarn-berry^AUR) (make)
Show 2 more dependencies...

Required by (0)

Sources (4)

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

« First ‹ Previous 1 .. 8 9 10 11 12 13 14 15 16 17 18 .. 54 Next › Last »

karcher commented on 2022-01-09 11:07 (UTC)

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)

meyznu commented on 2022-01-08 08:21 (UTC)

You may need to remove your src/ folder before using this version

What is 'src/' folder? Where should I remove it from?

So far, I get this while trying to install this package:

Error: Cannot find module 'code-point-at'
Require stack:
- /usr/lib/node_modules/npm/node_modules/node-gyp/node_modules/string-width/index.js
- /usr/lib/node_modules/npm/node_modules/node-gyp/node_modules/gauge/wide-truncate.js
- /usr/lib/node_modules/npm/node_modules/node-gyp/node_modules/gauge/render-template.js
- /usr/lib/node_modules/npm/node_modules/node-gyp/node_modules/gauge/plumbing.js
- /usr/lib/node_modules/npm/node_modules/node-gyp/node_modules/gauge/index.js
- /usr/lib/node_modules/npm/node_modules/node-gyp/node_modules/npmlog/log.js
- /usr/lib/node_modules/npm/node_modules/node-gyp/lib/node-gyp.js
- /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)

strubbl commented on 2022-01-06 13:45 (UTC) (edited on 2022-01-06 13:46 (UTC) by strubbl)

Is there any upstream issue to follow already?

At the moment, i cannot click into the edit window of a note to add text.

edit: sorry, i only saw your pinned comments and thought that they were the most recent ones. but below them there are newer ones.

maderios commented on 2022-01-05 18:15 (UTC)

I got error

error electron-builder@22.14.5: The engine "node" is incompatible with this module. Expected version ">=14.0.0". Got "12.22.8"
error Found incompatible module.
lerna ERR! yarn install --mutex network:42424 --non-interactive --cache /home/fre/ARCH-AUR/joplin/src/npm-cache --no-optional exited 1 in '@joplin/app-desktop'
lerna WARN complete Waiting for 3 child processes to exit. CTRL-C to exit immediately.
error Command failed with exit code 1.

Rhinoceros commented on 2022-01-04 23:31 (UTC)

Like the others, I would also have preferred to install this instead of the appimage version.

I'm sorry you feel that way @masterkorp. I actually think it's a good thing that people are posting build issues here (although I think that issues with the application itself should be posted upstream). I think maintainers should be notified of build issues, even if the commenter is incapable of providing the solution.

However, if you feel unable to fix this package, then perhaps you could post upstream or in the Arch forum for help? If the PKGBUILD is broken, I would certainly not want to discourage people from posting here.

(Also, I noticed that you maintain three other packages, all of which have been flagged as out of date. One is 2 months out of date, and another is 14 months! The last should probably be deleted. No offence, but if you do feel overwhelmed by maintaining packages in general, perhaps it would be a good idea to disown them.)

jost21 commented on 2022-01-04 16:23 (UTC)

@masterkorp I understand your frustration. I hope you continue maintaining the package and I really appreciate the work and time you put into this. I prefer this over flatpak, AppImage etc. and also having the CLI client.

Darkmind2007 commented on 2022-01-04 14:43 (UTC)

To be honest, even though the AppImage provides a solution (I haven't tried it, just following the other comments), I must say that I'd personally consider it as the last resort.

My preference would be to have as little AppImage apps on my PC as possible, only for products that are too difficult to integrate with the system. Otherwise app management becomes too much MacOS style, which doesn't seem like Arch way of doing things.

Just to be clear, I didn't mean to complain about the package quality leaving the comment with the error message. It was just to provide some debug data or in case someone else has already faced the same problem.

I'd be happy to help if I had more experience with electron and JS.

masterkorp commented on 2022-01-04 14:15 (UTC) (edited on 2022-01-04 14:16 (UTC) by masterkorp)

@madjoe I only follow stable branches too, this is the cost of properly packaging stuff. That package is there if anyone needs it, but it does not provide the joppin cli client.

I honestly just want to disown this package, with some many people just demanding that stuff works out of the box, but they do not provide or help with any helpfull solution.

madjoe commented on 2022-01-04 11:48 (UTC)

@Rhinoceros: Too many issues with this package. I agree, joplin-appimage simply works and besides, it only follows stable branches, which is a plus.

Rhinoceros commented on 2022-01-03 22:29 (UTC) (edited on 2022-01-03 22:30 (UTC) by Rhinoceros)

For anyone else unable to build this package, joplin-appimage works well as a replacement to joplin-desktop.