Package Details: ghost 0.11.10-1

Git Clone URL: (read-only)
Package Base: ghost
Description: Free, open, simple blogging platform
Upstream URL:
Keywords: nodejs
Licenses: MIT
Submitter: cyang
Maintainer: dmeijboom
Last Packager: storrgie
Votes: 30
Popularity: 0.670286
First Submitted: 2013-10-15 06:07
Last Updated: 2017-06-20 20:35

Latest Comments

storrgie commented on 2017-10-01 15:39

@Alad: done, sorry I didn't see that option. I'm thinking that this package should turn into ghost-legacy, and that someone should package ghost-cli. Either way, I'm not someone who does development in nodejs so I get frustrated easily with the ecosystem, I hope someone else with more experience picks this up.

Alad commented on 2017-09-30 16:05

@storrgie: you don't need to file a request to orphan a package you maintain. Just click "Disown Package" in the Package Actions box.

derintendant commented on 2017-09-30 11:42

I"m sorry, but I am afraid, I'll have to disown this package. With 1.0 the packaging will have to be completely overhauled, and as I am rathjer inexperienced with NodeJS, I dont"t think I will be able to do that dequately. Please feel free to go on. :)

RcrdBrt commented on 2017-09-28 14:53

it seems not @jollanza :(

jollanza commented on 2017-09-06 08:40

any news?

ToKrCZ commented on 2017-08-24 20:40

Just tried to make my own .pkg with `debtap`, but it fails to start. I am totally inexperienced with packaging, so maybe someone else may succeed. The package is built rather successfully, only with some minor warning, but the app doesn't start at all. There seem to be problems with main object init, as far as I can say (tested ghost-desktop-1.3.0-debian.deb as source).

tom-ntb% /usr/bin/Ghost
A JavaScript error occurred in the main process
Uncaught Exception:
Error: Unable to find a valid app
at Object.<anonymous> (/usr/lib/Ghost/resources/electron.asar/browser/init.js:121:9)
at Object.<anonymous> (/usr/lib/Ghost/resources/electron.asar/browser/init.js:173:3)
at Module._compile (module.js:571:32)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:488:32)
at tryModuleLoad (module.js:447:12)
at Function.Module._load (module.js:439:3)
at Module.runMain (module.js:605:10)
at run (bootstrap_node.js:424:7)
at startup (bootstrap_node.js:147:9)

jollanza commented on 2017-08-24 09:12

I want 1.0 so bad

sargate commented on 2017-08-22 16:45

My 2 cents, I tried ghost-cli is making things really easy for general use, too bad they focused only on ubuntu, we might want to contribute to ghost-cli to work with arch, instead of having to change everything in here to make it work.

I think for this package there are 2 options:
1. Use ghost-cli local over the /usr/share/weabapps/ghost directory (and maybe 1 more pkg for ghost-cli that should be included here as dependency)
2. Just get the latest src to build ghost


storrgie commented on 2017-08-20 15:57

I'm still unsure how how we should package this. They've released 1.0 now and there is a _very strong_ indication that their golden path for install requires ghost-cli (which should be a separate package).

I'm hesitant to change anything about this because right now it still installs a version of ghost legacy that actually works.

I'd really like some assistance from others, I'm not a node person. I feel entirely confused by all of the "assistance" that ghost-cli is trying to help out with. I would much prefer we package/install/run ghost 1.0 the same way as we're doing here.

MattScherbatsky commented on 2017-07-28 12:17

"please stop demanding that changes be made immediately."
Wtf? My ghost installation works fine, I don't demand that changes be made immediately. BTW, if you need my help, ask me.

storrgie commented on 2017-07-28 12:10


If you have a working solution for yourself that is fantastic. This is a package in the AUR for many people to use, so we're going to try to ensure that we're not making updates that will break peoples systems. I'll be looking at this over the weekend.

Please feel free to contribute what you're finding out works in the comments here, but make sure you're testing it locally, make sure your output is in english, and please stop demanding that changes be made immediately. As it stands, the current PKGBUILD will result in a fully working instance.

