Your message dated Sun, 27 Jan 2013 12:14:30 -0500
with message-id <[email protected]>
and subject line Re: Bug#699067: libpurple0: pidgin/purple does not integrate
with ca-certificates
has caused the Debian Bug report #699067,
regarding libpurple0: pidgin/purple does not integrate with ca-certificates
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
699067: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699067
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libpurple0
Version: 2.10.6-2
Severity: wishlist
Hi.
In a way,.. this issue is kinda upstream, well at least it's blocked by an
upstram
issue which I've reported (https://developer.pidgin.im/ticket/15485) and closely
related to it.
In Debian, packages should ideally use the certificates provided by
the ca-certificates package, which is for pidgin currently not the case.
The afforementioned upstream bug #15485 requests additional CA cert locations
to be
specifyable (both, on a per user and a system-wide basis).
Once this should be implemented, we should think about whether and how we might
use this for a better integration with ca-certificates.
One way could be a debconf question, where we ask admins whether they want to
automatically add the certs in /etc/ssl/certs to the trusted ones.
And/or one could document this in README.Debian.
Cheers,
Chris.
--- End Message ---
--- Begin Message ---
Pidgin/libpurple is built with --with-system-ssl-certs=/etc/ssl/certs,
so ca-certificates should be used.
--- End Message ---
