From: jgart via Guix-patches via <guix-patches@gnu.org>
To: 70995@debbugs.gnu.org, "Nicolas Graves" <ngraves@ngraves.fr>
Subject: [bug#70995] [PATCH] gnu: python-debugpy: Update to 1.8.1.
Date: Wed, 18 Dec 2024 21:28:58 +0000 [thread overview]
Message-ID: <88d323741abdb406e4f10704a656a6f4f7f0da29@dismail.de> (raw)
In-Reply-To: <20240517054144.15296-1-ngraves@ngraves.fr>
Hi Nicolas,
Should this issue be closed?
It looks like python-debugpy is already updated atleast to 1.8.9 🦆
https://toys.whereis.social/?search=debugpy
all best,
jgart
prev parent reply other threads:[~2024-12-18 21:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 5:41 [bug#70995] [PATCH] gnu: python-debugpy: Update to 1.8.1 Nicolas Graves via Guix-patches via
2024-05-18 10:00 ` [bug#70995] [PATCH v2 1/2] gnu: python-debugpy: Move to pyproject-build-system Nicolas Graves via Guix-patches via
2024-05-18 10:00 ` [bug#70995] [PATCH v2 2/2] gnu: python-debugpy: Update to 1.8.1 Nicolas Graves via Guix-patches via
2024-05-28 8:46 ` [bug#70995] [PATCH v3 0/2] Update python-debugpy Nicolas Graves via Guix-patches via
2024-05-28 8:46 ` [bug#70995] [PATCH v3 1/2] gnu: python-debugpy: Move to pyproject-build-system Nicolas Graves via Guix-patches via
2024-05-28 8:46 ` [bug#70995] [PATCH v3 2/2] gnu: python-debugpy: Update to 1.8.0 Nicolas Graves via Guix-patches via
2024-06-11 10:42 ` [bug#70995] [PATCH v3 0/2] Update python-debugpy Christopher Baines
2024-06-15 14:41 ` Nicolas Graves via Guix-patches via
2024-06-15 15:26 ` Nicolas Graves via Guix-patches via
2024-06-16 10:05 ` Nicolas Graves via Guix-patches via
2024-06-15 15:28 ` [bug#70995] [PATCH v4 1/2] gnu: python-debugpy: Move to pyproject-build-system Nicolas Graves via Guix-patches via
2024-06-15 15:29 ` [bug#70995] [PATCH v4 2/2] gnu: python-debugpy: Update to 1.8.0 Nicolas Graves via Guix-patches via
2024-12-18 21:28 ` jgart via Guix-patches via [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=88d323741abdb406e4f10704a656a6f4f7f0da29@dismail.de \
--to=guix-patches@gnu.org \
--cc=70995@debbugs.gnu.org \
--cc=jgart@dismail.de \
--cc=ngraves@ngraves.fr \
/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).