[Bug 1014570] Re: bzr: Unable to sign commits: "no terminal at all requested"

[Jelmer Vernooij]

** Changed in: bzr
    Milestone: None => 2.6b2

** Changed in: bzr (Ubuntu Precise)
    Milestone: None => precise-updates

** Changed in: bzr (Ubuntu Quantal)
    Milestone: None => quantal-alpha-3

** Description changed:

  Imported from Debian bug http://bugs.debian.org/673484:
- 
- Package: bzr
- Version: 2.6.0~bzr6522-1
- Severity: normal
  
  Without any modification in my configuration, Bzr is now rejecting my
  signatures to commits:
  
-     $ bzr sign-my-commits
-     gwolf at 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 at debian.org', '--no-tty']"
+     $ bzr sign-my-commits
+     gwolf at 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 at debian.org', '--no-tty']"
  
- I first noticed this in late April, but have not got around to report
- until now, sorry.
+ This bug was introduced in 2.5.1 and later snapshots of bzr 2.6. 2.5.1
+ was SRU'ed into precise.
  
- -- System Information:
- Debian Release: wheezy/sid
-   APT prefers unstable
-   APT policy: (500, 'unstable')
- Architecture: amd64 (x86_64)
+ [Impact]
+ This affects users of the 2.5.1 SRU who sign commits on the command-line without a GPG agent. The proposed fix reverts the use of --no-tty which will reintroduce bug 847388, which was also present long before 2.5.1.
  
- Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores)
- Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
- Shell: /bin/sh linked to /bin/dash
+ [Test Case]
+ Install bzr and gpg. Make sure there is no active GPG agent ("unset GPG_AGENT_INFO") and try to sign a few commits ("bzr sign-my-commits"). This should succeed, and prompt for a GPG password on the terminal.
  
- Versions of packages bzr depends on:
- ii  python         2.7.2-10
- ii  python-bzrlib  2.6.0~bzr6522-1
- 
- Versions of packages bzr recommends:
- ii  python-gpgme  0.2-2
- 
- Versions of packages bzr suggests:
- pn  bzr-doc              <none>
- pn  bzr-gtk              <none>
- pn  bzr-svn              <none>
- pn  bzrtools             2.5+bzr786-2
- pn  python-bzrlib.tests  <none>
- 
- -- no debconf information
+ [Regression Potential]
+ This is a revert of a problematic change in a SRU. We'll definitely reintroduce bug 847388, but that is a bug that has been present for a long time and only affects a really limited amount of users.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to bzr in Ubuntu.
https://bugs.launchpad.net/bugs/1014570

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

Status in Bazaar Version Control System:
  In Progress
Status in “bzr” package in Ubuntu:
  Fix Released
Status in “bzr” source package in Precise:
  In Progress
Status in “bzr” source package in Quantal:
  Fix Released
Status in “bzr” package in Debian:
  Confirmed

Bug description:
  Imported from Debian bug http://bugs.debian.org/673484:

  Without any modification in my configuration, Bzr is now rejecting my
  signatures to commits:

      $ bzr sign-my-commits
      gwolf at 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 at debian.org', '--no-tty']"

  This bug was introduced in 2.5.1 and later snapshots of bzr 2.6. 2.5.1
  was SRU'ed into precise.

  [Impact]
  This affects users of the 2.5.1 SRU who sign commits on the command-line without a GPG agent. The proposed fix reverts the use of --no-tty which will reintroduce bug 847388, which was also present long before 2.5.1.

  [Test Case]
  Install bzr and gpg. Make sure there is no active GPG agent ("unset GPG_AGENT_INFO") and try to sign a few commits ("bzr sign-my-commits"). This should succeed, and prompt for a GPG password on the terminal.

  [Regression Potential]
  This is a revert of a problematic change in a SRU. We'll definitely reintroduce bug 847388, but that is a bug that has been present for a long time and only affects a really limited amount of users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bzr/+bug/1014570/+subscriptions