Package Details: ssb-patchwork 3.18.1-1

Git Clone URL: https://aur.archlinux.org/ssb-patchwork.git (read-only, click to copy)
Package Base: ssb-patchwork
Description: A decentralized messaging and sharing app built on top of Secure Scuttlebutt (SSB)
Upstream URL: https://github.com/ssbc/patchwork
Keywords: decentralized gossip network patchwork scuttlebutt ssb
Licenses: AGPL3
Submitter: dlandau
Maintainer: dlandau (pypper, christianbundy, zozs)
Last Packager: zozs
Votes: 20
Popularity: 0.49
First Submitted: 2017-09-09 19:25 (UTC)
Last Updated: 2021-04-11 20:05 (UTC)

Latest Comments

Tio commented on 2021-01-24 14:07 (UTC)

On Manjaro Gnome, the application's icon is the Electron icon and it is named "Electron". Any way to fix this? Or is this an upstream issue?

ekangmonyet commented on 2021-01-11 05:50 (UTC)

For Error 403 when downloading node headers from https://atom.io/download/electron/ , it worked for me by replacing L41 with: export npm_config_disturl=https://nodejs.org/dist

DianaNites commented on 2021-01-11 02:21 (UTC) (edited on 2021-01-11 02:21 (UTC) by DianaNites)

Build fails for me. Attempting install with yay

> @felixrieseberg/spellchecker@4.0.12 install /home/diana/.cache/yay/ssb-patchwork/src/patchwork-3.18.0/node_modules/@felixrieseberg/spellchecker
> node-gyp rebuild

gyp ERR! configure error 
gyp ERR! stack Error: Invalid version number: "v6.1.12\nWINDOW DECORATIONS RELOADED\nWINDOW DECORATIONS RELOADED"
gyp ERR! stack     at getNodeDir (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:56:25)
gyp ERR! stack     at /usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:30:7
gyp ERR! stack     at processTicksAndRejections (node:internal/process/task_queues:75:11)
gyp ERR! System Linux 5.10.3-arch1-1
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/diana/.cache/yay/ssb-patchwork/src/patchwork-3.18.0/node_modules/@felixrieseberg/spellchecker
gyp ERR! node -v v15.5.1
gyp ERR! node-gyp -v v5.1.0
gyp ERR! not ok 
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @felixrieseberg/spellchecker@4.0.12 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the @felixrieseberg/spellchecker@4.0.12 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/diana/.electron-gyp/.npm/_logs/2021-01-11T02_18_30_843Z-debug.log
==> ERROR: A failure occurred in build().
    Aborting...
error making: ssb-patchwork

kode54 commented on 2020-02-20 07:45 (UTC)

Oh, that's bloody stupid. It builds just fine if I run it under a terminal emulator from a graphical desktop. It only fails if I attempt to update my system from a TTY.

kode54 commented on 2020-02-19 22:51 (UTC)

This is the link that fails to retrieve when I attempt to build it:

https://atom.io/download/electron/v13.8.0/node-v13.8.0-headers.tar.gz

It reports error 403, access denied.

danievdm commented on 2020-02-19 11:56 (UTC) (edited on 2020-02-19 12:43 (UTC) by danievdm)

Latest update installed OK for me on Manjaro KDE but one odd thing is happening:

Whenever I paste a link URL in my post the post preview never comes up - just hangs. Other markdown characters or plain text work as per normal. Anyone else having this issue with links being pasted in?

It was working fine before the latest update on v3.17.2-2. I retested with both versions of the AppImage with identical post - worked on older version, did not work on latest version 3.17.3.

Issue is being tracked now at https://github.com/ssbc/patchwork/issues/1248 as I'm not the only one.

zozs commented on 2020-02-19 09:38 (UTC)

kode54: anything that can be done on the PKGBUILD side? I can build it on several of my local machines :/

kode54 commented on 2020-02-19 05:17 (UTC)

Latest is not buildable due to npm build bots being a piece of crap and failing to provide either a working copy of node 13.8.0 headers, or a copy of npm which can fall back on 403 errors.

