Your message dated Sat, 09 May 2020 11:53:52 +0100
with message-id
<fd7fa4d56896c35aab49a5a51cb69727dc60e87a.ca...@adam-barratt.org.uk>
and subject line Closing requests included in 10.4 point release
has caused the Debian Bug report #958887,
regarding buster-pu: package purple-discord/0.9.2019.02.07.git.e5d9627-1
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.)
--
958887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958887
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: buster
User: [email protected]
Usertags: pu
A change to the Discord service causes crashes in purple-discord. There
is a workaround for this issue in unstable that I would like to have in Debian
buster. I have uploaded the package to Debian buster just now and I attach the
debdiff for review.
--
bye,
pabs
https://wiki.debian.org/PaulWise
diff -Nru purple-discord-0.9.2019.02.07.git.e5d9627/debian/changelog purple-discord-0.9.2019.02.07.git.e5d9627/debian/changelog
--- purple-discord-0.9.2019.02.07.git.e5d9627/debian/changelog 2019-02-09 10:54:10.000000000 +0800
+++ purple-discord-0.9.2019.02.07.git.e5d9627/debian/changelog 2020-04-26 17:47:55.000000000 +0800
@@ -1,3 +1,9 @@
+purple-discord (0.9.2019.02.07.git.e5d9627-1+deb10u1) buster; urgency=medium
+
+ * Backport workaround for crashes in ssl_nss_read (Closes: #955635)
+
+ -- Paul Wise <[email protected]> Sun, 26 Apr 2020 17:47:55 +0800
+
purple-discord (0.9.2019.02.07.git.e5d9627-1) unstable; urgency=medium
* New upstream snapshot
diff -Nru purple-discord-0.9.2019.02.07.git.e5d9627/debian/patches/series purple-discord-0.9.2019.02.07.git.e5d9627/debian/patches/series
--- purple-discord-0.9.2019.02.07.git.e5d9627/debian/patches/series 1970-01-01 08:00:00.000000000 +0800
+++ purple-discord-0.9.2019.02.07.git.e5d9627/debian/patches/series 2020-04-26 17:47:55.000000000 +0800
@@ -0,0 +1 @@
+workaround-ssl_nss_read-crashes.patch
diff -Nru purple-discord-0.9.2019.02.07.git.e5d9627/debian/patches/workaround-ssl_nss_read-crashes.patch purple-discord-0.9.2019.02.07.git.e5d9627/debian/patches/workaround-ssl_nss_read-crashes.patch
--- purple-discord-0.9.2019.02.07.git.e5d9627/debian/patches/workaround-ssl_nss_read-crashes.patch 1970-01-01 08:00:00.000000000 +0800
+++ purple-discord-0.9.2019.02.07.git.e5d9627/debian/patches/workaround-ssl_nss_read-crashes.patch 2020-04-26 17:47:55.000000000 +0800
@@ -0,0 +1,18 @@
+Description: Wrap all purple_ssl_read's to prevent segfaults elsewhere
+Origin: https://github.com/EionRobb/purple-discord/compare/4e71974...db7dc79.diff
+Bug: https://github.com/EionRobb/purple-discord/issues/288
+Bug-Debian: https://bugs.debian.org/955635
+Author: Eion Robb <[email protected]>
+Applied-Upstream: yes
+--- a/libdiscord.c
++++ b/libdiscord.c
+@@ -50,6 +50,9 @@
+
+ #include "markdown.h"
+
++// Prevent segfault in libpurple ssl plugins
++#define purple_ssl_read(a, b, c) ((a) && (a)->private_data ? purple_ssl_read((a), (b), (c)) : 0)
++
+ #define DISCORD_PLUGIN_ID "prpl-eionrobb-discord"
+ #ifndef DISCORD_PLUGIN_VERSION
+ #define DISCORD_PLUGIN_VERSION "0.1"
signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Package: release.debian.org
Version: 10.4
Hi,
Each of the uploads referred to by these bugs was included in today's
stable point release.
Regards,
Adam
--- End Message ---
