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

[GNU bug Tracking System]

Your message dated Thu, 10 Feb 2022 23:28:06 +0100
with message-id <874k562w7d.fsf_-_@gnu.org>
and subject line Re: bug#53850: [PATCH] gnu: bitlbee-discord: Update to 
0.4.3-1.607f988
has caused the debbugs.gnu.org bug report #53840,
regarding The current bitlbee-discord@0.4.3 does not work with glib@2.70.2
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
53840: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=53840
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems

--- Begin Message --- Subject: The current bitlbee-discord@0.4.3 does not work with glib@2.70.2 Date: Mon, 07 Feb 2022 09:44:27 +0100 User-agent: mu4e 1.6.10; emacs 28.0.91

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

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#53850: [PATCH] gnu: bitlbee-discord: Update to 0.4.3-1.607f988
>
>
>
>
> Date: 
>
> Thu, 10 Feb 2022 23:28:06 +0100
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
>
>
>
>
> Hi,
>
> Adam Maleszka <adam_maleszka@aol.com> skribis:
>
> > From b307d3e8bccbef9436502b10192960441f684687 Mon Sep 17 00:00:00 2001
> > From: Adam Maleszka <adam_maleszka@aol.com>
> > Date: Mon, 7 Feb 2022 16:47:56 +0100
> > Subject: [PATCH] gnu: bitlbee-discord: Update to 0.4.3-1.607f988
> >
> > ---
> >  gnu/packages/messaging.scm | 85 +++++++++++++++++++++-----------------
> >  1 file changed, 48 insertions(+), 37 deletions(-)
>
> I added a commit log and applied it.
>
> Thanks!
>
> Ludo’.
>
>
> --- End Message ---