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.
(cherry picked from commit 95e1d91d5d)
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.
(cherry picked from commit ba0b91b51b)
* 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
