Package Details: ruby-jekyll 3.2.1-1

Git Clone URL: (read-only)
Package Base: ruby-jekyll
Description: A simple, blog aware, static site generator.
Upstream URL:
Licenses: MIT
Submitter: oliparcol
Maintainer: CarstenF
Last Packager: CarstenF
Votes: 51
Popularity: 2.405182
First Submitted: 2010-12-14 20:45
Last Updated: 2016-09-07 19:06

Latest Comments

zasdfgbnm commented on 2016-08-11 17:24

Please update the dependency list

jleclanche commented on 2016-07-31 19:05

Edit: Ruby-colorator dependency seems broken. It's not finding it.

CarstenF commented on 2016-04-01 14:16

@fusion809, Thanks for your report. I have changed the url and updated to the new version.

fusion809 commented on 2016-04-01 05:57

@CarstenF, I know this is a minor detail, but you may wish to note that the Jekyll GitHub repo is now at and not Jekyll also has its own website at Jekyll 3.1.2 is now out too.

caleb commented on 2016-03-14 14:54

This needs to have dependencies added for ruby-rb-{fsevent,inotify}.

CarstenF commented on 2016-02-09 15:01

Package Update to 3.1.1

sleeping commented on 2016-02-03 22:06

I had to install a whole bunch of gems manually, after that I had to downgrade Celluloid with

gem install celluloid --version 0.16.0
gem uninstall celluloid --version 0.17.3

Works now!

CarstenF commented on 2016-01-27 10:06

The Update of the Package is WIP. But I can not upload it. If I find the Problem I will push the Update

kseistrup commented on 2015-12-23 10:09

The official version is now 3.0.1. Could the maintainer please update this package? Cheers.

hobarrera commented on 2015-08-24 23:03

Manually maintaining a pile of ruby-* packages is a PITA. I recently discovered an Arch repo that contains binary packages for these, automatically generated, and maintained by one of the Arch devs (so we might as well trust it).

I recommend that you prefer it instead of using the AUR:

I'll be orphaning this now, so feel free to pick it up if you don't care much about my above advise.

Note that I've updated jekyll and all it's dependencies too, so it's safe to keep using this anyway.

All comments