christianbundy commented on 2020-01-06 21:07 (UTC)

zozs: Thanks, just pushed a new release to resolve that problem. I've also contacted dlandau to ask to have you added as a maintainer. Really appreciate your attention to detail on that dep!

zozs commented on 2020-01-04 09:47 (UTC)

gconf has been removed from the main repos, and only exists in AUR now. However, electron does not seem to depend on gconf anymore [1], so I think it can be removed from the depends array completely (this also means one less package depending on python2 :) ).

I removed it from depends and recompiled the package, and it seems to be working for me for the past hour or so.

[1] https://github.com/electron/electron/issues/2727

christianbundy commented on 2019-11-28 16:28 (UTC)

zozs: Oops, thanks for the comment, I've just pushed a fix. Please let me know if this gives you any trouble!

zozs commented on 2019-11-27 20:22 (UTC)

There seems to be some errors regarding the required version of electron. The depends=() array contains electron6, while the build() function, as well as /usr/bin/ssb-patchwork (i.e. run.sh) contains electron4, causing the build to fail (or /usr/bin/ssb-patchwork to not run) if electron4 not happens to be installed on the system by sheer luck.

Everything works if all instances of electron4 is replaced with electron6.

dhole commented on 2019-11-06 19:55 (UTC)

Running v3.16.2 failed on my Arch Linux due to a missing npm dependency: "ssb-caps". Here's the diff of the changes that I made to add the missing dependency (which seems to be missing from upstream):

diff --git a/PKGBUILD b/PKGBUILD
index 9961cbc..9b3def3 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -4,7 +4,7 @@
 pkgname=ssb-patchwork
 _upstream=patchwork
 pkgver=3.16.2
-pkgrel=1
+pkgrel=2
 pkgdesc="A decentralized messaging and sharing app built on top of Secure Scuttlebutt (SSB)"
 arch=('i686' 'x86_64')
 url="https://github.com/ssbc/patchwork"
@@ -16,12 +16,14 @@ source=(
 "https://github.com/ssbc/${_upstream}/archive/v${pkgver}.tar.gz"
 'run.sh'
 "${pkgname}.desktop"
+"missing-dependency.patch"
 )

 sha256sums=(
 '7bf634bbc56fbd3db18efa8ac8bcbdfa348520944c481dfc1d08c0f35eb30881'
 '5db66d7942606df5f48ea0db2d90b584fa3a984bc2de7bb678d25897f64e3a2f'
 'b226436970db40030ad03e9cd847c103aa534d775cd81212308e86a23917d76a'
+'SKIP'
 )


