* bug#53840: The current bitlbee-discord@0.4.3 does not work with glib@2.70.2 [not found] <87iltrca11.fsf.ref@aol.com> @ 2022-02-07 8:44 ` Adam Maleszka via Bug reports for GNU Guix 2022-02-07 10:03 ` Liliana Marie Prikler 2022-02-07 14:40 ` Adam Maleszka via Bug reports for GNU Guix 0 siblings, 2 replies; 3+ messages in thread From: Adam Maleszka via Bug reports for GNU Guix @ 2022-02-07 8:44 UTC (permalink / raw) To: 53840 [-- Attachment #1: Type: text/plain, Size: 1728 bytes --] 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? [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 832 bytes --] ^ permalink raw reply [flat|nested] 3+ messages in thread
* bug#53840: The current bitlbee-discord@0.4.3 does not work with glib@2.70.2 2022-02-07 8:44 ` bug#53840: The current bitlbee-discord@0.4.3 does not work with glib@2.70.2 Adam Maleszka via Bug reports for GNU Guix @ 2022-02-07 10:03 ` Liliana Marie Prikler 2022-02-07 14:40 ` Adam Maleszka via Bug reports for GNU Guix 1 sibling, 0 replies; 3+ messages in thread From: Liliana Marie Prikler @ 2022-02-07 10:03 UTC (permalink / raw) To: Adam Maleszka, 53840 Hi, Am Montag, dem 07.02.2022 um 09:44 +0100 schrieb 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: > > [...] > I see three solutions. > * 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. If the patch applies cleanly on 0.4.3, this is to be preferred. > * 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. Upstreams decide what they consider stable enough to tag as release. I don't think pinging them would be too bad, considering they have a history of tagging patch releases :) > * 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. If all else fails, this would count as an "exceptional case" to use commit versioning -- see `info "(guix)Version Numbers"' for more context. Don't forget to clearly explain the reason for the commit you picked in a comment preceding the let-binding, i.e. as in (define bitlbee-discord ;; We use this commit, because ... (let ((commit "deadbeef") (revision "1")) (package ... (version (git-version "0.4.3" revision commit)) ...))) Of course, instead of deadbeef, use the full commit hash. Cheers ^ permalink raw reply [flat|nested] 3+ messages in thread
* bug#53840: The current bitlbee-discord@0.4.3 does not work with glib@2.70.2 2022-02-07 8:44 ` bug#53840: The current bitlbee-discord@0.4.3 does not work with glib@2.70.2 Adam Maleszka via Bug reports for GNU Guix 2022-02-07 10:03 ` Liliana Marie Prikler @ 2022-02-07 14:40 ` Adam Maleszka via Bug reports for GNU Guix 1 sibling, 0 replies; 3+ messages in thread From: Adam Maleszka via Bug reports for GNU Guix @ 2022-02-07 14:40 UTC (permalink / raw) To: 53840 [-- Attachment #1: Type: text/plain, Size: 460 bytes --] Referenced commit is only 6 commits behind, and there aren't any breaking changes. Therefore, for testing purposes, I wrote a custom bitlbee-discord package definition to publish on my channel after reporting this bug. Since then, I have been chatting with my colleagues all the time. In other words, connection works smoothly, no errors are thrown. In my opinion, there is no need to write additional patches. I will submit modified version to guix patches. [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 832 bytes --] ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2022-02-07 14:57 UTC | newest] Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- [not found] <87iltrca11.fsf.ref@aol.com> 2022-02-07 8:44 ` bug#53840: The current bitlbee-discord@0.4.3 does not work with glib@2.70.2 Adam Maleszka via Bug reports for GNU Guix 2022-02-07 10:03 ` Liliana Marie Prikler 2022-02-07 14:40 ` Adam Maleszka via Bug reports for GNU Guix
Code repositories for project(s) associated with this public inbox https://git.savannah.gnu.org/cgit/guix.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).