https://dev.arvados.org/https://dev.arvados.org/favicon.ico?15576888422015-08-11T18:51:12ZArvadosArvados - Bug #6885: [Deployment] Add meaningful package versions to distro packageshttps://dev.arvados.org/issues/6885?journal_id=286592015-08-11T18:51:12ZBrett Smithbrett.smith@curii.com
<ul><li><strong>Subject</strong> changed from <i>[Deployment] Add meaningful package verisons to distro packages</i> to <i>[Deployment] Add meaningful package versions to distro packages</i></li></ul> Arvados - Bug #6885: [Deployment] Add meaningful package versions to distro packageshttps://dev.arvados.org/issues/6885?journal_id=286602015-08-11T19:03:53ZBrett Smithbrett.smith@curii.com
<ul></ul><p>Current expected solution: arvados-dev includes a configuration file that includes triples of (source package name, source version, package version). Whenever run-build-packages.sh builds source package name+package version, it should set the increment to package version. For any other build, it should not set the increment, or set it to 1 (the default).</p> Arvados - Bug #6885: [Deployment] Add meaningful package versions to distro packageshttps://dev.arvados.org/issues/6885?journal_id=289182015-08-18T13:24:13ZBrett Smithbrett.smith@curii.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/28918/diff?detail_id=28316">diff</a>)</li></ul><p>The fpm-info.sh mechanism recently added to arvados-dev gives us another channel to do this. For packages with source outside the Arvados tree, you can have the corresponding fpm-info.sh say:</p>
<pre><code>fpm_args+=(--iteration 2)</code></pre>
<p>You could also do this with our own Arvados packages… except, of course, that will bump the software version as well. So maybe we want to use empty commits as our package rebuild trigger?</p> Arvados - Bug #6885: [Deployment] Add meaningful package versions to distro packageshttps://dev.arvados.org/issues/6885?journal_id=289482015-08-18T18:42:37ZBrett Smithbrett.smith@curii.com
<ul><li><strong>Story points</strong> set to <i>1.0</i></li></ul><p>Empty commits don't work to trigger new package builds for our own packages, since they look for commits that affect the specific component. So we still need an out of band mechanism to specify package iterations for those.</p>
<p>We're still agreed on the concept of maintaining a file of triples with package name, source version, and package iteration. Do that.</p> Arvados - Bug #6885: [Deployment] Add meaningful package versions to distro packageshttps://dev.arvados.org/issues/6885?journal_id=319872015-10-30T18:10:53ZBrett Smithbrett.smith@curii.com
<ul><li><strong>Target version</strong> changed from <i>Arvados Future Sprints</i> to <i>Kanban</i></li></ul> Arvados - Bug #6885: [Deployment] Add meaningful package versions to distro packageshttps://dev.arvados.org/issues/6885?journal_id=472722017-01-18T03:09:08ZWard Vandewegeward@curii.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Resolved</i></li><li><strong>Assigned To</strong> set to <i>Ward Vandewege</i></li><li><strong>Target version</strong> changed from <i>Kanban</i> to <i>2017-01-18 sprint</i></li></ul><p>This was fixed as part of #10858</p>