Thorsten Glaser wrote:
> Resul Cetin dixit:
> >Personally i doubt that gpg-agent really starts pinentry-kwallet.
> 
> Does it now start it or not?

It seems that it start, but I don't know why it doesn't create that 
/tmp/blablub file. Maybe a mksh specific behavior? The debug output seems to 
indicate that it is, because I see "warning: unknown line 'GETINFO pid'"


> >I think the problem is that it doesn't support `GETINFO pid` correctly.
> > When I remove that from gpg-agent I get the password window and the rest
> > works as expected.
> >
> >So please implement GETINFO correctly for >= gnupg2_2.0.9. I move that up
> > to serious because this makes it complete unusable for everyone using it
> > with gpg-agent.
> 
> Interesting. As I only have gnupg2-2.0.7 at work, I didn’t know about
> this. I shall look into that and RTFM of the newer version.
> 
> However, this is a feature enhancement, and as such wishlist, because
> kwalletcli itself is not impacted, only one of the “tools” that come
> with it. Although I agree it’s more important than wishlist, so I’m
> ok with severity normal. I’ll have to do this upstream though, not in
> Debian, so raising the priority would not help.

No it isn't normal. It breaks other things in Debian and this makes it 
unsuitable for a release. It isn't important that it is not the same tool as 
the name of the package. Please read the policy for more information. Either 
add a
Breaks: gpg-agent (>= 2.0.9)

or remove it from the package or fix it. Depends on you. But don't think that 
it is a good idea to release broken stuff which suggest a specific usage in 
its manpage with a Debian stable. And raising it in Debian helps because then 
release manager know that it is unsuitable for their release and can remove it 
from testing or another person can initiate a NMU to fix it for squeeze or 
when it hasn't entered testing it is blocked to do so.

> I just looked through documentation (especially doc/pinentry.texi) at
> http://cvs.gnupg.org/cgi-bin/viewcvs.cgi/trunk/?root=Pinentry
> and could not find any on GETINFO. Please provide some, otherwise I
> won’t be able to “fix” this.

And I am not in the state to write such documentation for you. But as stated 
before it can clearly shown by modifying gpg-agent that this thing is needed 
or nothing will happen when you run gpg-agent with pinentry-kwallet as 
pinentry-program. Either you get that information from upstream or you must 
reverse engineer the behavior - or remove that program for now from the 
package. But having broken gpg-agent due to that package after the release of 
squeeze is a no go.



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to