| Age | Commit message (Collapse) | Author |
|---|
|
remove python:Depends macro from the control.in file. This seemed to be
overriding my 'python-json-patch | python-jsonpatch' with whichever
one was installed.
So, we're not getting automatic dependencies on trunk, which is honestly fine.
We'll manage them this way.
|
|
debian bug 717916 renames python-json-patch to python-jsonpatch, so ubuntu
cloud-images with cloud-init may not have python-json-patch.
Just accept either one.
|
|
saucy split cloud-utils into cloud-guest-utils and cloud-image-utils.
The former is in the cloud image, the latter is not, and
we actually need it for growpart which is in the former.
|
|
|
|
These are debian's init scripts as taken from their trunk svn
as of today. Thanks Juerg.
|
|
this way you can now do ./package/bddeb --init-system=sysvinit_deb
|
|
|
|
|
|
|
|
-d pass through '-d' to debuild
--no-cloud-utils don't depend on cloud-utils package (default: False)
These are essential for building on Debian 6, because there are
no python-mocker (build dependency) and cloud-utils (install dependency)
in squeeze and squeeze-backports.
|
|
|
|
It seems like its possible that boto 2.5.2 and below have the lazy loading
metadata dictionary so as a precaution we will always take the hit of
unlazying the metadata dictionary by traversing it which in the non-lazy
dictionary case has no effect (its marginal). This also removes the need
to check the boto version and the dependency on setup tools just for this
case.
|
|
|
|
|
|
newer versions of boto lazily load the metadata from the ec2
metadata service. Here, we:
1. Add a ec2_utils module that checks which version of boto is being used and
under the right versions the metadata dictionary will be expanded.
2. Use this new ec2_utils module in the cloudstack and ec2
datasources as there entrypoints into boto.
3. Add a dependency on python-pkg-resources (from pkg_resources import
parse_version) to determine the boto version.
LP: #1068801
|
|
differently in the rpm spec file template instead
of being joined with the release.
|
|
release number which can be to increment
cloud-init while still maintaining the
'major' cloud-init version number from bzr.
|
|
|
|
use the datetime.now(), the others get
a warning message.
|
|
since this causes rpmbuild to croak with errors like
'changelog not in descending chronological order'.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
rpm builder utility.
|
|
This does a few things:
* changes bddeb to copying out all files created during builddeb.
* link to .dsc file
* remove the '--no-sign' flag, replace that by '-us -uc' command line args
* also know about debuild flag '-S'.
|
|
|
|
The ubuntu packaging uses ~bzrREVNO, just be more like that.
|
|
use python-software-properties or software-properties-common to fullfill
the need for 'apt-add-repository'.
|
|
In cherry picking the cheetah commit, I missed the rename of these files.
packages/debian/changelog => packages/debian/changelog.in
packages/debian/control => packages/debian/control.in
packages/redhat/cloud-init.spec => packages/redhat/cloud-init.spec.in
|
|
At this point there is a mixture of "double hash" cheetah comments and '#*'
cheetah comments.
|
|
LP: #1022101
|
|
|
|
Also, remove the pre-processing of debian/rules. instead use an
environment variable. To build with sysvinit:
$ INIT_SYSTEM=sysvinit ./packages/bddeb
Note, debuild does complain with several errors on sysvinit
building at the moment. Primarily about package installing into
/etc/init.d.
|
|
output of 'make-tarball' now is tarball with name formatted as:
cloud-init-$VERSION~bzr$REVNO.tar.gz
Instead of
cloud-init-$VERSION-$REVNO.tar.gz
The former is desireable for apt at least as the '~' is understood
to mean less than.
This merges revno 569 and 570 from lp:~harlowja/cloud-init/rework
|
|
|
|
This also fixes 'brpm' to address --init-system change that
smoser made to setup.py before the large 'rework' merge.
|
|
|
|
as adjustments due to sysvinit rename.
|
|
This brings with it other changes, and also makes an install
install all of the requisite init files. (ie, cloud-init needs the -local and
the non-local)
|
|
2. Adjust the bddeb to pass this in (as well as other output statement being added)
3. Adjust make-tarball to only archive the bzr versioned files (using --recursive)
|
|
type
which then later affects the installation of certain config files, which then
can be extracted during package creation as needed.
|
|
packaging solutions handle these
2. Get the cloud-init specfile working for the init.d case (with the right postun and post and install sections)
a. It works!!!
|
|
needed to import glob, and use os.symlink, not util.symlink.
Also, here made the 'tar' verbose. if '-v' option given.
|
|
|
|
|
|
|
|
|
