Github messages for voidlinux
 help / color / mirror / Atom feed
From: raitonoberu <raitonoberu@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] spotify-player: update to 0.16.0
Date: Sun, 03 Dec 2023 10:30:46 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47545@inbox.vuxu.org> (raw)

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

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

https://github.com/raitonoberu/void-packages master
https://github.com/void-linux/void-packages/pull/47545

spotify-player: update to 0.16.0
#### Testing the changes
- I tested the changes in this PR: **YES**


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

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

From c00a9d0a34105da828a647ab66245e18ed8583cb Mon Sep 17 00:00:00 2001
From: Denis <raitonoberu@mail.ru>
Date: Sun, 3 Dec 2023 09:28:32 +0000
Subject: [PATCH] spotify-player: update to 0.16.0

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

diff --git a/srcpkgs/spotify-player/template b/srcpkgs/spotify-player/template
index ed944ede93abd..8cf345e1db264 100644
--- a/srcpkgs/spotify-player/template
+++ b/srcpkgs/spotify-player/template
@@ -1,17 +1,17 @@
 # Template file for 'spotify-player'
 pkgname=spotify-player
-version=0.14.0
-revision=2
+version=0.16.0
+revision=1
 build_style=cargo
 make_install_args="--path spotify_player"
 hostmakedepends="pkg-config"
-makedepends="openssl-devel alsa-lib-devel dbus-devel"
+makedepends="openssl-devel alsa-lib-devel dbus-devel libxcb-devel"
 short_desc="Command driven spotify player"
 maintainer="Thang Pham <phamducthang1234@gmail.com>"
 license="MIT"
 homepage="https://github.com/aome510/spotify-player"
 distfiles="https://github.com/aome510/spotify-player/archive/refs/tags/v${version}.tar.gz"
-checksum=3cb80919faacc0b50537b6161a464a27818b3fbf916f44e47290cf9bab7bf490
+checksum=2f70cd8fbea928022497fdd34140ce648ff695cdcc21d366228f41727c9e0d1f
 
 post_install() {
 	vlicense LICENSE

             reply	other threads:[~2023-12-03  9:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-03  9:30 raitonoberu [this message]
2023-12-03 19:58 ` [PR PATCH] [Merged]: " Duncaen

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