bug#53840: The current bitlbee-discord@0.4.3 does not work with glib@2.70.2

[Adam Maleszka]

I'm trying to configure bitlbee-discord in order to write on Discord
using ERC in Emacs. Unfortunately, every time I open connection to
Discord, this error is thrown:

discord - Login error: Failed to switch to websocket mode

Actually, it is a well-known issue caused by breaking changes in the new
version of glib (2.70.X):
https://github.com/sm00th/bitlbee-discord/issues/226 A fix is introduced
with commit 607f9887ca85f246e970778e3d40aa5c346365a7:
https://github.com/sm00th/bitlbee-discord/commit/607f9887ca85f246e970778e3d40aa5c346365a7
However, the commit is far newer than the 0.4.3 tag, thus
bitlbee-discord@0.4.3 is unusable with glib@2.70.2.

I see three solutions.

* The first solution --- upgrade bitlbee-discord

This solution involves upgrading bitlbee-discord to the specified
commit. I don't think it will make the package more unstable, especially
after this post:
https://github.com/sm00th/bitlbee-discord/issues/118#issuecomment-606856620

However, it would be good to stick to convention and only introduce
"stable" release versions.

* The second solution --- requesting a new release

That said, I think it would be a good idea to request a new release
from the author, particularly as glib@2.70.X is becoming more common.

However, there is no certainty that the new release would be stable,
though.

* The third solution --- patching current release

Last but not least, what about writing a patch for the current release?
The mentioned commit does not seem complicated. I think it is the best
solution, because it gives us more control while preserving the
stability of the release. However, it is always extra work.

Which solution do you think is the best?

signature.asc
Description: PGP signature