Thicket data repository for the EEG
anil.recoil.org
1{
2 "id": "https://mort.io/blog/inconstant-ruby/",
3 "title": "Diamonds are a Chap's Best Friend",
4 "link": "https://mort.io/blog/inconstant-ruby/",
5 "updated": "2015-04-09T00:00:00",
6 "published": "2015-04-09T00:00:00",
7 "summary": "<p>As <a href=\"https://mort.io/blog/2015/01/15/begin-again/\">noted previously</a>, this site is basically a\n<a href=\"https://github.com/\">Github</a>-hosted <a href=\"http://jekyllrb.com/\">Jekyll</a> site at present, though one that can be built as a\n<a href=\"http://openmirage.org/\">Mirage</a> unikernel. Part of the <a href=\"http://openmirage.org/\">Mirage</a> workflow to publish a new post\ninvolves using <a href=\"https://travis-ci.org/\">Travis CI</a> to build and then commit back a new unikernel\nimage. Thus it is currently necessary to run <a href=\"http://jekyllrb.com/\">Jekyll</a> in the <a href=\"https://travis-ci.org/\">Travis</a> build\nscripts, and the dynamism of the Ruby environment meant that this broke (again)\nrecently as one of the <code>github-pages</code> gem’s dependencies now depends on <code>Ruby >= 2.0</code> while the default Rubies on the <a href=\"https://travis-ci.org/\">Travis</a> Ubuntu image for <code>C</code> language\nbuilds is <code>1.8</code> (via Ubuntu packaging) or, if you remove that one, <code>1.9</code> (via\n<a href=\"https://rvm.io/\">rvm</a>). Read on to find out how to fix this…</p>\n<p>The fix that currently works for me turns out to be relatively simple: remove\nall the rubies installed as Ubuntu packages, and then invoke <a href=\"https://rvm.io/\">rvm</a> to set the\ndefault ruby to something reasonable – in this case, 2.1.</p>\n<pre><code><span><span><span>#</span></span><span># remove old ubuntu rubies</span><span>\n</span></span><span><span><span>sudo</span></span><span> apt-get<span><span> -</span>y</span> remove ruby ruby1.8</span>\n</span><span><span><span>sudo</span></span><span> apt-get<span><span> -</span>y</span> autoremove</span>\n</span><span>\n</span><span><span><span>#</span></span><span># use rvm and a modern-ish ruby</span><span>\n</span></span><span><span><span>source</span></span><span> <span><span>~</span></span>/.rvm/scripts/rvm</span>\n</span><span><span><span>rvm</span></span><span><span><span> --</span>default</span> use 2.1</span>\n</span><span>\n</span><span><span><span>#</span></span><span># check that all worked...</span><span>\n</span></span><span><span><span>which</span></span><span> ruby</span>\n</span><span><span><span>ruby</span></span><span><span><span> --</span>version</span></span>\n</span><span>\n</span><span><span><span>#</span></span><span># install jekyll and github-pages</span><span>\n</span></span><span><span><span>gem</span></span><span> install jekyll</span>\n</span><span><span><span>gem</span></span><span> install github-pages<span><span> --</span>no-rdoc</span><span><span> --</span>no-ri</span></span>\n</span><span><span><span>jekyll</span></span><span><span><span> -</span>v</span></span>\n</span></code></pre>\n<p>And that’s all there is to it – you should now be able to call <code>jekyll</code> in your\n<a href=\"https://travis-ci.org/\">Travis</a> environment as you’d expect…</p>",
8 "content": "<p>As <a href=\"https://mort.io/blog/2015/01/15/begin-again/\">noted previously</a>, this site is basically a\n<a href=\"https://github.com/\">Github</a>-hosted <a href=\"http://jekyllrb.com/\">Jekyll</a> site at present, though one that can be built as a\n<a href=\"http://openmirage.org/\">Mirage</a> unikernel. Part of the <a href=\"http://openmirage.org/\">Mirage</a> workflow to publish a new post\ninvolves using <a href=\"https://travis-ci.org/\">Travis CI</a> to build and then commit back a new unikernel\nimage. Thus it is currently necessary to run <a href=\"http://jekyllrb.com/\">Jekyll</a> in the <a href=\"https://travis-ci.org/\">Travis</a> build\nscripts, and the dynamism of the Ruby environment meant that this broke (again)\nrecently as one of the <code>github-pages</code> gem’s dependencies now depends on <code>Ruby >= 2.0</code> while the default Rubies on the <a href=\"https://travis-ci.org/\">Travis</a> Ubuntu image for <code>C</code> language\nbuilds is <code>1.8</code> (via Ubuntu packaging) or, if you remove that one, <code>1.9</code> (via\n<a href=\"https://rvm.io/\">rvm</a>). Read on to find out how to fix this…</p>\n<p>The fix that currently works for me turns out to be relatively simple: remove\nall the rubies installed as Ubuntu packages, and then invoke <a href=\"https://rvm.io/\">rvm</a> to set the\ndefault ruby to something reasonable – in this case, 2.1.</p>\n<pre><code><span><span><span>#</span></span><span># remove old ubuntu rubies</span><span>\n</span></span><span><span><span>sudo</span></span><span> apt-get<span><span> -</span>y</span> remove ruby ruby1.8</span>\n</span><span><span><span>sudo</span></span><span> apt-get<span><span> -</span>y</span> autoremove</span>\n</span><span>\n</span><span><span><span>#</span></span><span># use rvm and a modern-ish ruby</span><span>\n</span></span><span><span><span>source</span></span><span> <span><span>~</span></span>/.rvm/scripts/rvm</span>\n</span><span><span><span>rvm</span></span><span><span><span> --</span>default</span> use 2.1</span>\n</span><span>\n</span><span><span><span>#</span></span><span># check that all worked...</span><span>\n</span></span><span><span><span>which</span></span><span> ruby</span>\n</span><span><span><span>ruby</span></span><span><span><span> --</span>version</span></span>\n</span><span>\n</span><span><span><span>#</span></span><span># install jekyll and github-pages</span><span>\n</span></span><span><span><span>gem</span></span><span> install jekyll</span>\n</span><span><span><span>gem</span></span><span> install github-pages<span><span> --</span>no-rdoc</span><span><span> --</span>no-ri</span></span>\n</span><span><span><span>jekyll</span></span><span><span><span> -</span>v</span></span>\n</span></code></pre>\n<p>And that’s all there is to it – you should now be able to call <code>jekyll</code> in your\n<a href=\"https://travis-ci.org/\">Travis</a> environment as you’d expect…</p>",
9 "content_type": "html",
10 "author": {
11 "name": "Unknown",
12 "email": null,
13 "uri": null
14 },
15 "categories": [],
16 "source": "https://mort.io/atom.xml"
17}