Thicket data repository for the EEG
anil.recoil.org
1{
2 "id": "https://mort.io/blog/topkg-addendum/",
3 "title": "Platforms, Packaging, Progress— Addendum",
4 "link": "https://mort.io/blog/topkg-addendum/",
5 "updated": "2017-09-01T00:00:00",
6 "published": "2017-09-01T00:00:00",
7 "summary": "<p>This is a short addendum to my <a href=\"http://mort.io/blog/2017/08/28/past-present-future/\">post of a couple of days\nago</a> caused by my\ncarelessness in writing the <a href=\"https://github.com/mor1/ocal/blob/13a9a7f5b8f2e0be4c2b55941a00a885df202cf8/ocal.opam#L16-L22\">OPAM\nfile</a>.\nCareful readers will observe the lack of any dependency on <a href=\"https://github.com/pqwy/notty/\">notty</a>. Read on for\nwhat happened next…</p>\n<p>The result of this carelessness was that everything worked just fine locally,\nbut <a href=\"https://github.com/ocaml/opam-repository/pull/10176\">my PR to the OPAM package\nrepository</a> failed. Cue\nmuch wailing and gnashing of teeth.</p>\n<p>However, thanks to a moment’s assistance\nfrom <a href=\"http://erratique.ch/contact.en\">Daniel Bünzli</a>, this was easy to fix:</p>\n<pre><code><span><span><span>$</span></span><span> git checkout 0.2.0 <span><span>#</span></span><span> checkout the relevant release version tag</span><span>\n</span></span></span><span><span><span>$</span></span><span> topkg opam pkg <span><span>#</span></span><span> create the release metadata</span><span>\n</span></span></span><span><span><span>$</span></span><span> e _build/ocal.0.2.0/opam <span><span>#</span></span><span> invoke editor so I can add the missing dep</span><span>\n</span></span></span><span><span><span>$</span></span><span> topkg opam submit <span><span>#</span></span><span> submit the updated OPAM metadata, updating the PR</span><span>\n</span></span></span><span><span><span>Submitting</span></span><span> _build/ocal.0.2.0</span>\n</span><span><span><span>[ocal-0.2.0.tbz]</span></span><span> http://github.com/mor1/ocal/releases/download/0.2.0/ocal-0.2.0.tbz downloaded</span>\n</span><span><span><span>Updating</span></span><span> existing pull-request <span><span>#</span></span><span>10176</span><span>\n</span></span></span><span><span><span>Pull-requested:</span></span><span> https://github.com/ocaml/opam-repository/pull/10176</span>\n</span></code></pre>\n<p>For me, the main thing to note here is that the OPAM metadata in the repo at the\ncommit ref tagged for release doesn’t match that which OPAM uses to install the\nrelease. But as <a href=\"http://seb.mondet.org/\">Sebastien Mondet</a> pointed out to me,\nthis is neither relevant nor (in the long term) likely, as (e.g.) version\nconstraints on dependencies may need to be added to old versions of dependent\npackages to keep them working. (Though I did add and commit the dependency to\n<code>master</code>, naturally.)</p>\n<p>So, all-in-all, an easy fix to a common problem. Which is the way it should\nbe…</p>",
8 "content": "<p>This is a short addendum to my <a href=\"http://mort.io/blog/2017/08/28/past-present-future/\">post of a couple of days\nago</a> caused by my\ncarelessness in writing the <a href=\"https://github.com/mor1/ocal/blob/13a9a7f5b8f2e0be4c2b55941a00a885df202cf8/ocal.opam#L16-L22\">OPAM\nfile</a>.\nCareful readers will observe the lack of any dependency on <a href=\"https://github.com/pqwy/notty/\">notty</a>. Read on for\nwhat happened next…</p>\n<p>The result of this carelessness was that everything worked just fine locally,\nbut <a href=\"https://github.com/ocaml/opam-repository/pull/10176\">my PR to the OPAM package\nrepository</a> failed. Cue\nmuch wailing and gnashing of teeth.</p>\n<p>However, thanks to a moment’s assistance\nfrom <a href=\"http://erratique.ch/contact.en\">Daniel Bünzli</a>, this was easy to fix:</p>\n<pre><code><span><span><span>$</span></span><span> git checkout 0.2.0 <span><span>#</span></span><span> checkout the relevant release version tag</span><span>\n</span></span></span><span><span><span>$</span></span><span> topkg opam pkg <span><span>#</span></span><span> create the release metadata</span><span>\n</span></span></span><span><span><span>$</span></span><span> e _build/ocal.0.2.0/opam <span><span>#</span></span><span> invoke editor so I can add the missing dep</span><span>\n</span></span></span><span><span><span>$</span></span><span> topkg opam submit <span><span>#</span></span><span> submit the updated OPAM metadata, updating the PR</span><span>\n</span></span></span><span><span><span>Submitting</span></span><span> _build/ocal.0.2.0</span>\n</span><span><span><span>[ocal-0.2.0.tbz]</span></span><span> http://github.com/mor1/ocal/releases/download/0.2.0/ocal-0.2.0.tbz downloaded</span>\n</span><span><span><span>Updating</span></span><span> existing pull-request <span><span>#</span></span><span>10176</span><span>\n</span></span></span><span><span><span>Pull-requested:</span></span><span> https://github.com/ocaml/opam-repository/pull/10176</span>\n</span></code></pre>\n<p>For me, the main thing to note here is that the OPAM metadata in the repo at the\ncommit ref tagged for release doesn’t match that which OPAM uses to install the\nrelease. But as <a href=\"http://seb.mondet.org/\">Sebastien Mondet</a> pointed out to me,\nthis is neither relevant nor (in the long term) likely, as (e.g.) version\nconstraints on dependencies may need to be added to old versions of dependent\npackages to keep them working. (Though I did add and commit the dependency to\n<code>master</code>, naturally.)</p>\n<p>So, all-in-all, an easy fix to a common problem. Which is the way it should\nbe…</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}