brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Harris <>
Subject Re: Problems building the docs
Date Tue, 20 May 2014 10:00:01 GMT
Hi Richard,

David Toy sent me this a while ago when I was working on the docs. It was
sent last October, so I don't know how current it is...:

Hi Martin,

Jekyll has been updated and changed how parameters are specified, in a non
backwards compatible way.

// Aside: Some significant tweaking will be required to update how we build
Brooklyn docs to be compatible with the current version of Jekyll.

Here is a temporary workaround to downgrade Jekyll:

*Remove the new version of Jekyll:*

% sudo gem uninstall jekyll

*Add an older version [1]:*

% wget --no-check-certificate
/archive/v0.11.2.tar.gz > jekyll-0.11.2.tar.gz
% tar -zxf  jekyll-0.11.2.tar.gz
% cd jekyll-0.11.2.tar.gz
% gem build jekyll.gemspec
% sudo gem install jekyll-0.11.2.gem

1. I'm using 0.11.2 at the moment, but I see that it is now ancient, and
there has been plenty of activity since it was released. A dive into will show when the url
parameters were changed. (perhaps on transition to version 1?)


On 19 May 2014 17:40, Richard Downer <> wrote:

> Hi,
> I'm having trouble building docs at the moment. At the root is that
> Jekyll has moved on a few versions and the Brooklyn docs scripts are
> no longer compatible - so when I start from a clean Ruby environment
> and follow the instructions at
> (which
> don't say what component versions they use), when I invoke
> _scripts/ I got errors:
>        Deprecation: Jekyll now uses subcommands instead of just
> switches. Run `jekyll help' to find out more.
>        Deprecation: The 'pygments'settings has been removed in favour
> of 'highlighter'.
> /Users/richard/.rvm/gems/ruby-2.1.0@llp-rpi
> /gems/mercenary-0.3.3/lib/mercenary/program.rb:30:in
> `go': invalid option: --pygments (OptionParser::InvalidOption)
> This is no problem - a couple of tweaks to _config.yml and
> _scripts/ fixes that. (See
> But it results in a much longer error message about malformed JSON,
> which is too long to post here - see:
> Any ideas what is going wrong here?
> Thanks
> Richard.

Martin Harris
Lead Software Engineer
Cloudsoft Corporation Ltd
Mobile: +44 (0)7989 047-855

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message