unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: jgart <jgart@dismail.de>
Cc: Raghav Gururajan <rg@raghavgururajan.name>,
	packaging-guix@libremiami.org, 48006-done@debbugs.gnu.org
Subject: bug#48006: [PATCH] gnu: Add python-stripe.
Date: Thu, 23 Jun 2022 12:42:58 -0400	[thread overview]
Message-ID: <87pmiz2uwd.fsf@gmail.com> (raw)
In-Reply-To: <20220622194647.GD11143@gac> (jgart@dismail.de's message of "Wed,  22 Jun 2022 19:46:47 -0500")

OK,

jgart <jgart@dismail.de> writes:

> On Wed, 22 Jun 2022 15:41:03 -0400 Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:
>> Any update on this?  Adding a package without tests doesn't provide any
>> guarantee of about whether it is functional, so I'd rather we add
>> stripe-mock first.
>> 
>> Thanks,
>> 
>> Maxim
>
> Hi, this can be closed as someone had already merged python-stripe without stripe-mock in another ticket.
>
> We should probably add stripe-mock and enable tests for python-stripe in a new contribution.

OK, sounds good.  Thanks for the heads-up.

For the record, you can close a ticket yourself by adding '-done' at the
end of the bug number in Debbugs, like so:

48006-done@debbugs.gnu.org

C.f.: "Synopsis of bug submission and followup addresses" at
https://debbugs.gnu.org/server-refcard.html.

Thank you!

Maxim




      reply	other threads:[~2022-06-23 16:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-24 20:47 [bug#48006] [PATCH] gnu: Add python-stripe jgart via Guix-patches via
2021-06-30  1:39 ` [bug#48006] Raghav Gururajan via Guix-patches via
2022-06-22 19:41   ` [bug#48006] [PATCH] gnu: Add python-stripe Maxim Cournoyer
2022-06-23  0:46     ` jgart via Guix-patches via
2022-06-23 16:42       ` 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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pmiz2uwd.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=48006-done@debbugs.gnu.org \
    --cc=jgart@dismail.de \
    --cc=packaging-guix@libremiami.org \
    --cc=rg@raghavgururajan.name \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).