Package Details: ssb-patchwork 3.11.4-3

Git Clone URL: (read-only)
Package Base: ssb-patchwork
Description: A decentralized messaging and sharing app built on top of Secure Scuttlebutt (SSB)
Upstream URL:
Keywords: decentralized gossip network patchwork scuttlebutt ssb
Licenses: AGPL3
Submitter: dlandau
Maintainer: dlandau (pypper, christianbundy)
Last Packager: christianbundy
Votes: 13
Popularity: 0.165032
First Submitted: 2017-09-09 19:25
Last Updated: 2019-02-13 16:36

Latest Comments

1 2 3 4 Next › Last »

christianbundy commented on 2019-02-13 16:37

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

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

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: *** [ Release/] 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

@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

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:

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

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

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

Lazalatin commented on 2018-11-10 13:01

Hi, @christianbundy May you update the version to 3.11.4? It is the newest release on github:

Thank you :3

christianbundy commented on 2018-11-06 17:42

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

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.