@@ -31,6 +33,7 @@ build() {
     # Remove postinstall script that rebuilds for Electron
     # Instead we just build correctly the first time
     sed -i '/postinstall/d' package.json
+    patch -Np0 -i "${srcdir}/missing-dependency.patch"

     # Electron's version.
     export npm_config_target=$(electron4 -v)
diff --git a/missing-dependency.patch b/missing-dependency.patch
new file mode 100644
index 0000000..bc0bd24
--- /dev/null
+++ b/missing-dependency.patch
@@ -0,0 +1,10 @@
+--- package.json.orig  2019-11-06 20:14:28.542628997 +0100
++++ package.json       2019-11-06 20:15:04.316149411 +0100
+@@ -70,6 +70,7 @@
+     "ssb-backlinks": "^0.7.3",
+     "ssb-blob-files": "^1.1.6",
+     "ssb-blobs": "^1.2.2",
++    "ssb-caps": "^1.1.0",
+     "ssb-client": "^4.7.8",
+     "ssb-config": "github:ssbc/ssb-config#auto-config-incoming",
+     "ssb-db": "^19.3.0",

beroal commented on 2019-06-05 10:08 (UTC) (edited on 2019-06-05 10:08 (UTC) by beroal)

"env" does not output any variable name containing "NODE". Sorry, I know nothing about Node.js, Electron, or NPM, so probably, I am doing something wrong. Should we move this discussion to the forums? BTW, should this package depend on "electron" or "electron2"? "PKGBUILD" is running the "electron" command which the "electron2" package does not contain. Versions:

electron 4.1.4-1
electron2 2.0.18-1
node-gyp 4.0.0-1
nodejs 11.15.0-1
npm 6.9.0-1

christianbundy commented on 2019-06-05 01:25 (UTC)

@beroal: Sorry to hear you're having a rough time trying to get this installed. Could you check the output of env and ensure you don't have any NODE_ options set? The PKGBUILD should be setting a different Node version (to target Electron) and I don't think it should be trying to download headers for Node.js 11.15.0 at all.

beroal commented on 2019-06-04 22:15 (UTC)

@Powersource I tried to build in a clean directory. The same error.

Powersource commented on 2019-06-04 21:56 (UTC)

@beroal It "works for me". Could you try clearing that build dir, downloading & installing stuff again, and see if it works then?

beroal commented on 2019-06-04 18:38 (UTC)

I can't compile this.

==> Making package: ssb-patchwork 3.12.0-1 (Tue 04 Jun 2019 09:37:18 PM EEST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found v3.12.0.tar.gz
  -> Found run.sh
  -> Found ssb-patchwork.desktop
==> Validating source files with sha512sums...
    v3.12.0.tar.gz ... Passed
    run.sh ... Passed
    ssb-patchwork.desktop ... Passed
==> Extracting sources...
  -> Extracting v3.12.0.tar.gz with bsdtar
==> Removing existing $pkgdir/ directory...
==> Starting build()...

(electron:28977): Gtk-WARNING **: 21:37:18.739: cannot open display:

> @felixrieseberg/spellchecker@4.0.8 install /var/abs/local/ssb-patchwork/src/patchwork-3.12.0/node_modules/@felixrieseberg/spellchecker > node-gyp rebuild

gyp WARN install got an error, rolling back install gyp ERR! configure error gyp ERR! stack Error: 404 response downloading https://atom.io/download/electron/v11.15.0/node-v11.15.0-headers.tar.gz gyp ERR! stack at Request.<anonymous> (/usr/lib/node_modules/node-gyp/lib/install.js:204:14) gyp ERR! stack at Request.emit (events.js:198:15) gyp ERR! stack at Request.onRequestResponse (/usr/lib/node_modules/node-gyp/node_modules/request/request.js:1066:10) gyp ERR! stack at ClientRequest.emit (events.js:193:13) gyp ERR! stack at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:560:23) gyp ERR! stack at HTTPParser.parserOnHeadersComplete (_http_common.js:113:17) gyp ERR! stack at TLSSocket.socketOnData (_http_client.js:447:22) gyp ERR! stack at TLSSocket.emit (events.js:193:13) gyp ERR! stack at addChunk (_stream_readable.js:295:12) gyp ERR! stack at readableAddChunk (_stream_readable.js:276:11) gyp ERR! System Linux 5.1.6-arch1-1-ARCH gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/node-gyp/bin/node-gyp.js" "rebuild" gyp ERR! cwd /var/abs/local/ssb-patchwork/src/patchwork-3.12.0/node_modules/@felixrieseberg/spellchecker gyp ERR! node -v v11.15.0 gyp ERR! node-gyp -v v4.0.0 gyp ERR! not ok npm WARN acorn-dynamic-import@4.0.0 requires a peer of acorn@^6.0.0 but none is installed. You must install peer dependencies yourself. npm WARN acorn-jsx@5.0.1 requires a peer of acorn@^6.0.0 but none is installed. You must install peer dependencies yourself. npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! @felixrieseberg/spellchecker@4.0.8 install: node-gyp rebuild npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the @felixrieseberg/spellchecker@4.0.8 install script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in: npm ERR! /home/compile/.electron-gyp/.npm/_logs/2019-06-04T18_37_30_087Z-debug.log ==> ERROR: A failure occurred in build(). Aborting...

makeworld commented on 2019-03-18 00:34 (UTC)

Error installing with the new update:

In file included from /home/makeworld/.node-gyp/iojs-2.0.18/src/node.h:63,
                 from ../binding.cc:1:
/home/makeworld/.node-gyp/iojs-2.0.18/deps/v8/include/v8.h: In instantiation of ‘void v8::PersistentBase<T>::SetWeak(P*, typename v8::WeakCallbackInfo<P>::Callback, v8::WeakCallbackType) [with P = node::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo<P>::Callback = void (*)(const v8::WeakCallbackInfo<node::ObjectWrap>&)]’:
/home/makeworld/.node-gyp/iojs-2.0.18/src/node_object_wrap.h:85:78:   required from here
/home/makeworld/.node-gyp/iojs-2.0.18/deps/v8/include/v8.h:9199:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfo<node::ObjectWrap>::Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<node::ObjectWrap>&)’} to ‘Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<void>&)’} [-Wcast-function-type]
                reinterpret_cast<Callback>(callback), type);
                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/makeworld/.node-gyp/iojs-2.0.18/deps/v8/include/v8.h: In instantiation of ‘void v8::PersistentBase<T>::SetWeak(P*, typename v8::WeakCallbackInfo<P>::Callback, v8::WeakCallbackType) [with P = Nan::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo<P>::Callback = void (*)(const v8::WeakCallbackInfo<Nan::ObjectWrap>&)]’:
