GNU bug report logs - #40064
Resubmission of patch for Package Description for CRAN Package r-crochet

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 40064 in the body.
You can then email your comments to 40064 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: Naga Malleswari <nagamalli <at> riseup.net>
To: guix-patches <at> gnu.org
Cc: dannym <at> scratchpost.org
Subject: Resubmission of patch for Package Description for CRAN Package
 r-crochet
Date: Sat, 14 Mar 2020 23:46:58 +0530

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

Hi

I am resubmitting with the new patch file for CRAN Package Description 
r-crochet.

Hope it's the correct way which i was following.


Through put the process,I have doubt in lint.

when i run it , it's showing the error continuously like this with 
different codes.

guix/build/download.scm:313:6: In procedure tls-wrap:
X.509 certificate of 'www.x.org' could not be verified:
  signer-not-found
  invalid

-- 
Regards
NagaMalli

[0001-gnu-r-crochet-New-variable.patch (text/x-patch, attachment)]

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

From: Tobias Geerinckx-Rice <me <at> tobias.gr>
To: 40064 <at> debbugs.gnu.org
Subject: Re: [bug#40064] Resubmission of patch for Package Description for
 CRAN Package r-crochet
Date: Sat, 14 Mar 2020 23:41:20 +0100

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

Hullo Naga,

Naga Malleswari 写道：
> I am resubmitting with the new patch file for CRAN Package 
> Description 
> r-crochet.

Thank you!

> Hope it's the correct way which i was following.

Sending a patch to guix-patches <at> gnu.org will always create a new 
bug number[0].  In this case, you don't want that to happen.

The way to submit a revised patch is to send it to the previous 
bug number (nnnnn <at> debbugs.gnu.org, in this case 
40040 <at> debbugs.gnu.org) and clearly mark it as a new revision (V2, 
V3, &c.).

If, like me, you use git send-email, this is easy:

 ~/guix $ git send-email --to=40040 <at> debbugs.gnu.org -v2 -1

I've merged the two duplicate bug numbers for this package.

Kind regards,

T G-R

[0]: 
https://debbugs.gnu.org/cgi/pkgreport.cgi?package=guix-patches;include=subject%3Ar-crochet

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

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

From: Naga Malli CH <ch.nagamalli148 <at> gmail.com>
To: Tobias Geerinckx-Rice <me <at> tobias.gr>, 
 Tobias Geerinckx-Rice via Guix-patches <guix-patches <at> gnu.org>
Cc: Danny Milosavljevic <dannym <at> scratchpost.org>, 40064 <at> debbugs.gnu.org
Subject: Re: [bug#40064] Resubmission of patch for Package Description for
 CRAN Package r-crochet
Date: Sun, 15 Mar 2020 18:03:01 +0530

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

On Sun, 15 Mar 2020 at 04:11, Tobias Geerinckx-Rice via Guix-patches via <
guix-patches <at> gnu.org> wrote:

> Hullo Naga,
>
> Naga Malleswari 写道：
> > I am resubmitting with the new patch file for CRAN Package
> > Description
> > r-crochet.
>
> Thank you!



You are Welcome

>
> > Hope it's the correct way which i was following.
>
> Sending a patch to guix-patches <at> gnu.org will always create a new
> bug number[0].  In this case, you don't want that to happen.
>
> The way to submit a revised patch is to send it to the previous
> bug number (nnnnn <at> debbugs.gnu.org, in this case
> 40040 <at> debbugs.gnu.org) and clearly mark it as a new revision (V2,
> V3, &c.).
>
> If, like me, you use git send-email, this is easy:
>
>   ~/guix $ git send-email --to=40040 <at> debbugs.gnu.org -v2 -1
>
> I've merged the two duplicate bug numbers for this package.
>
> Sure,I will do that from next time Onwards.


> Kind regards,
>
> T G-R
>
> [0]:
>
> https://debbugs.gnu.org/cgi/pkgreport.cgi?package=guix-patches;include=subject%3Ar-crochet




Can I Now the status of my patch ? Can you please advice me here about the
further process i have to do to reach the contribution?

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

Previous Next

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