From: unspecd <unspecd@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] mitmproxy: remove unused python3-pyzstd dependency
Date: Fri, 22 Jul 2022 05:38:46 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38181@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 927 bytes --]
There is a new pull request by unspecd against master on the void-packages repository
https://github.com/unspecd/void-packages pkg/mitmproxy
https://github.com/void-linux/void-packages/pull/38181
mitmproxy: remove unused python3-pyzstd dependency
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-musl)
A patch file from https://github.com/void-linux/void-packages/pull/38181.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-pkg/mitmproxy-38181.patch --]
[-- Type: text/x-diff, Size: 1354 bytes --]
From b53b0c4b3c3102d863fb717b126d60bb568cde17 Mon Sep 17 00:00:00 2001
From: Evgeny Ermakov <evgeny.v.ermakov@gmail.com>
Date: Fri, 22 Jul 2022 14:26:17 +1100
Subject: [PATCH] mitmproxy: remove unused python3-pyzstd dependency
---
srcpkgs/mitmproxy/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/mitmproxy/template b/srcpkgs/mitmproxy/template
index b662359d5c7c..9ddf143084a0 100644
--- a/srcpkgs/mitmproxy/template
+++ b/srcpkgs/mitmproxy/template
@@ -1,13 +1,13 @@
# Template file for 'mitmproxy'
pkgname=mitmproxy
version=8.1.1
-revision=1
+revision=2
build_style=python3-module
hostmakedepends="python3-setuptools"
depends="python3-Brotli python3-Flask python3-asgiref python3-blinker python3-certifi
python3-click python3-cryptography python3-h11 python3-h2 python3-hyperframe python3-kaitaistruct
python3-ldap3 python3-msgpack python3-openssl python3-parsing python3-passlib python3-protobuf
- python3-publicsuffix2 python3-pyperclip python3-pyzstd python3-ruamel.yaml python3-sortedcontainers
+ python3-publicsuffix2 python3-pyperclip python3-ruamel.yaml python3-sortedcontainers
python3-tornado python3-urwid python3-wsproto python3-zstandard"
checkdepends="${depends} python3-hypothesis python3-parver
python3-pytest-asyncio python3-pytest-cov python3-pytest-timeout python3-requests"
next reply other threads:[~2022-07-22 3:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 3:38 unspecd [this message]
2022-07-22 4:06 ` unspecd
2022-07-22 5:00 ` [PR PATCH] [Merged]: " classabbyamp
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38181@inbox.vuxu.org \
--to=unspecd@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).