../../nan/nan_object_wrap.h:66:61:   required from here
/home/makeworld/.node-gyp/iojs-2.0.18/deps/v8/include/v8.h:9199:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfo<Nan::ObjectWrap>::Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<Nan::ObjectWrap>&)’} to ‘Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<void>&)’} [-Wcast-function-type]
make: *** [sodium.target.mk:117: Release/obj.target/sodium/binding.o] Error 1
make: Leaving directory '/home/makeworld/.cache/yay/ssb-patchwork/src/patchwork-3.11.5/node_modules/sodium-native/build'
gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/node-gyp/lib/build.js:262:23)
gyp ERR! stack     at ChildProcess.emit (events.js:197:13)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:254:12)
gyp ERR! System Linux 5.0.0-arch1-1-ARCH
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/makeworld/.cache/yay/ssb-patchwork/src/patchwork-3.11.5/node_modules/sodium-native
gyp ERR! node -v v11.12.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok 
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! sodium-native@2.2.2 install: `node-gyp-build "node preinstall.js" "node postinstall.js"`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the sodium-native@2.2.2 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/makeworld/.npm/_logs/2019-03-18T00_30_07_658Z-debug.log
==> ERROR: A failure occurred in build().
    Aborting...
Error making: ssb-patchwork

christianbundy commented on 2019-02-13 16:37 (UTC)

Nevermind, it looks like I was using a Node LTS whereas you two were most likely using nodejs latest. I've pushed a fix that just installs for the Electron version, whereas previously we were installing for your current Node version and then rebuilding for the Electron version.

christianbundy commented on 2019-02-13 16:09 (UTC)

xanc and kode54: could you give some more information about your system? For example, could you verify that you're 100% up-to-date with pacman -Syu and let me know which versions of nodejs/npm you're using? I'd love to help debug these issues.

xanc commented on 2019-02-13 13:26 (UTC)

During build process, I get an error:

