Bug#704924: debcommit -r should create a signed tag even when there are no uncommitted changes

[Joachim Breitner]

Hi,

On Sun, 7 Apr 2013 14:54:34 -0400 Joey Hess <joeyh at debian.org> wrote:
> Package: devscripts
> Version: 2.12.6
> Severity: normal
> 
> 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.

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

-- 
Joachim "nomeata" Breitner
Debian Developer
  nomeata at debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F
  JID: nomeata at joachim-breitner.de | http://people.debian.org/~nomeata
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/devscripts-devel/attachments/20150713/0e64151d/attachment.sig>