This bug was fixed in the package purple-discord -
0.9.2020.04.05.git.db7dc79-1
---------------
purple-discord (0.9.2020.04.05.git.db7dc79-1) unstable; urgency=high
* New upstream snapshot
- Adds workaround for crashes in ssl_nss_read (Closes: #955635)
-- Paul Wise <[email protected]> Sun, 05 Apr 2020 08:09:21 +0800
purple-discord (0.9.2020.03.10.git.4e71974-1) unstable; urgency=high
* New upstream snapshot
- Fixes issues with channel user lists and null names
-- Paul Wise <[email protected]> Thu, 12 Mar 2020 11:19:53 +0800
purple-discord (0.9.2020.02.14.git.d47f0bc-1) unstable; urgency=medium
[ Paul Wise ]
* New upstream snapshot
* Bump Standards-Version, no changes needed
[ lintian-brush ]
* Remove obsolete field Name from debian/upstream/metadata (already
present in machine-readable debian/copyright).
-- Paul Wise <[email protected]> Sat, 29 Feb 2020 14:05:33 +0800
** Changed in: purple-discord (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872309
Title:
Sync purple-discord 0.9.2020.04.05.git.db7dc79-1 (universe) from
Debian unstable (main)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/purple-discord/+bug/1872309/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