../../../../nan/nan_object_wrap.h:66:61: required from here /home/xan/.node-gyp/iojs-2.0.17/deps/v8/include/v8.h:9199:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfo<Nan::ObjectWrap>::Callback’ {aka ‘void ()(const v8::WeakCallbackInfo<Nan::ObjectWrap>&)’} to ‘Callback’ {aka ‘void ()(const v8::WeakCallbackInfo<void>&)’} [-Wcast-function-type] make: *** [sodium.target.mk:117: Release/obj.target/sodium/binding.o] Error 1 make: Leaving directory '/home/xan/aur/patchwork-scuttlebutt/ssb-patchwork/src/patchwork-3.11.4/node_modules/private-box/node_modules/sodium-native/build' gyp ERR! build error gyp ERR! stack Error: make failed with exit code: 2 gyp ERR! stack at ChildProcess.onExit (/usr/lib/node_modules/node-gyp/lib/build.js:262:23) gyp ERR! stack at ChildProcess.emit (events.js:197:13) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:254:12) gyp ERR! System Linux 4.19.20-1-lts gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/node-gyp/bin/node-gyp.js" "rebuild" gyp ERR! cwd /home/xan/aur/patchwork-scuttlebutt/ssb-patchwork/src/patchwork-3.11.4/node_modules/private-box/node_modules/sodium-native gyp ERR! node -v v11.9.0 gyp ERR! node-gyp -v v3.8.0 gyp ERR! not ok npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! sodium-native@2.2.2 install: node-gyp-build "node preinstall.js" "node postinstall.js" npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the sodium-native@2.2.2 install script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in: npm ERR! /home/xan/.npm/_logs/2019-02-13T13_25_17_583Z-debug.log ==> ERROR: S'ha produït un error a build(). Cancel·lant...

makeworld commented on 2019-01-22 02:24 (UTC)

@christianbundy @dlandau could you update the package to replace the some files with the work @kode54 has done? Thanks.

kode54 commented on 2019-01-14 03:21 (UTC) (edited on 2019-01-14 03:27 (UTC) by kode54)

I found the issue. Upstream needs to refresh their bloody package-lock.json. I refreshed my own using npm install, and it built just fine. It also looks like they were frozen (^) on v2.0.0 of sodium-native, and not the latest, 2.1.6. I could report this upstream, but I doubt they'll fix it in both git master and in the 3.11.4 tag.

For now, a workaround is to add a prepare step, or extra build steps, which rm the package-lock.json, and regenerate it with npm install, or replace it with a copy I'll upload to a gist for you:

https://gist.github.com/kode54/c5716af59ea979f6ef590598ebd09229

Incidentally, this isn't the first time I've encountered a Scuttlebutt related project where the package-lock.json being horribly out of date caused a build time breakage on one of my systems.

And sorry, it wasn't node-gyp, that was just what successfully built when it reached the error: sodium-native was pinned on 2.0.0 by package-lock, so it was failing to build that now that libsodium is up to 1.0.17 as of 7 Jan 2019.

Do be sure to read over the diff between the official and my file, first, of course, never know if someone may pull a trick like this to get their own special trojan horse embedded in a project.

christianbundy commented on 2019-01-13 22:55 (UTC)

kode54: Sorry that this is causing problems for you. Could you post the errors you're seeing? Also, if you're using any package variants (e.g. nodejs-lts-boron) please include that as well so that we can identify the incompatibility.

kode54 commented on 2019-01-13 22:47 (UTC)

This now fails to build with a whole mess of errors about node-gyp.

Lazalatin commented on 2018-11-10 13:01 (UTC)

Hi, @christianbundy May you update the version to 3.11.4? It is the newest release on github: https://github.com/ssbc/patchwork/releases/tag/v3.11.4

Thank you :3

christianbundy commented on 2018-11-06 17:42 (UTC)

Thanks @GergelyPolonKai, I've just pushed a new version -- could you let me know if the new version works better for you? Good luck!

GergelyPolonkai commented on 2018-11-06 08:09 (UTC)

As of version 3.11.3-1 I Patchwork fails to start:

Error: Cannot find module '@paulcbetts/spellchecker'
    at Module._resolveFilename (module.js:543:15)
    at Function.Module._resolveFilename (/usr/lib/electron/resources/electron.asar/common/reset-search-paths.js:35:12)
    at Function.Module._load (module.js:473:25)
    at Module.require (module.js:586:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/opt/ssb-patchwork/node_modules/electron-spellchecker/lib/node-spellchecker.js:8:18)
    at Object.<anonymous> (/opt/ssb-patchwork/node_modules/electron-spellchecker/lib/node-spellchecker.js:9:3)
    at Module._compile (module.js:642:30)
    at Object.Module._extensions..js (module.js:653:10)
    at Module.load (module.js:561:32)

I saw this module mentioned in a few SSB posts, but no real solution.

christianbundy commented on 2018-09-27 15:26 (UTC)

