From: Adam Maleszka via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 53840@debbugs.gnu.org
Subject: bug#53840: The current bitlbee-discord@0.4.3 does not work with glib@2.70.2
Date: Mon, 07 Feb 2022 15:40:59 +0100 [thread overview]
Message-ID: <87fsouk9qh.fsf@aol.com> (raw)
In-Reply-To: <87iltrca11.fsf@aol.com>
[-- 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 --]
prev parent reply other threads:[~2022-02-07 14:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fsouk9qh.fsf@aol.com \
--to=bug-guix@gnu.org \
--cc=53840@debbugs.gnu.org \
--cc=adam_maleszka@aol.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).