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: derintendant (storrgie)
Last Packager: storrgie
Votes: 29
Popularity: 1.117275
First Submitted: 2013-10-15 06:07
Last Updated: 2017-06-20 20:35

Latest Comments

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.

All comments