Oops, accidentally deleted my comment. Sorry about that.

TL;DR: as long as NPM is up-to-date you should be able to run npm ci. If there are compatibility issues, let me know and I can see about adding a fallback for older versions of NPM. Good luck!

Blaiz0r commented on 2018-09-03 21:07 (UTC)

Line 30 in the PKGBUILD didn't work for me:

npm ci --only=production

I had to separate the c and the i and reverse them.

christianbundy commented on 2018-05-30 18:33 (UTC)

Stephen304: Please read the most recent comments (just below your post).

Patchwork 3.9.0 requires Node.js < 10 as a build dependency (makedepends), but once it's installed you can reinstall nodejs as it isn't required as a runtime dependency.

Stephen304 commented on 2018-05-30 18:27 (UTC) (edited on 2018-05-30 18:28 (UTC) by Stephen304)

Is there any specific reason why this depends on nodejs-lts-carbon now? I have atom installed, which depends on nodejs, so I am failing to update to 3.9.0-3 since the nodejs-lts-carbon conflicts with my currently installed nodejs from atom.

:: The following 1 package(s) are getting installed:
   community/nodejs-lts-carbon  /         ->  8.11.2-1

:: The following 1 package(s) are getting updated:
   aur/ssb-patchwork            3.8.10-1  ->  3.9.0-3

:: The following 3 package(s) are getting removed:
   community/apm                1.19.0-6  ->  /
   community/atom               1.27.1-1  ->  /
   community/nodejs             10.3.0-1  ->  /
:: Package nodejs will be removed due to a conflict with nodejs-lts-carbon
:: Dependency nodejs>=10 of package apm is not fulfilled
:: Dependency apm of package atom is not fulfilled

christianbundy commented on 2018-05-07 00:09 (UTC)

Shywim: My "relative confidence" ended up being completely backward, you were right! I've just pushed a new commit to move nodejs-lts-carbon and npm to makedepends, and after about 30 minutes of paranoid testing I can't find any reason not to do this. Thanks for the suggestion!

christianbundy commented on 2018-05-06 15:13 (UTC)

Shywim: I'm relatively confident that nodejs is required at runtime because it ends up hosting an sbot (https://github.com/ssbc/scuttlebot/) server in the background.

I'm working on bringing all of the Patchwork dependencies up-to-date (https://github.com/ssbc/patchwork/pull/789) to support Node 10, but it will likely take a few more days to wrap up all of the loose ends. Thanks for your patience!

Shywim commented on 2018-05-06 09:30 (UTC)

Is nodejs required for runtime? If not, please use makedepends for nodejs as I need the latest version of node of my machine, and I can't have nodejs and nodejs-lts-carbon side by side.

dlandau commented on 2018-04-29 20:44 (UTC)

Ok, got it to a working state. It's not ideal by a long shot, but at least it functions now.

dlandau commented on 2018-04-29 19:17 (UTC)

Uh, this package is broken by upstream(s) right now.

@Plexcon: That error is this one: https://github.com/npm/npm/issues/19989. Using npm ci instead of npm install gets through that, but then we have the next problem.

On node 10, there's this issue in a dependency https://github.com/Level/leveldown/issues/455.

@k3a: see christianbundy's comment. NPM has introduced package-lock.json since then, a file that lists all the exact dependencies and npm ci install exactly those. Using sed to get rid of the electron dependency in package.json is doable, but I'm not sure if doing same to package-lock.json would make any sense as that file is not meant to be human editable.

I tried to update the PKGBUILD to depend on older versions of node and npm from the AUR, which is highly unideal as this forces the removal of the packages from community. This didn't turn out to solve the problem as there's some error message about node-abi and trying to bypass that lead to Patchwork installing, but failing to launch with a message about NODE_MODULE_VERSION (unsurprising, as node-abi was being used for working with that as far as I could tell).

End result is no working package at the moment. I'll try to get it fixed asap, but it might require upstream to do something.

christianbundy commented on 2018-04-27 20:30 (UTC)

