[ 
https://issues.apache.org/jira/browse/FLINK-6797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16033018#comment-16033018
 ] 

ASF GitHub Bot commented on FLINK-6797:
---------------------------------------

GitHub user alpinegizmo opened a pull request:

    https://github.com/apache/flink/pull/4043

    [FLINK-6797][docs] Docs do not build cleanly with new version of bundler

    Our Gemfile.lock file includes an inaccurate dependency spec for 
jekyll-gist 1.4.0. Bundler 1.15.0 was recently released, and it is smart enough 
to notice this and fails with an error. This PR updates that dependency. 

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/alpinegizmo/flink 6797-update-gemfile-lock

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/4043.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #4043
    
----
commit 39302594358910ee5a77dc0024118d3c8f9faeeb
Author: David Anderson <[email protected]>
Date:   2017-06-01T13:48:29Z

    [FLINK-6797][docs] Docs do not build cleanly with new version of bundler

----


> building docs fails with bundler 1.15
> -------------------------------------
>
>                 Key: FLINK-6797
>                 URL: https://issues.apache.org/jira/browse/FLINK-6797
>             Project: Flink
>          Issue Type: Bug
>          Components: Documentation
>            Reporter: David Anderson
>            Assignee: David Anderson
>             Fix For: 1.3.1, 1.4.0
>
>
> The script for building the docs installs the latest version of the bundler 
> ruby gem (if it can't find the bundle command, which is always the case on 
> the build-bots, for example). Since the release of bundler 1.15 this fails 
> because it is now pickier about dependency checking, and we somehow ended up 
> with an invalid dependency rule in Gemfile.lock.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to