If the version of a package is 0, then mk-build-deps creates
$src-build-deps_1.0_all.deb instead of $src-build-deps_0_all.deb. If -i
is used, then it additionally attempts to install
$src-build-deps_0_all.deb, and this fails because of the previous
unexpected output.
AIUI, 0 is a perfectly valid package version according to Debian Policy,
and so should work.
This came up because I used 0 in a template. Of course it wouldn't last
long in a real package!
Minimal steps to reproduce:
# mkdir debian
# cat > debian/changelog
test (0) UNRELEASED; urgency=medium
* Test mk-build-deps