k3a: https://lists.archlinux.org/pipermail/aur-general/2014-September/029526.html

k3a commented on 2018-04-27 17:48 (UTC) (edited on 2018-04-27 18:35 (UTC) by k3a)

Is there any reason to use nodejs blob of electron instead of using a system one? https://www.archlinux.org/packages/community/x86_64/electron/ I can confirm it works just fine with the system one.

cole128: You can manually download a snapshot and edit the version in the meantime ;) Hopefully it's not abandoned.

makeworld commented on 2018-04-27 00:50 (UTC)

Will this be updated for new releases, or is it abandoned?

christianbundy commented on 2018-04-23 15:53 (UTC) (edited on 2018-04-23 15:54 (UTC) by christianbundy)

For folks who are itching for v3.9.0, here's the diff:

diff --git a/PKGBUILD b/PKGBUILD
index f33dafa..8b8204e 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -3,7 +3,7 @@

 pkgname=ssb-patchwork
 _upstream=patchwork
-pkgver=3.8.10
+pkgver=3.9.0
 pkgrel=1
 pkgdesc="A decentralized messaging and sharing app built on top of Secure Scuttlebutt (SSB)"
 arch=('i686' 'x86_64')
@@ -16,7 +16,7 @@ source=(
 'run.sh'
 "${pkgname}.desktop"
 )
-md5sums=('9325b924b3f3ecc9dbaddce1a3d88ad2'
+md5sums=('2036001984b4d904cac87ac452ebfa66'
          'bb315f14e6d7ef57976c8934ddad4fd9'
          '3c73b5245f2da7dd2e31729e2b57ad37')

Just makepkg -si and you're good to go.

Plexcon commented on 2018-04-17 15:00 (UTC) (edited on 2018-04-17 15:05 (UTC) by Plexcon)

-> Extrayendo v3.8.10.tar.gz con bsdtar ==> Iniciando build()... npm ERR! code ERR_STREAM_WRITE_AFTER_END npm ERR! write after end

npm ERR! A complete log of this run can be found in: npm ERR! /home/manjaro/.npm/_logs/2018-04-17T14_52_51_136Z-debug.log ==> ERROR: Se produjo un fallo en build(). Cancelando...

Pastebin: https://paste.ee/p/LtisZ http://pasted.co/25574889

pypper commented on 2018-03-15 01:33 (UTC)

@Powersource: this was added in the latest release.

Powersource commented on 2018-02-20 13:29 (UTC)

Could you please make it pass along arguments when running from the command line?

pypper commented on 2018-02-04 05:33 (UTC)

hotice, added that for you and re-released as a pkgver increment.

let me know if its working better.

hotice commented on 2018-01-25 13:02 (UTC)

Also, please add ;Network; to Categories in desktop file as otherwise it's hidden under Lost & Found in KDE app menu.

hotice commented on 2018-01-25 11:56 (UTC) (edited on 2018-01-25 14:45 (UTC) by hotice)

Error dialog "An error occurred while attempting to redeem invite. could not connect to sbot". Also, sbot command isn't available from console. $ npm doctor

npm ERR! checkFilePermissions Missing permissions on /opt/ssb-patchwork/node_modules Check Value Recommendation npm ping OK npm -v v5.6.0 node -v v9.4.0 npm config get registry https://registry.npmjs.org/ which git /usr/bin/git Perms check on cached files ok Perms check on global node_modules ok Perms check on local node_modules notOk /opt/ssb-patchwork/node_modules must be readable and writable by the current user.

EDIT: Even with chmod 777 on node_modules and clean npm doctor report the error persists. What might be the reason?

pypper commented on 2017-11-17 14:05 (UTC)

thanks, pushed!

dlandau commented on 2017-11-17 12:43 (UTC)

I added you as co-maintainer, feel free to push.

pypper commented on 2017-11-16 18:00 (UTC)

tested and running 3.7.1 in my fork here: https://notabug.org/pypper/aur-ssb-patchwork/commit/aff22869bba48d7ff5e591db8bbddeb5bf6a5420 if you want to pull it in / reduce your effort