vyos-build.git/scripts/make-version-file, branch vyos/1.2.6 VyOS image build scripts (mirror of https://github.com/vyos/vyos-build.git) https://git.amelek.net/vyos/vyos-build.git/atom?h=vyos%2F1.2.6 2020-04-16T19:50:16+00:00 T2305: include release train in "show version" output 2020-04-16T19:50:16+00:00 Christian Poessinger christian@poessinger.com 2020-04-16T19:50:16+00:00 urn:sha1:5d1499e61a58a313eaaf685d083e442bbd962ca2 T1378: extend version file with Git commit ID 2019-05-13T20:03:10+00:00 Christian Poessinger christian@poessinger.com 2019-05-11T12:22:17+00:00 urn:sha1:a51706c0467becdad29046475bfc803f9da0ad0f The Git commit ID will be crucial for the future when the full VyOS build can be reproduced by the one Git commit ID, thus start recording it in the version file. (cherry picked from commit e08da45e6d20f1f2ac38fff24e697a155ddac3ea) Move the version.json file used by newer code to /usr/share/vyos 2018-06-08T19:18:18+00:00 Daniil Baturin daniil@baturin.org 2018-06-08T19:17:38+00:00 urn:sha1:82d7ddb1b34e36fa399fd333efc716add8bf341a T596: replace + in new version format by - 2018-06-06T19:52:30+00:00 Christian Poessinger christian@poessinger.com 2018-06-06T19:52:28+00:00 urn:sha1:3af1486d488be0ce450b0f92fed3d45221bdac9f The new version scheme was introduced in commit d2e4f63f03 ("T596: use a more descriptive dev build version format.". It superseeded the old 999.something version numbers. New version numbers for rolling releases are in the form of vyos-1.2.0-rolling+201806062125-amd64.iso but the '+' sign will be replaced by '%2B' when e.g. downloading the file via http(s), this may be confusing. T596: use a more descriptive dev build version format. 2018-04-05T12:59:44+00:00 Daniil Baturin daniil@baturin.org 2018-04-05T12:59:44+00:00 urn:sha1:d2e4f63f03ef5628ab94be34bf368e8c8458a2d0 Switch all build scripts to python3. 2017-01-25T22:01:16+00:00 Daniil Baturin daniil@baturin.org 2017-01-25T22:01:16+00:00 urn:sha1:ea48b7bd747df4ae5c8ee64c72cdc67e31ddcd5a Since we only support jessie as build host, and jessie knowingly does have python3 (although not by default), we don't really need to worry about being both 2 and 3 compatible. After build, create a properly named symlink to the ISO (ref T8). 2016-03-03T23:28:31+00:00 Daniil Baturin daniil@baturin.org 2016-03-03T23:28:31+00:00 urn:sha1:6a7696a1122560073c3121fdecb5e3bd0c6549cf This is important for nightly builds, and handy for release builds. Add a build step for generating version files. 2016-01-26T21:10:52+00:00 Daniil Baturin daniil@baturin.org 2016-01-26T21:10:52+00:00 urn:sha1:cddc611ae3a6da15aaa2bded568209bb3eca27de