GNU bug report logs - #66695
(no subject)

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 66695 in the body.
You can then email your comments to 66695 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: jaeme <jaeme <at> runbox.com>
To: Christopher Baines <mail <at> cbaines.net>
Cc: 66548 <at> debbugs.gnu.org, guix-patches <at> gnu.org
Date: Mon, 23 Oct 2023 01:38:56 -0400

I redid my patches again, I split it up into 2 patches for rust-alsa and 
rust-alsa-sys since bitflags was updated on master.

On 10/18/23 04:44, Christopher Baines wrote:
> Jaeme Sifat via Guix-patches via <guix-patches <at> gnu.org> writes:
>
>> I revised my patch to not include older versions of rust-alsa as they
>> are not needed.
>>
>>
>>  From bb9a39beb92190d315284196ee63274e359fa657 Mon Sep 17 00:00:00 2001
>> From: jaeme <jaeme <at> runbox.com>
>> Date: Sat, 14 Oct 2023 22:54:54 -0400
>> Subject: [PATCH] gnu: Add rust-alsa
>>
>> * gnu/packages/crates-io.scm (rust-alsa-0.8): New variable.
>> * gnu/packages/crates-io.scm (rust-alsa-sys-0.3): New variable.
>> * gnu/packages/crates-io.scm (rust-bitflags-2): Update to 2.4.0.
>> * gnu/packages/crates-io.scm: Update copyright header.
> Hi Jaeme,
>
> Would you be able to split this up in to three commits/patches, with one
> package added/updated per commit?
>
> I did try to apply the patch, but wasn't able to. I think Git took issue
> with the format of the email (and it seemed to have lots of non breaking
> spaces in it as well). Could you use git send-email to send the patches,
> or maybe generate patch files and send them one by one as attachments if
> git send-email isn't possible for you?
>
> Thanks,
>
> Chris

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

From: jaeme <jaeme <at> runbox.com>
To: 66695 <at> debbugs.gnu.org
Subject: Mistaken Email
Date: Mon, 23 Oct 2023 10:10:48 -0400

This issue was open as a mistake and was related to 
https://issues.guix.gnu.org/66548

This can be removed.

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

From: jbranso <at> dismail.de
To: 66695 <at> debbugs.gnu.org
Date: Wed, 25 Oct 2023 00:47:58 +0000

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

close 66695

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

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

From: jbranso <at> dismail.de
To: 66695 <at> debbugs.gnu.org, jaeme <at> runbox.com
Date: Wed, 25 Oct 2023 01:03:11 +0000

So I apparently cannot close this bug, but you can jaeme:

https://debbugs.gnu.org/server-control.html

I personally use emacs-debbugs to close bug reports. It is fairly
easy wants you get it set up.

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

From: jaeme <jaeme <at> runbox.com>
To: 66695 <at> debbugs.gnu.org
Date: Tue, 24 Oct 2023 21:42:51 -0400

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

close 66695

[OpenPGP_0x2BBE3D4C390B79A3.asc (application/pgp-keys, attachment)]

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

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

From: jaeme <jaeme <at> runbox.com>
To: 66695 <at> debbugs.gnu.org
Subject: close 66695
Date: Tue, 24 Oct 2023 21:52:53 -0400

close 66695

Previous Next

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