Hi Dominique,
sorry for late answer.
On 24.10.2012 08:34, Dominique Dumont wrote:
Some time ago I opened a ticket in Pidgin upstream proposing a solution for
this bug[2], without any response yet. We will have to live with the
workaround for now.
Even if upstream adopts this patch, it can't be included in Wheezy.
Another possibility would be to setup pidgin-sipe package to divert
/usr/bin/pidgin and replace it with a script that would set up (or not) the
workaround. This behavior would be tuned by a config file.
Does that sound reasonable ?
I see you already made a NMU implementing the pidgin binary diversion. I don't
have any major problem with the solution, anyway that's what probably most users
do manually to make Sipe work.
On the other hand your change has exactly the same effect as a patch for pidgin
package I proposed[1] and that was promptly rejected by its maintainer, because
it affects SSL behavior of all protocols, not just MSOC/SIPE. So at least
Ari Pollak won't be very happy to see this, I presume :)
My original idea was to get[2] approved by Pidgin upstream, then ask Ari to
apply
it on our current version and upload to Wheezy on a basis that it fixes RC bug.
But
Pidgin guys seem employed by other tasks right now.
BTW we have Sipe 1.13.3 out, so if you are interested in sponsoring new upstream
release for wheezy+1, I can prepare a package for upload (I'm pidgin-sipe
Uploader,
approved by its maintainer, but not DD).
Regards,
Jakub
[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681593
[2] https://developer.pidgin.im/ticket/15247
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
