emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#40063: closed ([PATCH 1/2] gnu: bitlbee-discord: Fix build failure)


From: GNU bug Tracking System
Subject: bug#40063: closed ([PATCH 1/2] gnu: bitlbee-discord: Fix build failure)
Date: Wed, 14 Jul 2021 13:06:02 +0000

Your message dated Wed, 14 Jul 2021 09:05:45 -0400
with message-id <87h7gxoxjq.fsf_-_@gmail.com>
and subject line Re: bug#40063: [PATCH 1/2] gnu: bitlbee-discord: Fix build 
failure
has caused the debbugs.gnu.org bug report #40063,
regarding [PATCH 1/2] gnu: bitlbee-discord: Fix build failure
to be marked as done.

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


-- 
40063: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=40063
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: [PATCH 1/2] gnu: bitlbee-discord: Fix build failure Date: Sat, 14 Mar 2020 18:57:50 +0000 (UTC)
The old package definition fails to build due to attempting to create a help file in the bitlbee store location. This patch corrects the data directory in which the help file is placed to be in the bitlbee-discord output.


Attachment: 0001-gnu-bitlbee-discord-Fix-build-failure.patch
Description: Text Data


--- End Message ---
--- Begin Message --- Subject: Re: bug#40063: [PATCH 1/2] gnu: bitlbee-discord: Fix build failure Date: Wed, 14 Jul 2021 09:05:45 -0400 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
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


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]