Control: severity -1 important Hi Santiago!
On Sun, 2014-09-21 at 20:55:45 +0200, Santiago Vila wrote: > Package: dpkg-dev > Version: 1.17.13 > Severity: serious > When trying to build a trivial package on another machine via ssh, > I get this: > You need a passphrase to unlock the secret [...] > [...] > [...] > > pinentry-curses: no LC_CTYPE known - assuming UTF-8 > pinentry-curses: no > LC_CTYPE known - assuming UTF-8 > > pinentry-curses: no LC_CTYPE known - assuming UTF-8 > pinentry-curses: no LC_CTYPE known - assuming > UTF-8 > Then the keyboard becomes unresponsive and I have to break the process > using Control+C. Thanks for the info about this happening on a virtual console, and nicely spotted bug. :) > I'm using Xfce on jessie, and I'm building the package on another > jessie machine where I don't have XOrg installed. > > Maybe this is a bug in another package, but even in such case it > would be great if dpkg-dev could detect in advance that this is going > to happen. The package which was being built could have been non-trivial, > which means the user could have lost a lot of time because of this. This is a bug in dpkg-buildpackage when interacting with gpg2 and w/o an X display available. I've lowered the severity due to the recentish refactoring in dpkg-buildpackage, that delayed the signing to the end of the process, where nothing else is required to run (except for the hooks), which means that a Ctrl+C and a debsign should give you the correct build artifacts, so this ends up being just an annoyance. (For now you could also tell dpkg-buildpackage to use gpg instead of gpg2 with the -p option.) In any case the problem stems from dpkg-buildpackage piping the stuff to sign to gpg2 stdandard input and I assume then it does not know how to find the locale and terminal information. I'll be fixing this for the imminent dpkg 1.17.14 upload. Thinking about it a bit more, I guess pinentry should also get a bug report because the staircased output and the fact that it sits there w/o prompting should be considered erroneous behavior probably, instead of just bailing out. Thanks, Guillem -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
