Github messages for voidlinux
 help / color / mirror / Atom feed
From: bougyman <bougyman@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] spotify-player: update to 0.20.0.
Date: Tue, 05 Nov 2024 16:24:33 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-52922@inbox.vuxu.org> (raw)

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

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

https://github.com/bougyman/void-packages update-spotify-player
https://github.com/void-linux/void-packages/pull/52922

spotify-player: update to 0.20.0.
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**

<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-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, x86_64-LIBC


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

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-update-spotify-player-52922.patch --]
[-- Type: text/x-diff, Size: 1125 bytes --]

From b558458b1a5590b44ede30ecb4e3c94ca95bfd96 Mon Sep 17 00:00:00 2001
From: "Tj (bougyman) Vanderpoel" <bougyman@users.noreply.github.com>
Date: Tue, 5 Nov 2024 09:19:56 -0600
Subject: [PATCH] spotify-player: update to 0.20.0.

---
 srcpkgs/spotify-player/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/spotify-player/template b/srcpkgs/spotify-player/template
index 17d9f99553ce60..7cf006c31dda72 100644
--- a/srcpkgs/spotify-player/template
+++ b/srcpkgs/spotify-player/template
@@ -1,6 +1,6 @@
 # Template file for 'spotify-player'
 pkgname=spotify-player
-version=0.19.1
+version=0.20.0
 revision=1
 build_style=cargo
 make_install_args="--path spotify_player"
@@ -11,7 +11,7 @@ maintainer="Rodrigo Oliveira <mdkcore@qtrnn.io>"
 license="MIT"
 homepage="https://github.com/aome510/spotify-player"
 distfiles="https://github.com/aome510/spotify-player/archive/refs/tags/v${version}.tar.gz"
-checksum=bd516ed91cee0a96444797c2b99f3775efea84c252f79f7bc7de4cdb33dbd52c
+checksum=a0708da71e30c0d213bb9f840fad4e3667ce4348d4a9dcdd6370d00b9ac2bda3
 
 post_install() {
 	vlicense LICENSE

             reply	other threads:[~2024-11-05 15:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-05 15:24 bougyman [this message]
2024-11-05 15:53 ` [PR PATCH] [Updated] " bougyman
2025-02-04  1:58 ` github-actions
2025-02-18  1:59 ` [PR PATCH] [Closed]: " github-actions
  -- strict thread matches above, loose matches on Subject: below --
2024-11-01 14:32 [PR PATCH] " mdkcore0

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-52922@inbox.vuxu.org \
    --to=bougyman@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).