FYI, the bugfix was not released with milestone 2.5.4, but will be with
version 2.5.5.
Thanks,
Ludovico
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Applied upstream http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=508857
Regards,
Ludovico
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Hi,
Ari Pollak wrote:
> FWIW, I have no plans to apply these patches independently of upstream,
> especially before lenny gets released.
The useful patch is only one
http://developer.pidgin.im/attachment/ticket/7761/nullptr-noleak.patch
there others are win32 patches.
Moreover it would be useful
forwarded 508857 http://developer.pidgin.im/ticket/7761
thanks
FWIW, I have no plans to apply these patches independently of upstream,
especially before lenny gets released.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
Package: libpurple0
Version: 2.5.2-1
Severity: normal
Tags: patch upstream
If the prefs code of libpurple is re-initialized (e.g. by calling
purple_prefs_uninit() and than purple_prefs_init()),
the prefs data structure is not re-initialized properly.
This bug has already been reported upstream at
5 matches
Mail list logo
