From: Marius Bakke <marius@gnu.org>
To: Ryan Prior <rprior@protonmail.com>, 41580-done@debbugs.gnu.org
Subject: bug#41580: [PATCH] gnu: Update python-pylint to 2.5.2
Date: Sat, 30 May 2020 14:31:09 +0200 [thread overview]
Message-ID: <871rn138qa.fsf@gnu.org> (raw)
In-Reply-To: <20200528180122.21280-1-rprior@protonmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 211 bytes --]
Ryan Prior via Guix-patches via <guix-patches@gnu.org> writes:
> * gnu/packages/check.scm (python-pylint): Updated version to 2.5.2
Thanks! I fixed the commit message and applied with the following
changes:
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: diff --]
[-- Type: text/x-patch, Size: 1016 bytes --]
diff --git a/gnu/packages/check.scm b/gnu/packages/check.scm
index de4a978d97..8d99e67514 100644
--- a/gnu/packages/check.scm
+++ b/gnu/packages/check.scm
@@ -1902,7 +1902,7 @@ statements in the module it tests.")
(base32
"150x679mrlgm1s4ym7irf9mnsjilqyaakss4spc4pbrzkl11agnh"))))
(build-system python-build-system)
- ;; Further releases, up to 2.4.3, have failing unit tests. See:
+ ;; FIXME: Tests are failing since version 2.4.3, see:
;; https://github.com/PyCQA/pylint/issues/3198.
(arguments '(#:tests? #f))
(native-inputs
@@ -1946,7 +1946,7 @@ possible to write plugins to add your own checks.")
(base32
"02a89d8a47s7nfiv1ady3j0sg2sbyja3np145brarfp5x9qxz9x2"))))
(arguments
- `(,@(package-arguments pylint)
+ `(,@(strip-keyword-arguments '(#:tests?) (package-arguments pylint))
#:phases
(modify-phases %standard-phases
(replace 'check
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-05-30 12:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 18:01 [bug#41580] [PATCH] gnu: Update python-pylint to 2.5.2 Ryan Prior via Guix-patches via
2020-05-30 12:31 ` Marius Bakke [this message]
2020-05-30 21:34 ` Marius Bakke
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=871rn138qa.fsf@gnu.org \
--to=marius@gnu.org \
--cc=41580-done@debbugs.gnu.org \
--cc=rprior@protonmail.com \
/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).