[
https://issues.apache.org/jira/browse/STORM-2629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16165935#comment-16165935
]
ASF GitHub Bot commented on STORM-2629:
---------------------------------------
Github user srdo commented on the issue:
https://github.com/apache/storm-site/pull/1
@HeartSaVioR I've tried it out on Windows 10 and ruby 2.3.4p301. I just
went and tested it on a fresh install of Ubuntu 17.04 and ruby 2.4.1p111.
Did you run `bundler install` after switching to this branch?
I'm wondering if the README is a little misleading, it's my understanding
that people should use Bundler to update dependencies and run Jekyll, but the
README doesn't mention it.
Here's the commands I ran to start the local server:
`bundler install`
`bundler exec jekyll serve -w`
> Can't build site on Windows due to Nokogiri failing to install
> --------------------------------------------------------------
>
> Key: STORM-2629
> URL: https://issues.apache.org/jira/browse/STORM-2629
> Project: Apache Storm
> Issue Type: Bug
> Components: asf-site
> Reporter: Stig Rohde Døssing
> Assignee: Stig Rohde Døssing
> Priority: Minor
> Labels: pull-request-available
> Attachments: STORM-2629.patch
>
>
> I'm using Windows 10's bash support, and I'm having some trouble building the
> site since Nokogiri won't install.
> {code}
> Running 'configure' for libxml2 2.9.2... ERROR, review
> '/tmp/bundler20170714-31-159r6j1nokogiri-1.6.7.2/gems/nokogiri-1.6.7.2/ext/nokogiri/tmp/x86_64-pc-linux-gnu/ports/libxml2/2.9.2/configure.log'
> to see what happened. Last lines are:
> ========================================================================
> checking build system type... ./config.guess: line 4: $'\r': command not found
> ./config.guess: line 6: $'\r': command not found
> ./config.guess: line 33: $'\r': command not found
> {code}
> Upgrading Nokogiri fixes this issue, so I'd like to upgrade the gemfile to
> the latest version of github-pages, i.e. run "bundler update". As far as I
> can tell, we only need to make a small number of changes to get it working.
> * It seems like the meaning of the {{page}} variable in a layout has changed
> in Jekyll. _layouts/about.html should use {{layout}} to refer to it's own
> variables instead of {{page}} (which would belong to the concrete page being
> rendered). The other layouts don't refer to their own front matter, so there
> shouldn't be any issue there
> * Jekyll has made redcarpet an optional dependency, so the gemfile should
> list that dependency explicitly
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
