Alas, this will still fail in the puppetdb case, because it has no `ext/debian` directory in the source tree. In an ideal world (the razor case) we use the source tree to obtain the top-level `debian` directory for packaging, as this PR suggests. But in the puppetdb case, we only have access to `ext/debian` from within the composed the tarball - it doesn't exist in the source tree. As such, with this PR we no longer have a `debian` directory at the top level of `workdir` when we cd in and perform the deb pkg build (it's still in `ext/`, where debian tools won't find it). I sincerely apologize for backwards-ness of this. In order for this PR to work, we need a test here for the existence of a top-level `debian` directory inside `workdir.` If it exists (as it will in almost all cases, razor included) we're fine. If it doesn't we need to check if it exists in `ext` and obtain its contents from there. This is all the result of poor original specifications on my part of what we expected in a project for compatibility with this tooling.