![](https://secure.gravatar.com/avatar/41be34ff24f17922ea199e0f3048d50a.jpg?s=120&d=mm&r=g)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 9 Feb 2011 14:02:21 +0000 Hazel Russman <hazel_russman@yahoo.co.uk> wrote:
What counts as a reportable bug in Crux and what is "upstream" and therefore someone else's responsibility? I ask because there is a critical bug in Sylpheed v.310 (built last week) which seems to be identical to one reported on the Debian list on 2nd February (Bug #611855).
hi, as Sylpheed is my favourite client and i use it everyday i never noticed this kind of problem. Instead, if you use gnupg & gpgme you'll need pinentry-gtk2 too. greetz, - -- GNU/Linux on Power Architecture CRUX PPC - http://cruxppc.org/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iEYEARECAAYFAk1S0L8ACgkQxq34tDeO7LjA9wCfUvOz7/wpTWpfAw7NxOFH5mRa P14AnjfPI6PB8uqchFSJR02g6tmaEVLv =CeyX -----END PGP SIGNATURE-----