From: jcgruenhage <jcgruenhage@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] New package: giara-1.0.1
Date: Mon, 12 Dec 2022 00:30:09 +0100 [thread overview]
Message-ID: <20221211233009.-h_caRiGBdk4y4aElP9olglC1CpjMeC-iNpUMrBLSl4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37132@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1215 bytes --]
New review comment by jcgruenhage on void-packages repository
https://github.com/void-linux/void-packages/pull/37132#discussion_r1045316420
Comment:
It does try though, and then fails:
```
=> python3-betamax-serializers-0.2.1_1: running do_check ...
running test
WARNING: Testing via this command is deprecated and will be removed in a future version. Users looking for a generic test entry point independent of test runner are encouraged to use tox.
/usr/lib/python3.11/site-packages/setuptools/installer.py:27: SetuptoolsDeprecationWarning: setuptools.installer is deprecated. Requirements should be satisfied by a PEP 517 installer.
warnings.warn(
WARNING: The wheel package is not available.
/usr/bin/python3: No module named pip
error: Command '['/usr/bin/python3', '-m', 'pip', '--disable-pip-version-check', 'wheel', '--no-deps', '-w', '/tmp/tmpxidysgrh', '--quiet', 'betamax>=0.3.2']' returned non-zero exit status 1.
=> ERROR: python3-betamax-serializers-0.2.1_1: do_check: '${make_check_pre} python3 setup.py ${make_check_target} ${make_check_args}' exited with 1
=> ERROR: in do_check() at common/build-style/python3-module.sh:28
```
Do you have a suggestion for a better comment?
next prev parent reply other threads:[~2022-12-11 23:30 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-14 17:44 [PR PATCH] " jcgruenhage
2022-09-02 2:16 ` github-actions
2022-09-02 13:05 ` [PR PATCH] [Updated] " jcgruenhage
2022-09-02 13:05 ` jcgruenhage
2022-09-02 19:05 ` paper42
2022-09-03 8:25 ` [PR PATCH] [Updated] " jcgruenhage
2022-09-03 8:25 ` jcgruenhage
2022-11-27 10:58 ` [PR PATCH] [Updated] " jcgruenhage
2022-11-27 11:02 ` jcgruenhage
2022-12-11 20:44 ` [PR REVIEW] " paper42
2022-12-11 21:11 ` jcgruenhage
2022-12-11 21:41 ` jcgruenhage
2022-12-11 21:43 ` [PR PATCH] [Updated] " jcgruenhage
2022-12-11 21:57 ` [PR REVIEW] " paper42
2022-12-11 21:57 ` paper42
2022-12-11 21:57 ` paper42
2022-12-11 21:57 ` paper42
2022-12-11 21:57 ` paper42
2022-12-11 21:57 ` paper42
2022-12-11 21:57 ` paper42
2022-12-11 21:57 ` paper42
2022-12-11 23:30 ` jcgruenhage [this message]
2022-12-11 23:35 ` [PR PATCH] [Updated] " jcgruenhage
2022-12-16 18:58 ` [PR REVIEW] " paper42
2022-12-16 18:58 ` paper42
2022-12-16 23:01 ` [PR PATCH] [Updated] " jcgruenhage
2023-03-17 1:56 ` github-actions
2023-03-19 14:26 ` jcgruenhage
2023-04-10 16:27 ` [PR REVIEW] " eli-schwartz
2023-07-10 2:08 ` github-actions
2023-07-25 2:01 ` [PR PATCH] [Closed]: " github-actions
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=20221211233009.-h_caRiGBdk4y4aElP9olglC1CpjMeC-iNpUMrBLSl4@z \
--to=jcgruenhage@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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.
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 NNTP newsgroup(s).