From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: mps-youtube: rename to yewtube, update to 2.10.4.
Date: Wed, 28 Jun 2023 10:12:56 +0200 [thread overview]
Message-ID: <20230628081256.LNMjP0TVqBDKOouy-Z7iOhGATGuYpU9DIKOZWPxJmCM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42662@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 822 bytes --]
There's a merged pull request on the void-packages repository
mps-youtube: rename to yewtube, update to 2.10.4.
https://github.com/void-linux/void-packages/pull/42662
Description:
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture: **x86_64**
Seems like mps-youtube has been rebranded in upstream a while ago. There is a couple of hiccups while trying to test it though. The first one is that it complained yt-dlp requires brotli which I fixed in https://github.com/void-linux/void-packages/pull/42661. Now it says httpx requires rfc3986[idna2008]<2,>=1.3 which is also [true](https://github.com/encode/httpx/blob/0.23.3/pyproject.toml#L33) but the version in our repo is already 2.0 so I don't know how to fix that.
prev parent reply other threads:[~2023-06-28 8:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 19:44 [PR PATCH] mps-youtube: rename to yewtube, update to 2.9.4 icp1994
2023-03-09 1:14 ` sgn
2023-03-09 1:14 ` sgn
2023-03-09 20:14 ` icp1994
2023-05-09 3:37 ` sgn
2023-05-09 7:53 ` [PR PATCH] [Updated] " icp1994
2023-06-27 22:38 ` mps-youtube: rename to yewtube, update to 2.10.2 classabbyamp
2023-06-28 6:41 ` [PR PATCH] [Updated] " icp1994
2023-06-28 6:41 ` icp1994
2023-06-28 8:12 ` classabbyamp [this message]
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=20230628081256.LNMjP0TVqBDKOouy-Z7iOhGATGuYpU9DIKOZWPxJmCM@z \
--to=classabbyamp@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).