From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Christopher Baines <mail@cbaines.net>
Cc: 40063-done@debbugs.gnu.org, Adrian Fullmer <adrianfullmer@yahoo.com>
Subject: bug#40063: [PATCH 1/2] gnu: bitlbee-discord: Fix build failure
Date: Wed, 14 Jul 2021 09:05:45 -0400 [thread overview]
Message-ID: <87h7gxoxjq.fsf_-_@gmail.com> (raw)
In-Reply-To: <875z5zk8vt.fsf@cbaines.net> (Christopher Baines's message of "Fri, 20 Nov 2020 21:37:10 +0000")
Hello,
Christopher Baines <mail@cbaines.net> writes:
> Leo Famulari <leo@famulari.name> writes:
>
>> On Sat, Mar 14, 2020 at 07:34:56PM +0000, Adrian Fullmer via Guix-patches via wrote:
>>> The latest stable version of bitlbee-discord is partially
>>> incompatible with discord as it exists now, so i upgraded to the
>>> latest git version which functions correctly.
>>
>> Is there a link to any upstream bug reports about this?
>
> Not sure you got this previous email Adrian, but is this Bitlbee fix
> something you're still interested in getting merged?
I've merged the fix to the build failure as
a6a4d4b843e8fcf35009ca556d9ed25a700b52d5, and updated the package to
0.4.3 in e69e0c43f867f23127029fd6959534f6a130bcfe. Let me know if
something still needs to be done!
Closing.
Maxim
prev parent reply other threads:[~2021-07-14 13:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1327954942.3272829.1584212270035.ref@mail.yahoo.com>
2020-03-14 18:57 ` [bug#40063] [PATCH 1/2] gnu: bitlbee-discord: Fix build failure Adrian Fullmer via Guix-patches via
2020-03-14 19:34 ` [bug#40063] [PATCH 2/2] gnu: bitlbee-discord: update to working version Adrian Fullmer via Guix-patches via
2020-03-15 17:32 ` Leo Famulari
2020-11-20 21:37 ` Christopher Baines
2021-07-14 13:05 ` Maxim Cournoyer [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h7gxoxjq.fsf_-_@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=40063-done@debbugs.gnu.org \
--cc=adrianfullmer@yahoo.com \
--cc=mail@cbaines.net \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.