Merge lp:~smoser/maas/packaging.1231693 into lp:~maas-maintainers/maas/packaging
Status: | Merged |
---|---|
Approved by: | Andres Rodriguez |
Approved revision: | 204 |
Merged at revision: | 204 |
Proposed branch: | lp:~smoser/maas/packaging.1231693 |
Merge into: | lp:~maas-maintainers/maas/packaging |
Diff against target: |
55 lines (+9/-12) 2 files modified
debian/control (+1/-1) debian/maas-dhcp.maas-dhcp-server.upstart (+8/-11) |
To merge this branch: | bzr merge lp:~smoser/maas/packaging.1231693 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Andres Rodriguez (community) | Approve | ||
Launchpad code reviewers | Pending | ||
Review via email: mp+188932@code.launchpad.net |
Commit message
revert maas-dhcp-server upstart job to quantal-
This knowingly stops saucy level packages from running with
isc-dhcpd-server from precise. That is intended because we are more
interested in supporting isc-dhcpd-server from the cloud-archive which
will be a newer version.
Description of the change
One of these 2 branches can be chosen. Either
a.
https:/
or
https:/
I'm really OK with either. One is more complex but supports more scenarios
the other (this one) is a simpler upstart job that only supports one version of isc-dhcp (quantal-saucy version).
This lgtm! Provided that the backport to precise is no longer going to use the DHCP from precise (but rather a backported one) then I approve these changes.