From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] New package: mitmproxy-8.1.1
Date: Mon, 04 Jul 2022 00:07:23 +0200 [thread overview]
Message-ID: <20220703220723.7ckdWlOJKa8x-iYgkuzbN2O4RhqIvxFEa-qCOoR_8Nk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34776@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 557 bytes --]
New review comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/pull/34776#discussion_r912542213
Comment:
```
Command '['/usr/bin/python3', '-m', 'pip', '--disable-pip-version-check', 'wheel', '--no-deps', '-w', '/tmp/tmp3mvkx0wo', '--quiet', 'requests>=2.7.0']' returned non-zero exit status 1.
```
That only means you are missing requests from dependencies. Adding pip to hostmakedepends will just hide this issue and download requests in their preferred version, but we want to run the tests on Void packages.
next prev parent reply other threads:[~2022-07-03 22:07 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-31 0:10 [PR PATCH] Pkg/mitmproxy unspecd
2021-12-31 0:23 ` [PR PATCH] [Updated] New package: mitmproxy-7.0.4 unspecd
2021-12-31 18:03 ` unspecd
2021-12-31 18:26 ` paper42
2021-12-31 19:03 ` [PR PATCH] [Updated] " unspecd
2021-12-31 19:06 ` unspecd
2021-12-31 19:07 ` unspecd
2021-12-31 21:17 ` unspecd
2021-12-31 21:31 ` unspecd
2021-12-31 21:35 ` unspecd
2021-12-31 21:38 ` [PR PATCH] [Updated] " unspecd
2022-01-01 17:18 ` paper42
2022-01-04 3:14 ` [PR PATCH] [Updated] " unspecd
2022-01-04 3:28 ` unspecd
2022-01-14 22:06 ` [PR PATCH] [Updated] " unspecd
2022-01-15 20:23 ` [PR REVIEW] " unspecd
2022-03-22 7:35 ` [PR PATCH] [Updated] " unspecd
2022-03-22 7:42 ` unspecd
2022-03-22 7:59 ` New package: mitmproxy-8.0.0 unspecd
2022-05-23 23:56 ` [PR PATCH] [Updated] " unspecd
2022-05-23 23:57 ` New package: mitmproxy-8.1.0 unspecd
2022-07-03 13:51 ` [PR PATCH] [Updated] " unspecd
2022-07-03 14:05 ` New package: mitmproxy-8.1.1 unspecd
2022-07-03 18:42 ` [PR REVIEW] " classabbyamp
2022-07-03 18:42 ` classabbyamp
2022-07-03 18:42 ` classabbyamp
2022-07-03 18:42 ` classabbyamp
2022-07-03 18:42 ` classabbyamp
2022-07-03 18:42 ` classabbyamp
2022-07-03 18:42 ` classabbyamp
2022-07-03 18:42 ` classabbyamp
2022-07-03 18:42 ` classabbyamp
2022-07-03 18:42 ` classabbyamp
2022-07-03 18:42 ` classabbyamp
2022-07-03 18:42 ` classabbyamp
2022-07-03 18:42 ` classabbyamp
2022-07-03 20:21 ` paper42
2022-07-03 20:21 ` paper42
2022-07-03 22:04 ` unspecd
2022-07-03 22:07 ` paper42 [this message]
2022-07-03 22:08 ` unspecd
2022-07-03 22:09 ` paper42
2022-07-03 22:11 ` unspecd
2022-07-03 22:13 ` unspecd
2022-07-03 22:27 ` unspecd
2022-07-03 22:27 ` unspecd
2022-07-03 22:31 ` [PR REVIEW] " unspecd
2022-07-03 22:32 ` [PR PATCH] [Updated] " unspecd
2022-07-03 22:48 ` [PR PATCH] [Merged]: " classabbyamp
2022-07-11 17:40 ` Duncaen
2022-07-22 3:48 ` unspecd
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=20220703220723.7ckdWlOJKa8x-iYgkuzbN2O4RhqIvxFEa-qCOoR_8Nk@z \
--to=paper42@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).