Merge ~chad.smith/cloud-init:make-deb-cleanup into cloud-init:master
| Status: | Merged | ||||
|---|---|---|---|---|---|
| Merge reported by: | Scott Moser | ||||
| Merged at revision: | not available | ||||
| Proposed branch: | ~chad.smith/cloud-init:make-deb-cleanup | ||||
| Merge into: | cloud-init:master | ||||
| Diff against target: |
175 lines (+40/-64) 2 files modified
Makefile (+4/-0) packages/bddeb (+36/-64) |
||||
| Related bugs: |
|
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Server Team CI bot | continuous-integration | Approve on 2017-04-24 | |
| cloud-init commiters | 2017-04-24 | Pending | |
|
Review via email:
|
|||
Commit Message
make deb: Add devscripts dependency for make deb. Cleanup packages/bddeb.
Add a simple dependency check to "make deb" target for devscripts. Rework a bit of the logic in package/bddeb to drop superfluous STD_NAMED_PACKAGES to avoid duplication of requirements already listed in (test-)
This branch also moves logic inside write_debian_folder which is unneeded up in main. Moving the logic inside write_debian_folder helps cut down on the number of parameters we need to paas into the function.
LP: #1685935
Description of the Change
make deb: Add dependency on devscripts for make deb and minor cleanup of packages/bddeb script.
Add a simple dependency check to "make deb" target for devscripts. Rework a bit of the logic in package/bddeb to drop superfluous STD_NAMED_PACKAGES to avoid duplication of requirements already listed in (test-)
to test:
make deb # will print install instruction on a machine without devscripts
# check final product to make sure dependencies listed haven't changed for the package
dpkg -I cloud-init_all.deb
Note: I didn't address reading build-deps directly from the debian/config.in template as the error message you receive about build-deps seemed fairly straight forward if some build-deps are missing.
| Ryan Harper (raharper) wrote : | # |
Some thoughts on this:
1) we don't want users who apt install cloud-init to also pull down python-devel, gcc and have to compile the extension, so please don't change package deps here
2) this is currently an issue for the tox/venv environment, so let's focus on how to enable the SafeLoader library for that path
3) Once we make (2) an optional testing path (env or parameter can trigger the dep install prior to calling tox/venv which triggers the compile during pip install of the module IIUC), we can have two travis paths, one without the library (representing how things work today) and one *with* the library enabled. This allows us to compare results, unittests all pass, and time it takes to complete (some estimate of the improvement it may provide).
4) With results from (3), we may propose changes to the underlying images (server seed, cloud-image seed, etc) which could ensure that the library is present in the default cloud images.
| Chad Smith (chad.smith) wrote : | # |
Thanks Ryan for the review points, I know you are commenting on the Safeloader proposal which is over here https:/


PASSED: Continuous integration, rev:8be60732fae 6ae5eaae97f3740 79b1c63160187c /jenkins. ubuntu. com/server/ job/cloud- init-ci/ 269/ /jenkins. ubuntu. com/server/ job/cloud- init-ci/ nodes=metal- amd64/269 /jenkins. ubuntu. com/server/ job/cloud- init-ci/ nodes=metal- arm64/269 /jenkins. ubuntu. com/server/ job/cloud- init-ci/ nodes=metal- ppc64el/ 269 /jenkins. ubuntu. com/server/ job/cloud- init-ci/ nodes=metal- s390x/269 /jenkins. ubuntu. com/server/ job/cloud- init-ci/ nodes=vm- i386/269
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
Click here to trigger a rebuild: /jenkins. ubuntu. com/server/ job/cloud- init-ci/ 269/rebuild
https:/