<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-cloud-init.git/tools/make-tarball, branch crux</title>
<subtitle> (mirror of https://github.com/vyos/vyos-cloud-init.git)
</subtitle>
<id>https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=crux</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=crux'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/'/>
<updated>2018-04-12T21:51:45+00:00</updated>
<entry>
<title>tools: Fix make-tarball cli tool usage for development</title>
<updated>2018-04-12T21:51:45+00:00</updated>
<author>
<name>Chad Smith</name>
<email>chad.smith@canonical.com</email>
</author>
<published>2018-04-12T21:51:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=49b562c94838f4e2c0aa0df01a5247d06bc8a561'/>
<id>urn:sha1:49b562c94838f4e2c0aa0df01a5247d06bc8a561</id>
<content type='text'>
This tool is used to assist during the creation of ubuntu packages for
release testing. Address the following on the command-line:
 * --help option now print usage
 * Add --orig-tarball which creates named output file
   cloud-init_&lt;release-version&gt;.orig.tar.gz
 * drop unused --verbose option
</content>
</entry>
<entry>
<title>tools: Give specific --abbrev=8 to "git describe"</title>
<updated>2017-10-05T18:21:00+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@brickies.net</email>
</author>
<published>2017-10-05T18:21:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=6eb4dc24fe314ce5c98b05b21988402cda95afce'/>
<id>urn:sha1:6eb4dc24fe314ce5c98b05b21988402cda95afce</id>
<content type='text'>
The tools that use "git describe" were just assuming a consisent
number of characters in the hash.  It seems ubuntu 16.04 would use 7
and later versions use 8.  To avoid that discrepency in developer
environments, set it to 8.
</content>
</entry>
<entry>
<title>build: fix running Make on a branch with tags other than master</title>
<updated>2017-01-23T14:39:01+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@brickies.net</email>
</author>
<published>2017-01-20T14:36:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=a3376d45c83e90150d8de79a2b31282a7d760bd7'/>
<id>urn:sha1:a3376d45c83e90150d8de79a2b31282a7d760bd7</id>
<content type='text'>
running 'make' on a git branch other than master would fail with
complaint that the tools/read-version reported a different version
than the code.

Change to only consider tags starting with 0-9 in read-version.
</content>
</entry>
<entry>
<title>make-tarball: older versions of git with --format=tar.</title>
<updated>2016-08-10T05:02:28+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@ubuntu.com</email>
</author>
<published>2016-08-10T05:02:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=3973223593ab7bded806f02473164ac105f2896e'/>
<id>urn:sha1:3973223593ab7bded806f02473164ac105f2896e</id>
<content type='text'>
Some older versions of git (Centos 6) do not have --format=tar.gz.
To work around this, create a .tar file and then compress it.
</content>
</entry>
<entry>
<title>For upstream snapshot versions do not modify git-describe output.</title>
<updated>2016-08-08T21:52:24+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@brickies.net</email>
</author>
<published>2016-08-08T17:24:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=48ec60ae19c749223cb58dcbdbf0ecb7343f2a31'/>
<id>urn:sha1:48ec60ae19c749223cb58dcbdbf0ecb7343f2a31</id>
<content type='text'>
For upstream version directly use the output of git-describe
(X.Y.Z-number.gHASH) rather than rather than changing it to
(X.Y.Z+number.gHASH).

The rpm version does not allow '-' in Version, so we create and use
rpm_upstream_version in the rpm spec file.  That is of format:
X.Y.Z+number.gHASH
</content>
</entry>
<entry>
<title>drop modification of version during make-tarball, tools changes.</title>
<updated>2016-08-05T20:53:53+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@brickies.net</email>
</author>
<published>2016-08-05T19:51:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=42bed116b411eb25ebd8368b2b4ed6c56ffd85e7'/>
<id>urn:sha1:42bed116b411eb25ebd8368b2b4ed6c56ffd85e7</id>
<content type='text'>
Modification of the tarball became problematic, as it meant that
any tool extracting source would find the orig source tarball different.
I found this unusable when trying to use 'gbp buildpackage'.

Other changes here are to better support using python3 or python2
for the build.  Makefile will try to call the right python version
and can be told which python to use.

read-version: by adding 'tiny_p' and avoiding the import of
cloudinit.util, we need less dependencies to run this.
</content>
</entry>
<entry>
<title>adjust tools and version information.</title>
<updated>2016-08-05T19:00:12+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@brickies.net</email>
</author>
<published>2016-08-05T15:56:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=10f82bd474c5bc91b330beccd883da06b0014a99'/>
<id>urn:sha1:10f82bd474c5bc91b330beccd883da06b0014a99</id>
<content type='text'>
upstream snapshots are versioned in the format 'X.Y.Z+&lt;distance&gt;.g&lt;commit&gt;'
where X.Y.Z are major, minor, and micro.  Distance is number of commits
since last annotated tag, and commit is the git commit.

bddeb and brpm will now create and use the "upstream version" like above.

Things changed here:
 - tools/make-tarball
   update cloudinit/version.py to contain the full version
   support --output
   support '--long' to always create the long format version string.

 - bddeb:
   - use quilt debian source format
   - use read-version and long version in changelog.

 - brpm:
   - change to use read-version and upstream long version in the spec.
   - flake8 changes

 - tools/read-version
   - read version from git or from cloudinit/version.
   - provide --json output with more nicely formed data.
</content>
</entry>
<entry>
<title>Update build tools to work with git</title>
<updated>2016-08-03T20:00:52+00:00</updated>
<author>
<name>Lars Kellogg-Stedman</name>
<email>lars@redhat.com</email>
</author>
<published>2016-07-22T19:09:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=72d6adcb2e4cb5911f7809b89835965d4bf04476'/>
<id>urn:sha1:72d6adcb2e4cb5911f7809b89835965d4bf04476</id>
<content type='text'>
- Update HACKING.rst to include git instructions
- update MANIFEST.in and .gitignore to ignore git-related things
- replaced tarball generation scripts with git-based script
- have the spec files correctly identify themselves as cheetah templates
- make brpm work with git
</content>
</entry>
<entry>
<title>tools/make-tarball: add ability to include uncommited changes</title>
<updated>2014-02-28T21:19:19+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@ubuntu.com</email>
</author>
<published>2014-02-28T21:19:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=91770eb78f30bea931bafa8d07b4f7f41193185b'/>
<id>urn:sha1:91770eb78f30bea931bafa8d07b4f7f41193185b</id>
<content type='text'>
if you have UNCOMMITTED=1 in environment then the tree will
contain uncommitted changes.
</content>
</entry>
<entry>
<title>tools: fix [some] shell quoting problems</title>
<updated>2013-04-09T21:57:41+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@ubuntu.com</email>
</author>
<published>2013-04-09T21:57:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=90a6bbda5c181569a969edb0d191d19b6110755b'/>
<id>urn:sha1:90a6bbda5c181569a969edb0d191d19b6110755b</id>
<content type='text'>
There were problems with these tools if the path had a space.  This should
make these tools safe.  There are others that still have problems.
</content>
</entry>
</feed>
