From: dotnetfox <dotnetfox@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] python3-bibtexparser: update to 1.2.0.
Date: Mon, 29 Nov 2021 18:08:27 +0100 [thread overview]
Message-ID: <20211129170827.SbFNIideCbSwX0Y9zB0Pb2PTl_-WnejfElbB81q3Gqg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34299@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1221 bytes --]
New review comment by dotnetfox on void-packages repository
https://github.com/void-linux/void-packages/pull/34299#discussion_r758567275
Comment:
@paper42, according to what you just wrote, I suppose you meant the following:
```
hostmakedepends="python3-setuptools python3-wheel"
depends="python3-parsing"
checkdepends="python3-future"
```
However, it still does not seem to be enough:
```
=> python3-bibtexparser-1.2.0_1: running do_check ...
/usr/lib/python3.10/distutils/dist.py:274: UserWarning: Unknown distribution option: 'extra_requires'
warnings.warn(msg)
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/bin/python3: No module named pip
error: Command '['/usr/bin/python3', '-m', 'pip', '--disable-pip-version-check', 'wheel', '--no-deps', '-w', '/tmp/tmpfxlnb_mp', '--quiet', 'pyparsing>=2.0.3']' returned non-zero exit status 1.
=> ERROR: python3-bibtexparser-1.2.0_1: do_check: 'python3 setup.py ${make_check_target} ${make_check_args}' exited with 1
=> ERROR: in do_check() at common/build-style/python3-module.sh:40
```
next prev parent reply other threads:[~2021-11-29 17:08 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-29 6:03 [PR PATCH] " jgarte
2021-11-29 6:48 ` [PR PATCH] [Updated] " jgarte
2021-11-29 7:58 ` jgarte
2021-11-29 16:11 ` [PR REVIEW] " dotnetfox
2021-11-29 16:29 ` dotnetfox
2021-11-29 16:41 ` paper42
2021-11-29 17:08 ` dotnetfox [this message]
2021-11-29 17:13 ` dotnetfox
2021-11-29 17:31 ` paper42
2021-11-29 18:49 ` [PR PATCH] [Updated] " jgarte
2021-11-29 19:26 ` [PR REVIEW] " jgarte
2021-11-29 19:33 ` paper42
2021-11-29 22:11 ` [PR PATCH] [Updated] " jgarte
2021-11-29 22:11 ` jgarte
2021-11-29 22:12 ` [PR PATCH] [Updated] " jgarte
2021-11-30 18:41 ` [PR REVIEW] " paper42
2021-11-30 18:43 ` paper42
2021-11-30 20:37 ` [PR PATCH] [Updated] " jgarte
2021-11-30 20:39 ` [PR REVIEW] " jgarte
2021-11-30 20:39 ` jgarte
2021-11-30 20:40 ` [PR PATCH] [Updated] " jgarte
2021-11-30 20:42 ` jgarte
2021-11-30 20:44 ` jgarte
2021-11-30 21:00 ` [PR PATCH] [Updated] " jgarte
2021-11-30 21:01 ` jgarte
2021-11-30 21:06 ` [PR PATCH] [Updated] " jgarte
2021-11-30 21:17 ` jgarte
2021-11-30 21:31 ` jgarte
2021-11-30 22:43 ` paper42
2021-11-30 23:40 ` jgarte
2021-11-30 23:45 ` jgarte
2021-12-11 3:24 ` [PR REVIEW] " ericonr
2021-12-15 22:38 ` paper42
2022-01-12 0:20 ` jgarte
2022-06-16 2:14 ` github-actions
2022-07-01 2:14 ` [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=20211129170827.SbFNIideCbSwX0Y9zB0Pb2PTl_-WnejfElbB81q3Gqg@z \
--to=dotnetfox@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).