The message you're talking about is generated inside libotr 3.2.0, so this
needs an API change in libotr and a corresponding change in pidgin-otr to fix.
I see that there's movement toward an OTR 4 on the upstream repos, so perhaps
it can be fixed eventually. Of course changing the library API means that
every app and plugin built on top of libotr will also need to be updated...
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
