Merge lp:~javier.collado/utah/bug1042895 into lp:utah
Status: | Merged |
---|---|
Merged at revision: | 699 |
Proposed branch: | lp:~javier.collado/utah/bug1042895 |
Merge into: | lp:utah |
Diff against target: |
152 lines (+53/-35) 4 files modified
Makefile (+5/-2) debian/control (+2/-1) debian/utah.install (+1/-1) utah/provisioning/provisioning.py (+45/-31) |
To merge this branch: | bzr merge lp:~javier.collado/utah/bug1042895 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Max Brustkern (community) | Approve | ||
Review via email: mp+128185@code.launchpad.net |
Description of the change
This branch adds a few changes on top of lp:~nuclearbob/utah/internal-jsonschema to get the python-jsonschema package into the utah package at build time instead of at installation time. This means that when utah package is installed, the server can install the client in a machine that doesn't have access to the PPA where the python-jsonschema is available.
For more information, have a look at the discussion in this merge proposal:
https:/
For a log of of a successful build, have a look at this link (explanation below):
https:/
The build above happened in my PPA (ppa:javier.
RUN: /usr/share/
Overriding sources.list in build-17aa1ff55
Later, the build-depends in the packages is retrieved:
Build-Depends: debhelper (>= 7.0.50~), devscripts, python-all, python-sphinx, python-jsonschema (>= 0.5~)
and the right version of the package is installed:
Setting up python-jsonschema (0.5-0~ppa1) ...
When the package builds, the Makefile commands get the binary package to make it available for the packaging:
apt-get download python-jsonschema
Get:1 Downloading python-jsonschema 0.5-0~ppa1 [10.3 kB]
Fetched 10.3 kB in 0s (0 B/s)
For the utah PPAs, since the package is available in both of them, the configuration to add a PPA dependency won't be needed as the PPA in which the package is build seems to be added automatically to the sources, so there shouldn't be any problem in building the package in any of them.
I'm still reviewing this, but on lines 41-43 of the merge, a number of dependencies are added to utah which are also dependencies of utah-client (bzr, git, python-yaml.) I think we had a previous merge where we determined that dependencies of utah-client don't also need to be dependencies of utah, since utah depends on utah-client. I'm guessing this was branched off before that happened. If it would be helpful to find the old merge, let me know, and I can do that.