Also, it doesn't matter if ghost-cli is a new "easy" thing they've released, we'll be ensuring that we wrap whatever initialization they require in systemd for continuity with the rest of the system.

MattScherbatsky commented on 2017-07-28 10:19

For 1.0.2:
mkdir /usr/share/webapps/ghost
cd /usr/share/webapps/ghost
sudo chmod 755 ghost
sudo npm install --unsafe-perm --verbose -g ghost-cli
sudo ghost install local and it works.

Very easy. To start it after backup, run "ghost start"

We need to change pkgbuild to works with new ghost installation.

MattScherbatsky commented on 2017-07-27 16:20

1.0.2 is out

same error.

MattScherbatsky commented on 2017-07-26 22:48

1.0.0 released.

nodejs-lts-boron is now a new dependecy instead Argon version.

But I've this error:

semop(1): encountered an error: Argomento non valido
/usr/bin/fakeroot: riga 1: kill: (5386) - Nessun processo corrisponde

storrgie commented on 2017-07-22 12:23

I'm really curious about someone with more experience packaging node related projects giving some advice. I don't think we'll get any assistance from upstream as they'll posit it's a distribution related issue. Consider me blocked unless I suddenly get some inspiration on this one.

MattScherbatsky commented on 2017-07-21 21:22

I have that problem, too. I'm sorry but I've tested it only now.

storrgie commented on 2017-07-21 16:47

@MattScherbatsky I'm seeing an error on any of my tests that looks like this:

I reported what I initially thought was an issue with upstream:

but then I looked and saw there were no dependent package updates in their `package.json`:

[storrgie@clavain Downloads]$ diff Ghost-0.11.10/package.json Ghost-0.11.11/package.json
< "version": "0.11.10",
> "version": "0.11.11",

I then reported this stuff to their slack but couldn't find a resolution.

Anyone with insight I'd be appreciative of. I'm able to get 0.11.10 built without issue, but 0.11.11 doesn't want to build on any of my instances so I'm reluctant to bump the version of the AUR and have others be in a failing state.

MattScherbatsky commented on 2017-07-20 22:10

0.11-11 is out.


storrgie commented on 2017-06-20 20:47

Thanks @Zepman, should be squared away now.

Zepman commented on 2017-06-20 15:11

Package is outdated. 0.11.10 is out:

It is easy to change the old version to build the new version (verified).

In PKGBUILD, change 'pkgver' to '0.11.10'.

In PKGBUILD, change the first value of sha512sums to 'b4d65af0c00e58c230b30fbe652d6bb16765166c52a334fc32efc85cab66c82dc36caec68fc9e1dd8e86024fc0adfd8c6f8167273d00af6a428a3006bd9726ea'.

Create and install the package in the usual way.

storrgie commented on 2017-06-12 14:19

With `nodejs-lts-argon` moving to Community and the OpenSSL 1.0 and 1.1 releases, you very well may have to reinstall `nodejs-lts-argon`, then re-install this package.

storrgie commented on 2017-05-19 00:16

This is my first AUR push, hope everything goes well for folks. With a minor revision I tested this PKGBUILD on two installs and didn't have any problems.

cinaed666 commented on 2017-05-18 09:16

0.11.9 is out!

jollanza commented on 2017-04-28 10:28

Ghost 0.11.8 is out now!

derintendant commented on 2017-03-18 11:55

Just updated to v.0.11.7.

@storrgie Sure, just send me a quick Email about it.

sargate commented on 2017-03-13 16:31

there is a commit in github, you can check it out to merge it:


storrgie commented on 2017-03-09 17:25

@derintendant, would you accept a co-maintainer?

sargate commented on 2017-03-08 16:48

New version 0.11.7 is out

storrgie commented on 2017-02-27 12:27

Thanks for the update!

jollanza commented on 2017-02-24 09:01

0.11.5 is out

storrgie commented on 2017-02-04 17:32

thanks for packaging this, it made life a lot easier.

jollanza commented on 2017-01-23 12:27


choose node-lts-argon instead of nodejs-7! it works perfectly

chrisjtaylor commented on 2017-01-22 23:54

Any suggestions on how to deal with this:

