From: dmarto <dmarto@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] spotify: update to 1.1.80.
Date: Thu, 10 Mar 2022 01:04:38 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36073@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 481 bytes --]
There is a new pull request by dmarto against master on the void-packages repository
https://github.com/dmarto/void-packages spotify
https://github.com/void-linux/void-packages/pull/36073
spotify: update to 1.1.80.
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### Local build testing
- I built this PR locally for my native architecture, x86_64-glibc
A patch file from https://github.com/void-linux/void-packages/pull/36073.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-spotify-36073.patch --]
[-- Type: text/x-diff, Size: 1310 bytes --]
From a818065b4ae3a320a5e7f15f2d56f278822e2929 Mon Sep 17 00:00:00 2001
From: Martin Dimov <martin@dmarto.com>
Date: Thu, 10 Mar 2022 02:02:43 +0200
Subject: [PATCH] spotify: update to 1.1.80.
---
srcpkgs/spotify/template | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/spotify/template b/srcpkgs/spotify/template
index 185d59ecdb5c..6e1a70f3697f 100644
--- a/srcpkgs/spotify/template
+++ b/srcpkgs/spotify/template
@@ -1,8 +1,8 @@
# Template file for 'spotify'
pkgname=spotify
-version=1.1.72
+version=1.1.80
revision=1
-_ver="${version}.439.gc253025e_amd64"
+_ver="${version}.699.gc3dac750_amd64"
_filename="spotify-client_${_ver}.deb"
archs="x86_64"
create_wrksrc=yes
@@ -14,8 +14,8 @@ maintainer="Stefan Mühlinghaus <jazzman@alphabreed.com>"
license="custom:Proprietary"
homepage="https://www.spotify.com"
distfiles="http://repository.spotify.com/pool/non-free/s/spotify-client/${_filename}"
-checksum=c211a16b6ed6627c4b7d8ca6997376f8345dca638938696933c5495405ce9e16
-_license_checksum=4465d0bba5deb87866184b04ba76604cd93561c0dc9cd21cacdf5b0295bdae3a
+checksum=19f80255b89d768969ff9d6a05d90091a30c05f65eabdd968592d47a7754b80e
+_license_checksum=e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
repository=nonfree
restricted=yes
nostrip=yes
next reply other threads:[~2022-03-10 0:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 0:04 dmarto [this message]
2022-03-10 0:15 ` [PR PATCH] [Updated] " dmarto
2022-03-10 0:15 ` dmarto
2022-03-10 0:16 ` dmarto
2022-03-10 0:17 ` dmarto
2022-03-10 22:24 ` [PR PATCH] [Closed]: " abenson
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-36073@inbox.vuxu.org \
--to=dmarto@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).