From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: jgart <jgart@dismail.de>
Cc: 56115-done@debbugs.gnu.org
Subject: bug#56115: [PATCH] python-build-system: Fix typo in module-level comment paragraph.
Date: Wed, 22 Jun 2022 14:40:22 -0400 [thread overview]
Message-ID: <87y1xo4k4p.fsf@gmail.com> (raw)
In-Reply-To: <20220620211733.14137-1-jgart@dismail.de> (jgart@dismail.de's message of "Mon, 20 Jun 2022 16:17:33 -0500")
Hi,
jgart <jgart@dismail.de> writes:
> * guix/build/python-build-system.scm: Fix typo in comment paragraph.
> ---
> guix/build/python-build-system.scm | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/guix/build/python-build-system.scm b/guix/build/python-build-system.scm
> index 08871f60cd..28041e90a3 100644
> --- a/guix/build/python-build-system.scm
> +++ b/guix/build/python-build-system.scm
> @@ -68,7 +68,7 @@ (define-module (guix build python-build-system)
> ;; downloading the package source from PyPI (the Python Package Index). Both
> ;; of them import setuptools and execute the "setup.py" file under their
> ;; control. Thus the "setup.py" behaves as if the developer had imported
> -;; setuptools within setup.py - even is still using only distutils.
> +;; setuptools within setup.py - even if it is still using only distutils.
> ;;
> ;; Setuptools' "install" command (to be more precise: the "easy_install"
> ;; command which is called by "install") will put the path of the currently
Thanks. Unfortunately this simply typo fix causes a world rebuild. I'd
suggest flagging such patches with the 'core-updates PATCH' prefix, as
hinted in info '(guix) Submitting Patches' to avoid committers from
unintentionally pushing these to master.
Applied to core-updates.
Closing!
Maxim
next prev parent reply other threads:[~2022-06-22 19:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 21:17 [bug#56115] [PATCH] python-build-system: Fix typo in module-level comment paragraph jgart via Guix-patches via
2022-06-22 18:40 ` Maxim Cournoyer [this message]
2022-06-23 0:48 ` jgart via Guix-patches via
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y1xo4k4p.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=56115-done@debbugs.gnu.org \
--cc=jgart@dismail.de \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.