nodejs-lts-argon conflicts:
- nodejs-7.4.0-1

It just gets caught in a loop if you proceed.

jollanza commented on 2017-01-20 15:55


I have a Raspberry PI 3 with ghost up&running!

follow this steps:
- yaourt -S ghost
- install EVERYTHING
- when nodejs-lts-argon asks if you want to modify PKGBUILD, answer YES
- with nano, vi, or other editors that you have, search the line "arch=", you will probably find other architectures, like x86 or 64bit. add 'arvm7h' (with quotation marks included) to them, then close the editor and run compiling the rest.

let me know if it works or not!

chrisjtaylor commented on 2017-01-19 00:16

Can anyone offer help on getting this to work on Raspberry Pi 3? I'm getting an armv7h incompatibility error as a result of nodejs-lts-argon.

derintendant commented on 2017-01-14 14:21

The package was updated to the latest stable version of ghost (0.11.4) and now depends on the AUR package for the Argon LTS version of NodeJS, as recommended in the Ghost documentation.

Rembrandt commented on 2017-01-10 16:06

@derintendant Thx for the info. I must have overlooked it. :-/ But now everything work.

MattScherbatsky commented on 2017-01-08 19:20

Please check this link for the best nodejs support:

<0.12.* Unsupported
0.12.* Supported
>=4.0 <4.2 Unsupported
>=4.2 <5.* (Node v4 argon LTS) Recommended
5.* Unsupported
>=6.0 <6.9 Unsupported
>=6.9 <7.* (Node v6 boron LTS) Supported
7.* Unsupported

derintendant commented on 2017-01-08 15:02

@Rembrandt I've made some changes to the directory structure to enable simpler updates in the future. You should have received a upgrade notice to manually copy your content directory from /srv/ghost/content to /var/lib/ghost/content and to update your configuration to point to the new directory:

