It's common to have debcommit -r be run as part of the release process.
However, if a commit has already been made of everything in the source
tree, then debcommit makes no commit, and it seems that in this case,
it also does not make a signed tag. Result is a release with a missing
tag, which is never good. debcommit -r should always tag the most recent
commit as the release tag, unless the release tag already exists.

I have only verified this happens with git, but it seems likely to
also affect other VCS.
--- /etc/devscripts.conf ---

--- ~/.devscripts ---
DEBCHANGE_RELEASE_HEURISTIC=changelog
DEBCOMMIT_SIGN_TAGS=yes
DEBSIGN_KEYID=2512E3C7
DEBSIGN_SIGNLIKE=gpg
DEBSIGN_MAINT=joeyh@debian.org
DEBCHANGE_AUTO_NMU=no

Hi,

indeed, I am affected by this as well.

The problem is that debcommit aborts if the commit fails (which is a
good thing), but does not distinguishingthis from failing due to no
changes.

A solution might be to use git status(?) to check if any of the
selected files are modified and if not, simply skip the commit.

Any volunteers in the Debian Haskell Group?

Joachim