#673484 bzr: Unable to sign commits: "no terminal at all requested"

#673484#5
Date:
2012-05-18 23:00:55 UTC
From:
To:
Without any modification in my configuration, Bzr is now rejecting my
signatures to commits:

    $ bzr sign-my-commits
    gwolf@debian.org-20120518225242-3r185pl8dxrvqowf
    gpg: Sorry, no terminal at all requested - can't get input
    bzr: ERROR: Failed to GPG sign data with command "[u'gpg', '--clearsign', '-u', u'gwolf@debian.org', '--no-tty']"

I first noticed this in late April, but have not got around to report
until now, sorry.

#673484#18
Date:
2012-08-02 18:43:13 UTC
From:
To:
tags 673484 + patch
thanks

This bug has been confirmed and patched¹ in Ubuntu's version
2.5.1-0ubuntu2; I have copied over Ubuntu's patch
(debian/patches/07_revert_no_tty), applied to the version currently in
Sid (2.6.0~bzr6526-1), and ran "quilt refresh" on it; I am attaching
the patch here. The patch appears to have been included upstream at
the 2.6.0~beta2 version, according to the latest Ubuntu changelog²,
but it seems to be after the 2.6.0~bzr6526 version we are carrying.

The patch is very easy and non-invasive; I applied it and attempted to
rebuild the package, but after >15 minutes, the build failed during
the tests (on a test that seems completely unrelated to said changes —
bzrlib.tests.per_workingtree.test_eol_conversion.TestEolConversion.test_eol_crlf_dirty)
I am not familiar with the package, but just hand-patching
/usr/share/pyshared/bzrlib/gpg.py with the first hunk of the patch
made it work again.

Please consider uploading a fixed version (and requeting the Release
Team to include it in Wheezy), as having the commits signed is an
important feature for many, and we will be regressing on it otherwise.

Thanks,

¹ https://bugs.launchpad.net/bzr/+bug/1014570

² https://launchpad.net/ubuntu/+source/bzr/2.6.0~beta2-0ubuntu1