Package Details: abricotine 0.3.3-1

Git Clone URL: https://aur.archlinux.org/abricotine.git (read-only)
Package Base: abricotine
Description: A markdown editor with inline preview
Upstream URL: http://abricotine.brrd.fr
Licenses: GPL3
Submitter: heddson
Maintainer: heddson
Last Packager: heddson
Votes: 5
Popularity: 0.725274
First Submitted: 2016-02-24 09:47
Last Updated: 2016-07-02 23:46

Dependencies (1)

Required by (0)

Sources (2)

Latest Comments

z3ntu commented on 2016-07-08 08:32

python2 is a (build) dependency!

gyp ERR! configure error
gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable.
gyp ERR! stack at failNoPython (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:449:14)
gyp ERR! stack at /usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:353:11
gyp ERR! stack at F (/usr/lib/node_modules/npm/node_modules/which/which.js:69:16)
gyp ERR! stack at E (/usr/lib/node_modules/npm/node_modules/which/which.js:81:29)
gyp ERR! stack at /usr/lib/node_modules/npm/node_modules/which/which.js:90:16
gyp ERR! stack at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/index.js:44:5
gyp ERR! stack at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/access.js:8:5
gyp ERR! stack at FSReqWrap.oncomplete (fs.js:123:15)

EDIT: After manually installing python2 (NOT python(3)!) I get the error in a completely clean chroot (where every build should work): http://pastebin.com/4htppbXX
See https://github.com/brrd/Abricotine/issues/63#issuecomment-231308863 for more info.

EDIT 2: I have found a workaround for now! Install https://aur.archlinux.org/packages/nodejs-electron-rebuild/ (or "npm install -g electron-rebuild") and build this!

heddson commented on 2016-07-02 23:34

JohnRobson: Sorry I can't reproduce your issue. I'm running npm v3.10.3 and Linux 4.6.2-1-ARCH, but don't know if that makes any difference..

Abricotine just updated to 0.3.3, maybe that works for you.

JohnRobson commented on 2016-07-02 12:06

npm ERR! Linux 4.6.3-1-ARCH
npm ERR! argv "/usr/bin/node" "/sbin/npm" "install"
npm ERR! node v6.2.2
npm ERR! npm v3.10.2
npm ERR! code ELIFECYCLE

npm ERR! nslog@3.0.0 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the nslog@3.0.0 install script 'node-gyp rebuild'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the nslog package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs nslog
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls nslog
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! /tmp/yaourt-tmp-us/aur-abricotine/src/Abricotine-0.3.2/npm-debug.log
==> ERROR: A failure occurred in build().
Aborting...
==> ERROR: Makepkg was unable to build abricotine.

z3ntu commented on 2016-05-02 20:15

Builds now for me. Weird... EDIT: Maybe the /tmp partition was too small on my server and I expanded it... But probably not...

j1simon commented on 2016-04-14 10:33

It's solved to me but I have done so many things that I don't know what was really the problem. More info in issue: https://github.com/brrd/Abricotine/issues/63

heddson commented on 2016-04-14 08:20

z3ntu: I compaired your installed pkgs with mine. We have a lot of different pkgs and I couldn't figure out if we have some missing dependencies.. You should try and see if you're able to install from source (without the PKGBUILD), just like j1simon did.

j1simon: Great that you opened an issue! Hopefully we'll see we're missing a dependency or maybe if it's a permission issue.

j1simon commented on 2016-04-13 13:03

The problem occurs too when I try to install the git version from sources. I have opened a issue: https://github.com/brrd/Abricotine/issues/63

j1simon commented on 2016-04-13 12:24

Same problem:
.....
> Abricotine@0.3.2 postinstall /home/juan/bin/nodejs/lib/node_modules/Abricotine
> electron-rebuild && bower install

sh: electron-rebuild: command not found
npm ERR! Linux 4.4.7-1-ck
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install"
npm ERR! node v5.10.1
npm ERR! npm v3.8.6
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn

npm ERR! Abricotine@0.3.2 postinstall: `electron-rebuild && bower install`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the Abricotine@0.3.2 postinstall script 'electron-rebuild && bower install'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the Abricotine package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! electron-rebuild && bower install
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs Abricotine
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls Abricotine
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! /tmp/makepkg/abricotine/src/Abricotine-0.3.2/npm-debug.log
==> ERROR: A failure occurred in build().
Aborting...

z3ntu commented on 2016-04-07 13:39

Actually this error happens on both my server and on my laptop. I have bower installed only on my laptop (not on my server) and there is no command "electron" on either.
If you are interested in more info:
pacman -Q: http://pastebin.com/8P2HTXhN
another build log after removing pkg/, src/, etc: http://pastebin.com/r80dWZYS

heddson commented on 2016-04-07 13:29

I tried different scenarios (like building for different architectures and so on..) but I'm still unable to get your error.

Maybe it could be something with permissions? but I'm just guessing..

Another thing maybe worth noting is that I neither have bower or electron installed on my system. Do you have any of them installed? Maybe they conflict in some way, since npm installs them locally in the build dir..

I'm building on x64 with regular kernel.

All comments