Github messages for voidlinux
 help / color / mirror / Atom feed
From: 1is7ac3 <1is7ac3@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-chromecast: update to 10.3.0.
Date: Mon, 28 Mar 2022 00:47:23 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36389@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1255 bytes --]

There is a new pull request by 1is7ac3 against master on the void-packages repository

https://github.com/1is7ac3/void-packages python3-chromecast
https://github.com/void-linux/void-packages/pull/36389

python3-chromecast: update to 10.3.0.
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: briefly

<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->

<!-- 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, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl
  - armv7l
  - armv6l-musl
-->


A patch file from https://github.com/void-linux/void-packages/pull/36389.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python3-chromecast-36389.patch --]
[-- Type: text/x-diff, Size: 1239 bytes --]

From 9ce83807f0205ab3e61e72b52f11ecec4a268478 Mon Sep 17 00:00:00 2001
From: *1is7ac3* Isaac Quiroz <isaac.qa13@gmail.com>
Date: Sun, 27 Mar 2022 19:33:22 -0300
Subject: [PATCH] python3-chromecast: update to 10.3.0.

---
 srcpkgs/python3-chromecast/template | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/python3-chromecast/template b/srcpkgs/python3-chromecast/template
index cd54fcaf8977..72f891be6a1f 100644
--- a/srcpkgs/python3-chromecast/template
+++ b/srcpkgs/python3-chromecast/template
@@ -1,7 +1,7 @@
 # Template file for 'python3-chromecast'
 pkgname=python3-chromecast
-version=8.1.0
-revision=2
+version=10.3.0
+revision=1
 wrksrc="pychromecast-${version}"
 build_style=python3-module
 hostmakedepends="python3-setuptools python3-protobuf python3-zeroconf python3-casttube"
@@ -12,7 +12,7 @@ maintainer="Ulf <void@uw.anonaddy.com>"
 license="MIT"
 homepage="https://github.com/home-assistant-libs/pychromecast"
 distfiles="https://github.com/home-assistant-libs/pychromecast/archive/${version}.tar.gz"
-checksum=f11d73cffa84b25417192c30e6ea46df470b65055e229c568f677372c4ded1de
+checksum=325d8cfa686b7127de1783221f7ef3e81988c0631619bbacf3679ce647b1db1f
 
 post_install() {
 	vlicense LICENSE

             reply	other threads:[~2022-03-27 22:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-27 22:47 1is7ac3 [this message]
2022-04-07 14:03 ` [PR PATCH] [Merged]: " ahesford

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-36389@inbox.vuxu.org \
    --to=1is7ac3@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).