Merge lp://staging/~ev/ubuntu-ci-services-itself/cli-packaging into lp://staging/ubuntu-ci-services-itself

PASSED: Continuous integration, rev:313
http://s-jenkins.ubuntu-ci:8080/job/uci-engine-ci/297/
Executed test runs:

Click here to trigger a rebuild:
http://s-jenkins.ubuntu-ci:8080/job/uci-engine-ci/297/rebuild

I'm not a packaging expert so I'm mostly learning here ;)

9 + if os.path.exists(component_dir):
10 + os.chdir(component_dir)
11 + else:
12 + # We're probably in the component dir (like when we're called from the
13 + # Debian package build).
14 + component_dir = os.getcwd()

I thought setup.py and debian packaging where completely separate so I don't quite get why/when this is involved, can you shed some light on what commands you use to trigger that ?

72 === added file 'ci-utils/debian/copyright'
73 --- ci-utils/debian/copyright 1970-01-01 00:00:00 +0000
74 +++ ci-utils/debian/copyright 2014-03-05 11:28:37 +0000

Oooh, that's all it takes ! Will fix my packages accordingly ;)

107 +override_dh_python2:
108 + dh_python2 --no-guessing-deps

What does that do ?

The rest looks similar to what I use myself so I can only approve ;)

On 5 March 2014 11:53, Vincent Ladeuil <email address hidden> wrote:
> 9 + if os.path.exists(component_dir):
> 10 + os.chdir(component_dir)
> 11 + else:
> 12 + # We're probably in the component dir (like when we're called from the
> 13 + # Debian package build).
> 14 + component_dir = os.getcwd()
>
> I thought setup.py and debian packaging where completely separate so I don't quite get why/when this is involved, can you shed some light on what commands you use to trigger that ?

setup.py is called by debhelper as part of the package build.
`debian/rules binary` if you want to manually move through it.

On 5 March 2014 11:53, Vincent Ladeuil <email address hidden> wrote:
> 107 +override_dh_python2:
> 108 + dh_python2 --no-guessing-deps
>
> What does that do ?

Added a comment to address this.

Out of curiosity: is it not possible to have a single debian directory at the root of the project that could have built 2 packages, uci-cli and uci-utils?

It is. I thought this would be a bit cleaner, as when we decoupled
these into their own branches we could just carry their debian
directories with them. However, I'm now running into problems with
bzr-builder that make me think a single debian/ in the root dir is the
way forward.

On 5 March 2014 15:51, Andy Doan <email address hidden> wrote:
> Out of curiosity: is it not possible to have a single debian directory at the root of the project that could have built 2 packages, uci-cli and uci-utils?
> --
> https://code.launchpad.net/~ev/ubuntu-ci-services-itself/cli-packaging/+merge/209428
> You are the owner of lp:~ev/ubuntu-ci-services-itself/cli-packaging.