From: tibequadorian <tibequadorian@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] pianobar: update to 2022.04.01.
Date: Thu, 14 Apr 2022 16:35:45 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36691@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1255 bytes --]
There is a new pull request by tibequadorian against master on the void-packages repository
https://github.com/tibequadorian/void-packages pianobar
https://github.com/void-linux/void-packages/pull/36691
pianobar: update to 2022.04.01.
<!-- 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/36691.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-pianobar-36691.patch --]
[-- Type: text/x-diff, Size: 1233 bytes --]
From 263d55a8121a5bb4a43f4d6f1214899021885902 Mon Sep 17 00:00:00 2001
From: tibequadorian <tibequadorian@posteo.de>
Date: Thu, 14 Apr 2022 16:34:08 +0200
Subject: [PATCH] pianobar: update to 2022.04.01.
---
srcpkgs/pianobar/template | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/pianobar/template b/srcpkgs/pianobar/template
index b7d991fef5a4..a9b29e91993f 100644
--- a/srcpkgs/pianobar/template
+++ b/srcpkgs/pianobar/template
@@ -1,6 +1,6 @@
# Template file for 'pianobar'
pkgname=pianobar
-version=2020.11.28
+version=2022.04.01
revision=1
build_style=gnu-makefile
make_build_args="V=1"
@@ -11,8 +11,9 @@ short_desc="Free/open-source, console-based client for Pandora radio"
maintainer="Ulf <void@uw.anonaddy.com>"
license="MIT"
homepage="https://6xq.net/pianobar/"
-distfiles="https://github.com/PromyLOPh/pianobar/archive/${version}.tar.gz"
-checksum=f8cdd564e2a12ee0740c54e8bc4028b328e9afb041d9ea40bcb762e08034b9e9
+changelog="https://raw.githubusercontent.com/PromyLOPh/pianobar/master/ChangeLog"
+distfiles="https://6xq.net/pianobar/pianobar-${version}.tar.bz2"
+checksum=1670b28865a8b82a57bb6dfea7f16e2fa4145d2f354910bb17380b32c9b94763
post_install() {
vlicense COPYING
next reply other threads:[~2022-04-14 14:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 14:35 tibequadorian [this message]
2022-04-14 20:46 ` [PR PATCH] [Merged]: " paper42
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-36691@inbox.vuxu.org \
--to=tibequadorian@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).