Arjen Balfoort: > Package: debhelper > Version: 13.2.1 > Severity: normal > X-Debbugs-Cc: [email protected] > > Dear Maintainer, > > * What led up to the situation? > I needed a package name change of a pybuild package. > > * What exactly did you do (or not do) that was effective (or ineffective)? > I added the configuration of the transitional package to the package > control > file. > > * What was the outcome of this action? > dh_missing threw the following warning on all files: > dh_missing: warning: usr/bin/hello exists in debian/tmp but is not > installed to > anywhere > > Resulting in two empty packages: the new named package and the old > (transitional) package. > > * What outcome did you expect instead? > A complete package with a new name and an empty transitional package > with the > old name. > > Note: after removing the configuration of the transitional package the > new package was built correctly. > > > > [...]
Hi, You have hit an intentional design choice from debhelper - one that I am admittedly have been considering to change for exactly this the problem you are running into. What happens is that debhelper special-cases "single-binary packages" (namely dh_auto_install defaults to "--destdir=debian/<package>" rather than --destdir=debian/tmp" in this case). In compat 13, the dh_missing warning becomes an error preventing you from accidentally uploading the two empty packages - but it is still an unpleasant experience. If you need a second /empty/ binary, then you can override dh_auto_install and set dh_auto_install --destdir=debian/<package> for now. I am leaving this open until I figure out what to do about this corner case. Thanks, ~Niels
