<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-cloud-init.git/packages/debian, branch crux</title>
<subtitle> (mirror of https://github.com/marekm72/vyos-cloud-init.git)
</subtitle>
<id>https://git.amelek.net/marekm72/vyos-cloud-init.git/atom?h=crux</id>
<link rel='self' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/atom?h=crux'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/'/>
<updated>2018-05-22T20:06:41+00:00</updated>
<entry>
<title>Update version.version_string to contain packaged version.</title>
<updated>2018-05-22T20:06:41+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@ubuntu.com</email>
</author>
<published>2018-05-22T20:06:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=5446c788160412189200c6cc688b14c9f9071943'/>
<id>urn:sha1:5446c788160412189200c6cc688b14c9f9071943</id>
<content type='text'>
This modifies version.version_string to support having the package
build write the *packaged* version in with a easy replace.
Then, when cloud-init reports its version it will include the full
packaged version.

Also modified here are upstream package build files to get that done.

Note part of the trickery in packages/debian/rules.in was to avoid
the 'basic' templater consuming the '$variable' variable names.

LP: #1770712
</content>
</entry>
<entry>
<title>tools: Support adding a release suffix through packages/bddeb.</title>
<updated>2018-05-03T02:03:23+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@ubuntu.com</email>
</author>
<published>2018-05-03T02:03:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=d24057adbc70e7b034b8aca36c5351938b5de74a'/>
<id>urn:sha1:d24057adbc70e7b034b8aca36c5351938b5de74a</id>
<content type='text'>
bddeb already supported passing in a '--release' and that would get
into the changelog line.

If you used bddeb to build packages for a PPA, and built multiple
releases, then you would get the same version for each release, and
launchpad would reject your upload.

The change here means we get a ~16.04.1 (for xenial) suffix on the
dpkg version.  If the distro-info-data package is not installed,
or the release is not known (such as the default "UNRELEASED"),
then you get no suffix.
</content>
</entry>
<entry>
<title>packages/debian/control.in: add missing dependency on iproute2.</title>
<updated>2018-04-24T21:11:48+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@ubuntu.com</email>
</author>
<published>2018-04-24T21:11:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=00d7b9c5f5380d01c76b648877943c4c0cfbcfff'/>
<id>urn:sha1:00d7b9c5f5380d01c76b648877943c4c0cfbcfff</id>
<content type='text'>
Ubuntu minimal images do not have iproute2, so correctly identify
our dependency on it.

LP: #1766711
</content>
</entry>
<entry>
<title>Add missing dependency on isc-dhcp-client to trunk ubuntu packaging.</title>
<updated>2018-03-27T17:07:28+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@ubuntu.com</email>
</author>
<published>2018-03-27T17:07:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=5b9dc4bc6a02acb26d568ab4633661a621d83620'/>
<id>urn:sha1:5b9dc4bc6a02acb26d568ab4633661a621d83620</id>
<content type='text'>
This just correctly adds the missing dependency on isc-dhcp-client.
That package is used via 'dhclient' from cloudinit/net/dhcp.py.

LP: #1759307
</content>
</entry>
<entry>
<title>packages/debian/copyright: remove mention of boto and MIT license</title>
<updated>2017-10-02T20:00:35+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@brickies.net</email>
</author>
<published>2017-10-02T19:20:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=946232bb9eda2f4bc66c4464db9e72d3edfd9900'/>
<id>urn:sha1:946232bb9eda2f4bc66c4464db9e72d3edfd9900</id>
<content type='text'>
boto_utils.py had been removed some time ago, and the current
cloudinit/ec2_utils.py is not based on what was in boto_utils.

We just failed to remove the mention of it from the upstream
debian/copyright. And then put it back in everywhere in recent changes
to get upstream and ubuntu in sync.
</content>
</entry>
<entry>
<title>debian/copyright: dep5 updates, reorganize, add Apache 2.0 license.</title>
<updated>2017-09-29T12:54:48+00:00</updated>
<author>
<name>Joshua Powers</name>
<email>josh.powers@canonical.com</email>
</author>
<published>2017-09-29T12:53:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=d32049993a8e719c52cb491dd8cc7935bfede2d3'/>
<id>urn:sha1:d32049993a8e719c52cb491dd8cc7935bfede2d3</id>
<content type='text'>
The copyright was updated to be lintian clean and reorganized to list the
licenses at the bottom after declaring the metadata and file information.

Add the MIT license to the file.

LP: #1718681
</content>
</entry>
<entry>
<title>cmdline: add collect-logs subcommand.</title>
<updated>2017-09-15T19:46:02+00:00</updated>
<author>
<name>Chad Smith</name>
<email>chad.smith@canonical.com</email>
</author>
<published>2017-09-12T16:27:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=e626966ee7d339b53d2c8b14a8f2ff8e3fe892ee'/>
<id>urn:sha1:e626966ee7d339b53d2c8b14a8f2ff8e3fe892ee</id>
<content type='text'>
Add a new collect-logs sub command to the cloud-init CLI. This script
will collect all logs pertinent to a cloud-init run and store them in a
compressed tar-gzipped file. This tarfile can be attached to any
cloud-init bug filed in order to aid in bug triage and resolution.

A cloudinit.apport module is also added that allows apport interaction.
Here is an example bug filed via ubuntu-bug cloud-init: LP: #1716975.

Once the apport launcher is packaged in cloud-init, bugs can be filed
against cloud-init with the following command:
  ubuntu-bug cloud-init

LP: #1607345
</content>
</entry>
<entry>
<title>upstart: do not package upstart jobs, drop ubuntu-init-switch module.</title>
<updated>2017-09-01T02:01:57+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@brickies.net</email>
</author>
<published>2017-09-01T02:01:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=fa266bf8818a08e37cd32a603d076ba2db300124'/>
<id>urn:sha1:fa266bf8818a08e37cd32a603d076ba2db300124</id>
<content type='text'>
The ubuntu-init-switch module allowed the use to launch an instance that
was booted with upstart and have it switch its init system to systemd and
then reboot itself. It was only useful for the time period when Ubuntu was
transitioning to systemd but only produced images using upstart.

Also, do not run setup with --init-system=upstart. This means that by
default, debian packages built with packages/bddeb will not have upstart
unit files included. No other removal is done here.
</content>
</entry>
<entry>
<title>pkg build ci: Add make ci-deps-&lt;distro&gt; target to install pkgs</title>
<updated>2017-06-14T02:13:34+00:00</updated>
<author>
<name>Chad Smith</name>
<email>chad.smith@canonical.com</email>
</author>
<published>2017-06-07T23:26:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=744e648eaf6325758282ef23bffcc4194faa6bac'/>
<id>urn:sha1:744e648eaf6325758282ef23bffcc4194faa6bac</id>
<content type='text'>
This change adds a couple of makefile targets for ci environments to
install all necessary dependencies for package builds and test runs.

It adds a number of arguments to ./tools/read-dependencies to facilitate
reading pip dependencies, translating pip deps to system package names and
optionally installing needed system-package dependencies on the local
system. This relocates all package dependency and translation logic into
./tools/read-dependencies instead of duplication found in packages/brpm
and packages/bddeb.

In this branch, we also define buildrequires as including all runtime
requires when rendering cloud-init.spec.in and debian/control files
because our package build infrastructure will also be running all unit
test during the package build process so we need runtime deps at build
time.

Additionally, this branch converts
packages/(redhat|suse)/cloud-init.spec.in from cheetah templates to jinja
to allow building python3 envs.
</content>
</entry>
<entry>
<title>tox/build: do not package depend on style requirements.</title>
<updated>2017-05-24T17:30:14+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@brickies.net</email>
</author>
<published>2017-05-24T13:36:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=6b5369be71054a677b89fa8080f7ddd029ce4986'/>
<id>urn:sha1:6b5369be71054a677b89fa8080f7ddd029ce4986</id>
<content type='text'>
When the style/checking dependencies were updated in
test-requirements.txt, the debian package build dependencies created
by ./packages/bddeb were also updated.  Pycodestyle was added to the list
in order to pin its version.  That broke the package build for 16.04.  The
reason for this is simply that python3-pycodestyle is not available in
16.04.

The change here is to remove style dependencies from test-requirements,
and add them to the tox environments directly.  We had previously changed
the package build process to not run pep8 or flake8 simply to avoid having
to code to N different versions of style checkers (3bcb72c593f).

The link between package build and test-requirements still exists, though.
So future breakage can occur if any package is added to
test-requirements.txt (or requirements.txt) if the target distro release
does not have a python3-&lt;packagename&gt; in its archive.

There is also a bit of a tox.ini cleanup here, in that we do not have to
explictly list '-rrequirements.txt' as the setup.py pulls those in.  And
lastly, we drop the -rtest-requirements.txt from the base 'testenv', and
add these test requirements only to environments that need to run test.

Finally, a change to packages/debian/control.in to drop the build
dependencies that were listed for style checking and also a dependency
on iproute2 which was a bad unit test that has been previously fixed.
</content>
</entry>
</feed>
