Arch Linux User Repository

v3.4.3 was just released on the upstream and removes the need for the workaround fix in the current PKGBUILD. I updated the package accordingly.

Please let me know if problems pop up on your side.

Cheers, FillFeile

News regarding the upstream issue: The devs promised to release a hotfix version v3.4.3 later this week (https://github.com/standardnotes/desktop/issues/598#issuecomment-688156025). After that I will cleanup the PKGBUILD and remove the current workaround patch.

Hi all, sorry for the inconvienence caused. Sadly the error was not cause by the new PKBUILD. Version 3.4.2 is bricked on upstream as you can see here: https://github.com/standardnotes/desktop/issues/598

My local tests ran trough cause somehow my local npm cache must have provided a version of a subpart that is not available anymore. I switched the PKGBUILD to use a temporary npm cache for the future so this will not happen again.

The current packaged version uses a slightly older subpart version for standard-notes-web (the one from version 3.4.1). This is not completly clean but the app seams to work anyways. I will bump the upstream issue to get this fixed as soon as possible. If you want to help I would kindly ask you to upvote the linked github issue.

Also seeing the same error as Lanthanus Attempting to upgrade from 3.4.1

Tried with yay and cloning the repository directly and running makepkg -si with same results.

Unfortunately it stopped with an error. Seems to be a problem with the postinstall script.

> electron-builder install-app-deps
  • electron-builder  version=22.6.0
  • loaded configuration  file=package.json ("build" field)
  • installing production dependencies  platform=linux arch=x64 appDir=/var/tmp/pamac-build-user/standardnotes-desktop/src/desktop/app
  ⨯ /usr/bin/node exited with code ERR_ELECTRON_BUILDER_CANNOT_EXECUTE
Error output:
Error output:
npm WARN standard-notes@3.4.2 No repository field.
npm WARN standard-notes@3.4.2 No license field.
npm ERR! code 128
npm ERR! Command failed: git checkout 8a0b0c972f41e131f542ad18cc7bd547cb1aa4be
npm ERR! fatal: Referenz ist kein "Tree"-Objekt: 8a0b0c972f41e131f542ad18cc7bd547cb1aa4be
npm ERR!
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/user/.npm/_logs/2020-09-06T09_53_26_617Z-debug.log
  stackTrace=
Error: /usr/bin/node exited with code ERR_ELECTRON_BUILDER_CANNOT_EXECUTE
Error output:
Error output:
npm WARN standard-notes@3.4.2 No repository field.
npm WARN standard-notes@3.4.2 No license field.
npm ERR! code 128
npm ERR! Command failed: git checkout 8a0b0c972f41e131f542ad18cc7bd547cb1aa4be
npm ERR! fatal: Referenz ist kein "Tree"-Objekt: 8a0b0c972f41e131f542ad18cc7bd547cb1aa4be
npm ERR! 
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/user/.npm/_logs/2020-09-06T09_53_26_617Z-debug.log
at ChildProcess.<anonymous> (/var/tmp/pamac-build-user/standardnotes-desktop/src/desktop/node_modules/builder-util/src/util.ts:243:14)
at Object.onceWrapper (events.js:421:26)
at ChildProcess.emit (events.js:314:20)
at maybeClose (internal/child_process.js:1051:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! standard-notes@3.4.2 postinstall: `electron-builder install-app-deps`
npm ERR! Exit status 1
npm ERR! 

As promised the new verison is packaged and uploaded. I hope the update runs smooth for everyone. The PKGBUILD now uses electron-builder, as the upstream does, to build the app.

Sorry again for the delay!

Cheers, FillFeile

Thanks @FillFeile for the update!

Hi all, sorry for the delay with the recent update. I will continue to maintain this PKGBUILD but the latest update was delayed for two main reasons. I faced some time constrains on my side + Standard Notes (again) changed their build toolchain which broke the current PKGBUILD. The upstream package.json doesn't contain a build script for the plain linux "dir" target anymore. I'm currently working on a patched version that hopefully will arrive tomorrow. Thank you for your patience, I will keep you updated!

Hello, this has been flagged out of date for some time. Is nobody maintaining this PKGBUILD any longer?

@vyachkonovalov - thanks a lot for the heads up! You're totally right. Fixed this with 3.4.1-2.