GNU bug report logs - #40063
[PATCH 1/2] gnu: bitlbee-discord: Fix build failure

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 40063 in the body.
You can then email your comments to 40063 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Adrian Fullmer <adrianfullmer <at> yahoo.com>
To: "guix-patches <at> gnu.org" <guix-patches <at> gnu.org>
Subject: [PATCH 1/2] gnu: bitlbee-discord: Fix build failure
Date: Sat, 14 Mar 2020 18:57:50 +0000 (UTC)

[Message part 1 (text/plain, inline)]

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.

[Message part 2 (text/html, inline)]

[0001-gnu-bitlbee-discord-Fix-build-failure.patch (text/x-patch, attachment)]

Message #8 received at 40063 <at> debbugs.gnu.org (full text, mbox):

From: Adrian Fullmer <adrianfullmer <at> yahoo.com>
To: "40063 <at> debbugs.gnu.org" <40063 <at> debbugs.gnu.org>
Subject: [PATCH 2/2] gnu: bitlbee-discord: update to working version
Date: Sat, 14 Mar 2020 19:34:56 +0000 (UTC)

[Message part 1 (text/plain, inline)]

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.

[Message part 2 (text/html, inline)]

[0002-gnu-bitlbee-discord-update-to-working-version.patch (text/x-patch, attachment)]

Message #11 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Leo Famulari <leo <at> famulari.name>
To: Adrian Fullmer via Guix-patches via <guix-patches <at> gnu.org>
Cc: "40063 <at> debbugs.gnu.org" <40063 <at> debbugs.gnu.org>
Subject: Re: [bug#40063] [PATCH 2/2] gnu: bitlbee-discord: update to working
 version
Date: Sun, 15 Mar 2020 13:32:26 -0400

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?

Message #17 received at 40063 <at> debbugs.gnu.org (full text, mbox):

From: Christopher Baines <mail <at> cbaines.net>
To: Adrian Fullmer <adrianfullmer <at> yahoo.com>
Cc: 40063 <at> debbugs.gnu.org
Subject: Re: [bug#40063] [PATCH 2/2] gnu: bitlbee-discord: update to working
 version
Date: Fri, 20 Nov 2020 21:37:10 +0000

[Message part 1 (text/plain, inline)]

Leo Famulari <leo <at> 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?

Thanks,

Chris

[signature.asc (application/pgp-signature, inline)]

Message #22 received at 40063-done <at> debbugs.gnu.org (full text, mbox):

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Christopher Baines <mail <at> cbaines.net>
Cc: 40063-done <at> debbugs.gnu.org, Adrian Fullmer <adrianfullmer <at> yahoo.com>
Subject: Re: bug#40063: [PATCH 1/2] gnu: bitlbee-discord: Fix build failure
Date: Wed, 14 Jul 2021 09:05:45 -0400

Hello,

Christopher Baines <mail <at> cbaines.net> writes:

> Leo Famulari <leo <at> 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

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.