production: {
url: '',
mail: {},
database: {
client: 'sqlite3',
connection: {
filename: path.join('/var/lib/ghost/content/data/ghost.db')
debug: false

server: {
host: '',
port: '2368'

paths: {
contentPath: path.join('/var/lib/ghost/content/')

Besides that: Please, always make sure that you have a current backup before upgrading.

Rembrandt commented on 2017-01-08 14:03

Upgrade to latest version delete my whole content... :-/

MattScherbatsky commented on 2016-11-03 19:09

0.11.3 is out.

sha512sum is: 380effec7433c92bc1b3c73ab321d33c4a1e7053f663c1ba7f58d5f340ba182339812969df6a81c90a53238d323265e00e398fd0acf457d69784500784e68d4b

MattScherbatsky commented on 2016-10-13 07:56

0.11.2 is out.

change the version number and the first sha512sum with '003196b9e80701e213be0c102744ecf0d199fa6a8ed01cc4fb06fe5ca8e04dbcbe4f2da3c21971589ed7e2327aa28718b6eebd76a3df1de7722a49afccb47ff4'


MattScherbatsky commented on 2016-10-07 22:01

This is PKGBUILD for 0.11.1 version of Ghost. Works well on my Raspberry Pi.

MattScherbatsky commented on 2016-09-22 09:33

Ghost 0.11.0 is out..

niklaszantner commented on 2016-08-21 21:27

Interestingly I get this on install:

npm ERR! Linux
npm ERR! argv "/usr/bin/node" "/home/admin/.npm-global/bin/npm" "install" "--production"
npm ERR! node v6.4.0
npm ERR! npm v3.10.6
npm ERR! path /tmp/yaourt-tmp-admin/aur-ghost/pkg/ghost/srv/ghost/node_modules/.staging/core-js-36a99c7e/fn/reflect/prevent-extensions.js
npm ERR! code ENOSPC
npm ERR! errno -28
npm ERR! syscall open

npm ERR! nospc ENOSPC: no space left on device, open '/tmp/yaourt-tmp-admin/aur-ghost/pkg/ghost/srv/ghost/node_modules/.staging/core-js-36a99c7e/fn/reflect/prevent-extensions.js'
npm ERR! nospc This is most likely not a problem with npm itself
npm ERR! nospc and is related to insufficient space on your system.

npm ERR! Please include the following file with any support request:
npm ERR! /tmp/yaourt-tmp-admin/aur-ghost/pkg/ghost/srv/ghost/npm-debug.log

I already increased the amount of allowed watchers and checked the tmp dir for size - both fine. Has someone an idea?

nash commented on 2016-07-30 06:31

With the following simple patch, 0.9.0 seems to work well.

--- PKGBUILD 2016-07-30 14:46:01.240103642 +0900
+++ PKGBUILD.txt 2016-07-30 15:27:52.319174651 +0900
@@ -4,28 +4,25 @@
# Colaborator: Jonhoo

pkgdesc="Free, open, simple blogging platform"
-depends=('nodejs>=0.12' 'npm' 'python')
+depends=('nodejs>=4.0' 'npm' 'python')
- package.json.patch
- npm-shrinkwrap.json.patch
- '17e9c5572f4976af6e129ca20e66b8ef9aeb626b037d1d4b3de19a1dfa9d8feb7854d84dbfeba0e2056ed18cd05215fab5b7a0e05e4c1d67c17e4b58c4fe0483'
- 'be732d99fd2326d103f67cc502eb4ea0ae3bc4b2b2b4d2a713eb1dac7ee5357e01cc05ec9f73762b687a44b39370cb0f05d362d560a5b06e2f6e1b65c3ccaf4e')

# Note: You may need to log into and download the zip file manually
# and place it inside the same directory as the PKGBUILD
@@ -35,8 +32,6 @@
cd "$pkgdir/srv/ghost"
unzip "$srcdir/$pkgname-$"
echo "Fixing sqlite3 to 3.1.4 ......"
- patch npm-shrinkwrap.json < $srcdir/npm-shrinkwrap.json.patch
- patch package.json < $srcdir/package.json.patch
echo "Ingoring Ghost's Nodejs version check ......"
cp config.example.js config.js

Horo commented on 2016-05-31 01:34

I use some patch to make ghost use node-sqlite3@3.1.4 ,and it worked."
(These patch may be removed if Ghost support nodejs 6.x offically)

letroll commented on 2016-05-18 07:54

@springmeyer : "node-sqlite3@3.1.4 has been released, which is the first one to support node v6."

Horo commented on 2016-05-09 13:31

sqlite3 module could not support nodejs 6.0 yet :

PreparationH67 commented on 2016-05-02 18:46

Confirmed that I was able to install the package with nodejs-lts installed instead of the latest nodejs from the official repos and did NOT need to mess with any of the python symlinks, I'm guessing NPM has been using python2 correctly and changing the links just happened to not break anything. I'm not sure what's the best way to handle this in the package config besides more strict dependencies on the nodejs version that match the ghost officially supported node versions page or some more complicated setup around it to have ghost use a different node version in a manner that allows multiple installed versions.

PreparationH67 commented on 2016-05-02 17:00

I finally got around to confirming that sqlite3 can be build via NPM on my system in a clean directory, but errors out when trying to install/build in the ghost directory so it is something specific to Ghosts javascript packages and config. Currently installing nodejs-lts from the AUR to see if that helps when I get a change to try this again, but it does seem like node-gyp/npm are using the correct python binary without mucking with the symlinks. I'm on a 64-bit x86 system, so it still seems weird to me that it is trying to build this at all since my understanding was that compiling sqlite3 from source was an ARM problem.

hestia commented on 2016-04-30 02:55

I just have tested with official ghost installation guide (sorry but not AUR packagebuild) below environment and finally achieved success.

> Raspberry Pi 3 B+
> Arch Linux ARM ARMv7
> node v4.4.3
> npm v2.15.1
> used NVM for change node version from 6.0.1 to 4.4.3
> python2, created symlink as @lrizzo comment. But this will not be good idea for production servers. My server is just for test environment and nothing's using python3. First compile with python3 showed error and there is some command option to using python2, but I can't cuz I'm newbie. ;)

Didn't aware nodejs and npm has quite strict dependency with each versions.

Hestia @minibrary

PreparationH67 commented on 2016-04-29 19:25

Currently having an issue building sqlite3 that is preventing me from updating the package, there are some references to it using node v6 that seems to be the cause, but I am unsure of how to fix the issue.

@Irizzo advice is dangerous and incorrect, do not manipulate the python symlink on your system as most packages are working on the, correct, assumption that /usr/bin/python on Arch Linux is python3 and it is up to package maintainers to patch any packages that still assume /usr/bin/python is symlinked to python2. Manual manipulations like this should only be done as a temporary work around and undone right away or other programs will break on your system.

Horo commented on 2016-03-11 03:43

I have used python (not python2) to test and I haven't found problem now......

lrizzo commented on 2016-03-08 01:37

All those having an issue with build failing for sqlite (e.g. below in comments); you are missing python2.

Run 'pacman -S python2' and re-rerun the makepkg -s

Note: python2 is installed as /usr/bin/python2 so one needs to symlink that to python. By default installing python2 will *NOT* create /usr/bin/python. For example:

ln -s /usr/bin/python2 /usr/bin/python

Also make sure you uninstall python 3 (the default python when you install via pacman -S python) by running pacman -R python

If you follow the above steps, you should have no problem in compiling the ghost package)

Lucius Rizzo

ursidal commented on 2016-02-28 14:59

Trying to compile on a Raspberry Pi B+, I got stuck on the sqlite3 part.
I found somewhere that it is because of the lack of RAM/swap.
I have created a swapfile (see Archwiki) of 1024M (maybe less is enough) and it compiled.

PreparationH67 commented on 2016-02-19 16:09

Thanks for the quick update!

nash commented on 2016-02-15 13:05

Wow, updated! Thanks!

helmi77 commented on 2016-01-07 12:48

As a temporary workaround you could replace the "node" version string in package.json with the version you're using.

lordmetroid commented on 2016-01-05 22:34

Using ghost-0.7.1-3 on an updated Archlinux as of Jan 2016-01-05:

Jan 05 22:25:30 gorilla npm[16766]: ERROR: Unsupported version of Node
Jan 05 22:25:30 gorilla npm[16766]: Ghost needs Node version ~5.0 you are using version 5.3.0

Jonhoo commented on 2015-11-06 01:00

Updated new-node.patch that works with v5:

jascha commented on 2015-10-13 07:27

After the latest npm Update, the ghost servcice doesn't start anymore :(

Okt 13 09:08:09 systemd[1]: Started Ghost Blogging Platform.
Okt 13 09:08:10 npm[680]: > ghost@0.7.1 start /srv/ghost
Okt 13 09:08:10 npm[680]: > node index "/srv/ghost"
Okt 13 09:08:10 npm[680]: ERROR: Unsupported version of Node
Okt 13 09:08:10 npm[680]: Ghost needs Node version ~4.1.0 you are using version 4.2.0
Okt 13 09:08:10 npm[680]: Please go to to get a supported version

€dit: Just manually edit package.json and change "node": "~4.1.0",
This will solve the issue.

sflor commented on 2015-10-10 18:00

Build fails for me:

patching file /tmp/pacaurtmp-sf/ghost/pkg/ghost/srv/ghost/package.json
npm WARN engine html-to-text@1.3.0: wanted: {"node":">= 0.8.0 <=0.12 || <=1.4.0"} (current: {"node":"4.1.2","npm":"3.3.6"})
npm WARN prefer global js-beautify@1.5.4 should be installed with -g

> sqlite3@3.1.0 install /tmp/pacaurtmp-sf/ghost/pkg/ghost/srv/ghost/node_modules/sqlite3
> node-pre-gyp install --fallback-to-build

pedrogabriel commented on 2015-10-01 23:51

I will removed it, but Namcap acuse java-environment as a dep. If you think this is a bug, please contact the namcap upstream.

draringi commented on 2015-09-30 15:55

Removed java-environment from deps list and still builds and installs perfectly (on a machine without java-environment). Seems to be no reason for it.

Jonhoo commented on 2015-09-29 03:11

Why did you add java-environment as a makedepends? I can't see anything that would indicate this is needed from the changelog?

orbifx commented on 2015-09-24 08:54

Thanks Jonhoo, that did the trick. All up and working now.

Jonhoo commented on 2015-09-23 15:12

Ah, yes, AUR messes with whitespace. Try

orbifx commented on 2015-09-23 13:15

Jonhoo: I get an error with the patch:

patch: **** malformed oatch at line 4: "test": "grunt validate --verbose"

Is the patch out of date?

Jonhoo commented on 2015-09-23 04:42

FWIW, a working installation can be produced by:

1) Create a new file, new-node.patch, alongside the PKGBUILD:
--- package.json 2015-09-23 00:28:53.733674984 -0400
+++ package.json 2015-09-23 00:30:08.830456732 -0400
@@ -22,7 +22,7 @@
"test": "grunt validate --verbose"
"engines": {
- "node": "~0.10.0 || ~0.12.0",
+ "node": "~4.1.0",
"iojs": "~1.2.0"
"dependencies": {
@@ -60,7 +60,7 @@
"rss": "1.1.1",
"semver": "4.3.6",
"showdown-ghost": "0.3.6",
- "sqlite3": "3.0.8",
+ "sqlite3": "3.1.0",
"unidecode": "0.1.3",
"validator": "3.40.0",
"xml": "1.0.0"
2) Add new-node.patch to PKGBUILD source array (and run updpkgsums to add checksum)
3) Before "npm install --production" in package(), add:
patch "$pkgdir/srv/ghost/package.json" < "$srcdir/new-node.patch"
rm "$pkgdir/srv/ghost/npm-shrinkwrap.json"

This will update the dependency list of ghost to use an *unsupported* configuration though, so be careful. Discussion on the Ghost issue tracker here:

Jonhoo commented on 2015-09-23 04:25

Currently fails to build (because of sqlite3), but old version also fails to run:
Sep 23 06:24:02 npm[413]: ERROR: Unsupported version of Node
Sep 23 06:24:02 npm[413]: Ghost needs Node version ~0.10.0 || ~0.12.0 you are using version 4.1.0

lordmetroid commented on 2015-09-21 18:21

Tried to restart ghost but it complains about not finding ghost/node_modules/sqlite3/lib/binding/node-v46-linux-x64
There is however a node-v14-linux-x64

pedrogabriel commented on 2015-09-18 03:48

It's currently not building, because there's no sqlite3 build for npm 4.1.0.

blackleg commented on 2015-09-16 23:37

Ghost is a java script program
Not dependent of the processor architecture

Can change the package arch to any?


blackleg commented on 2015-09-04 14:23

@barsanuphe Build fails if npm is not installed, it should be added in the dependencies.

Add npm in the PKGBUILD
makedepends=('unzip' 'npm')

vreyes commented on 2015-05-28 19:33

Ghost 0.6.4 is out.

barsanuphe commented on 2015-05-05 20:26

Build fails if npm is not installed, it should be added in the dependencies.

vreyes commented on 2015-04-01 00:02


# Node v0.10.x - full support
# Node v0.12.x and io.js v1.2 - partial support
# Choose wisely


jdarnold commented on 2015-03-26 12:40

I'm getting the following when trying to update ghost after updating nodejs to 0.12:

npm WARN engine html-to-text@1.2.0: wanted: {"node":">= 0.8.0 <0.12"} (current: {"node":"0.12.0","npm":"2.7.1"})
/tmp/packerbuild-1000/ghost/ghost/PKGBUILD: line 22: 9085 Killed npm install --production
==> ERROR: A failure occurred in package().
The build failed.

HLFH commented on 2015-03-10 12:49 released with Node v0.12 (and the ugly io.js) support.

voxel commented on 2015-02-27 07:33

Thank you, I totally missed that. If it's a recommendation coming from Ghost itself then we should respect it.

cyang commented on 2015-02-25 19:12

Not sure, I haven't had a chance to test, but the docs say that 0.11.x are not supported.

voxel commented on 2015-02-25 11:18

Do we really need the nodejs<0.11.0 dependency? Just asking out of interest since my Pacman won't run now without adding nodejs into IgnorePkg list.

leafonsword commented on 2014-12-18 07:04

Upgrading to ghost 0.5.7-1 occurs foolowing err:
npm ERR! Linux 3.16.5-x86_64-linode46
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "--production"
npm ERR! node v0.10.34
npm ERR! npm v2.1.14

npm ERR! sqlite3@3.0.2 install: `node-pre-gyp install --fallback-to-build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the sqlite3@3.0.2 install script 'node-pre-gyp install --fallback-to-build'.
npm ERR! This is most likely a problem with the sqlite3 package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-pre-gyp install --fallback-to-build
npm ERR! You can get their info via:
npm ERR! npm owner ls sqlite3
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! /tmpdir/yaourt-tmp-gf/aur-ghost/pkg/ghost/srv/ghost/npm-debug.log
==> ERROR: A failure occurred in package().
==> ERROR: Makepkg was unable to build ghost.
==> Restart building ghost ? [y/N]

NOTtheMessiah commented on 2014-12-18 05:01

Make sure you have the environment variable PYTHON=python2 before building, otherwise, gyp will complain.

voxel commented on 2014-12-05 13:39

Ghost 0.5.6 is out.

voxel commented on 2014-11-18 15:16

Ghost 0.5.4 released.

cyang commented on 2014-09-15 16:27

Thanks, updated.

sflor commented on 2014-09-15 06:28

What about 0.5.1?

cyang commented on 2014-09-15 01:50

Someone flagged this out of date, 0.5.0 is currently the newest announced version I have found.

cyang commented on 2014-08-11 19:51

Package has been updated to 0.5.0 and is no longer running as root. Please backup the content directory before updating.

voxel commented on 2014-08-05 13:06

Please update.

linkmauve commented on 2014-06-01 13:43

Hi, could you make it run from a dedicated user instead, create it in an install file, remove it at uninstall time, and make the service script use it, while chowning the files required to be writable by it.

It is very uncomfortable to run it as root all the time.

qote commented on 2014-05-26 21:47

Last week of May and still not updated. Any chances to see the new version soon?

cyang commented on 2014-04-01 01:47

0.4.2 is out, but I won't have a chance to update the package until May. Someone can take a look in the meantime.

ilpianista commented on 2014-02-10 16:28

Oh wait, python2 is needed only on ARM, where sqlite3 is built from sources.
Forgot it then!

ilpianista commented on 2014-02-10 16:22

stack Error: Can't find Python executable "python2", you can set the PYTHON env variable.

Please add python2 to makedepends

cyang commented on 2014-01-23 20:28

I have updated the package to 0.4 with all your suggestions, please let me know if you find any bugs.

Backup the content directory before updating to be safe.

leafonsword commented on 2014-01-13 14:52

ghost 0.4 has released,please upgrade!

ilpianista commented on 2013-12-14 09:18

you don't need unzip to extract a ZIP archive, bsdtar can do that.

leafonsword commented on 2013-12-07 13:07

since differences of development mode and production mode will grow and become more apparent,and most users will be more suitable to production mode,it may be better to settle:
npm start --production
in ghost.service

cyang commented on 2013-12-06 16:04

Thanks guys, I've updated the PKGBUILD with the corrections.

Seems like the hash difference was due to the line terminators changing on all the files.

leafonsword commented on 2013-12-05 14:03

I also calculated with "5a323ac459ac16d84c92171c25e1c820a6ccd962812ed260bde7666f7cbe9922"
Please update PKGBUILD~

leafonsword commented on 2013-12-05 13:59

==> Validating source files with sha256sums... ... FAILED
ghost.service ... Passed
==> ERROR: One or more files did not pass the validity check!
==> ERROR: Makepkg was unable to build ghost.

starfry commented on 2013-11-20 14:28

I found the checksum for to be incorrect in the PKGBUILD. I calculated this to be '5a323ac459ac16d84c92171c25e1c820a6ccd962812ed260bde7666f7cbe9922'.

Also, I think you should add a makedepends=('unzip') to the PKGBUILD.

elirei72 commented on 2013-10-29 03:00

Awesome package man. However it would be helpful for people installing to add "After starting ghost, type http://<domain_name>:2368/ghost in your browser" to the echo in the package build.