(mirror of https://github.com/vyos/vyos-cloud-init.git) https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=20.1 2020-02-20T17:11:04+00:00 2020-02-20T17:11:04+00:00 Daniel Watkins oddbloke@ubuntu.com 2020-02-20T17:11:04+00:00 urn:sha1:4ad5c5d058cc9501ef2f294cb6430d9ffe372e7d * tools/read-version: don't enforce version parity in release branch CI We have a bootstrapping problem with new releases, currently. To take the example of 20.1: the branch that bumps the version fails CI because there is no 20.1 tag for it to use in read-version. Previously, this was solved by creating a tag and pushing it to the cloud-init repo before the commit landed. However, we have GitHub branch protection enabled, so the commit that needs to be tagged is not created until the pull request lands in master. This works around this problem by introducing a very specific check: if we are performing CI for an upstream release branch, we skip the read-version checking that we know will fail. * tools/make-tarball: add --version parameter When using make-tarball as part of a CI build of a new upstream release, the version it determines is inconsistent with the version that other tools determine. Instead of encoding the logic here (as well as in Python elsewhere), we add a parameter to allow us to set it from outside the script. * packages/bddeb: handle missing version_long in new version CI If we're running in CI for a new upstream release, we have to use `version` instead of `version_long` (because we don't yet have the tag required to generate `version_long`). 2018-05-03T02:03:23+00:00 Scott Moser smoser@ubuntu.com 2018-05-03T02:03:23+00:00 urn:sha1:d24057adbc70e7b034b8aca36c5351938b5de74a 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. 2018-05-01T21:38:41+00:00 Scott Moser smoser@ubuntu.com 2018-05-01T21:38:41+00:00 urn:sha1:26fbb1a0ce89451edad83a47054cacb6dd7b6dcc If you built packages with 'bddeb', each time it would create a new tarball with make-tarball. If you then tried to upload two different tarballs to launchpad (to a PPA), it would reject the second as the orig tarball already existed. This just supports looking in some places for a orig tarball and re-using if it is found. 2017-09-07T19:22:54+00:00 Scott Moser smoser@brickies.net 2017-08-29T13:59:20+00:00 urn:sha1:409918f9ba83e45e9bc5cc0b6c589e2fc8ae9b60 During boot, the usage of /tmp is not safe. In systemd systems, systemd-tmpfiles-clean may run at any point and clear out a temp file while cloud-init is using it. The solution here is to use /run/cloud-init/tmp. LP: #1707222 2017-09-01T02:01:57+00:00 Scott Moser smoser@brickies.net 2017-09-01T02:01:57+00:00 urn:sha1:fa266bf8818a08e37cd32a603d076ba2db300124 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. 2017-06-14T23:11:43+00:00 Chad Smith chad.smith@canonical.com 2017-06-14T23:11:43+00:00 urn:sha1:b23d9d7c5c112612dbaaf8c8371c9e735500b2eb read-dependencies now takes --test-distro param to indicate we want to install all system package depenencies to allow for testing and building for our continous integration environment. It allows us to install all needed deps on a fresh system with: python3 ./tools/read-dependencies --distro ubuntu --test-distro [--dry-run]. Additionally read-dependencies now looks at what version of python is running the script (py2 vs p3) and opts to install python 2 or 3 system deps respectively. This behavior can still be overridden with python3 ./tools/read-dependencies ... --python-version 2. There are also some distro-specific packaging and test dependencies, like devscripts, tox and libssl-dev on debian or ubuntu. Those pkg dependencies have now been broken out from common pkg deps to avoid trying to install them on centos/redhat/suse. 2017-06-14T02:13:34+00:00 Chad Smith chad.smith@canonical.com 2017-06-07T23:26:52+00:00 urn:sha1:744e648eaf6325758282ef23bffcc4194faa6bac 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. 2017-05-16T20:42:56+00:00 Chad Smith chad.smith@canonical.com 2017-04-24T17:57:04+00:00 urn:sha1:8f176479c0282e564a87036704c515f746aab3a9 Add a simple dependency check to "make deb" target for devscripts. Rework a bit of the logic in package/bddeb to drop superfluous STD_NAMED_PACKAGES to avoid duplication of requirements already listed in (test-)?requiremets.txt. All "standard" packages can be assumed to have either python3- or python- prefix if not listed in NONSTD_NAMED_PACKAGES. This branch also moves logic inside write_debian_folder which is unneeded up in main. LP: #1685935 2016-11-03T13:27:54+00:00 Scott Moser smoser@brickies.net 2016-11-03T13:27:54+00:00 urn:sha1:59d4ba565718dba1a6c7d61cb5e8d5aa505101fa When we added coverage to test-requirements, we need to add the mapping to package name. Without it there, bddeb complains that it cannot translate the dependency. Note, though, that the Makefile does not invoke nose with coverage. So we don't actually use that dependency. 2016-08-31T21:10:29+00:00 Scott Moser smoser@brickies.net 2016-08-31T21:10:29+00:00 urn:sha1:2ddaa93b870bb0953a5a23b0eab155b21dd05a0f ./packages/bddeb --release=xenial that will get you a changelog with Distribution of xenial rather than UNRELEASED.