These values are used by software updaters to show which applications
are being updates to the user. In the case of Ubuntu, it will now show
clearly that it is updating Ansible instead of a radically simple IT
automation platform.
It's almost always preferable to clone by way of https:// rather than
using the bare git:// protocol. Not only does https:// provide
stronger guarantees it also plays nicer with corporate proxies, etc.
* Adding acs module
* linter issue
* Reduce the VM Size for the int. tests
* Short the name of the cluster
* Fixing the asserts and title
* Fixing VM Scale count in int. tests
* Changing the location of the tests
* trying eastus2
* disabling acs CI tests until stabilized
* Adapt azure_rm_resource_group to azure 2.0.0 + azure Cli support
* Fix exceptions in Azure ARM plugins
* update azure_rm_networkinterface documention to reflect required params
* change state param to not required for docs in azure_rm_subnet
* fix import to reflect azure==2.0.0 changes
* add aliases and fix docs for azure_rm_storageblob
* add resource_group_name alias to azure_rm_storageaccount_facts
* fix import bug due to change in azure==2.0.0
* fix args bug and enum modules issue
* update docs to reflect azure==2.0.0
* pin management clients to a specific api_version
* update docs to reflect the new azure-ansible-base python package
* add fallback for older api resource group listing
* rework azure dependencies installation
* refactor path joining to a cross-plat solution
* Code smell test for iteritems and itervalues
* Change the keydict object in authorized_keys so it doesn't throw a false postive
keydict is a bad data structure anyway. We don't use the iteritems and
itervalues methods so just disable them so that the code-smell tests do
not trigger on it.
* Change release templates so they work with py3
* Build debs with pbuilder
* Update README in packaging/debian
* Add Dockerfile for building debs
* Add local_deb makefile target - Allows users to build debs using locally installed dependencies. This was the `deb` target before moving to pbuilder.
The previous commit resolved the debian build problem, but was building
packages with the stable version. A development version is required in
the changelog to properly build development DEB packages.
Remove 1.8 debian/changelog entry with a date of "TBD" as this causes
the debian build process to fail. We can add this back with the 1.8
release becomes a reality, or add it back now with a valid date in the
future.
The ansible PyPi package, and RPM both require crypto>=2.6. This change
carries that dependency into the ansible DEB package. Note, for
ubuntu-12.04, this dependency is only satisfied by a PPA. Users
installing from 'ppa:ansible/ansible' will not be affected..
Updates to Makefile include:
* add targets: deb-src, deb-src-upload, deb-upload
* add variables to control DEB building: DEBUILD_OPTS, DPUT_OPTS, DEB_PPA, DEB_DIST, DEB_RELEASE
* create deb files for all release values in DEB_DIST
Several updates to packaging/debian/*
* Updated control file
* Whitespace/formatting of changelog
Add deb-build to .gitignore
`make rpm` gives these warnings:
warning: bogus date in %changelog: Thu Feb 28 2014 Michael DeHaan <michael.dehaan@g.c> - 1.5-0
warning: bogus date in %changelog: Thu Jul 05 2013 Michael DeHaan <michael.dehaan@g.c> - 1.2-2
warning: bogus date in %changelog: Thu Aug 6 2012 Michael DeHaan <michael.dehaan@g.c> - 0.7-0
RPM build errors:
bogus date in %changelog: Thu Feb 28 2014 Michael DeHaan <michael.dehaan@g.c> - 1.5-0
bogus date in %changelog: Thu Jul 05 2013 Michael DeHaan <michael.dehaan@g.c> - 1.2-2
bogus date in %changelog: Thu Aug 6 2012 Michael DeHaan <michael.dehaan@g.c> - 0.7-0