Github messages for voidlinux
 help / color / mirror / Atom feed
From: garylaski <garylaski@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] picard: update to 2.7.2
Date: Tue, 18 Jan 2022 23:52:48 +0100	[thread overview]
Message-ID: <20220118225248.J10q8D8ozjNR-NUdgxOSOWgBQYJrMM-vNLOdO8tFIL0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35019@inbox.vuxu.org>

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

There is an updated pull request by garylaski against master on the void-packages repository

https://github.com/garylaski/void-packages master
https://github.com/void-linux/void-packages/pull/35019

picard: update to 2.7.2
#### 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**



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

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

From 4f66c91aa5dcbd50a1dadad606efa39666afea67 Mon Sep 17 00:00:00 2001
From: gary <28818063+garylaski@users.noreply.github.com>
Date: Wed, 12 Jan 2022 17:06:03 -0500
Subject: [PATCH] picard: update to 2.7.2

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

diff --git a/srcpkgs/picard/template b/srcpkgs/picard/template
index b5ea59ed5e07..03895b679281 100644
--- a/srcpkgs/picard/template
+++ b/srcpkgs/picard/template
@@ -1,6 +1,6 @@
 # Template file for 'picard'
 pkgname=picard
-version=2.6.4
+version=2.7.2
 revision=1
 wrksrc="${pkgname}-release-${version}"
 build_style=python3-module
@@ -9,7 +9,7 @@ hostmakedepends="gettext python3-setuptools"
 makedepends="python3-devel"
 depends="python3-PyQt5-multimedia chromaprint python3-mutagen
  python3-dateutil python3-discid python3-fasteners desktop-file-utils
- hicolor-icon-theme"
+ hicolor-icon-theme python3-yaml"
 checkdepends="python3-pytest $depends"
 short_desc="MusicBrainz's audio tagger"
 maintainer="Michael Aldridge <maldridge@voidlinux.org>"
@@ -17,4 +17,4 @@ license="GPL-2.0-or-later"
 homepage="https://picard.musicbrainz.org/"
 changelog="https://picard.musicbrainz.org/changelog/"
 distfiles="http://ftp.musicbrainz.org/pub/musicbrainz/${pkgname}/${pkgname}-${version}.tar.gz"
-checksum=c71ec4605842e24bbe6d92639e1cafac943548afed3a05193488d4bcc3d95370
+checksum=73c70933f78de9a92ad8943d2e237d5f580d4f695c950d2070385f1067315e76

  parent reply	other threads:[~2022-01-18 22:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-12 22:11 [PR PATCH] " garylaski
2022-01-16 18:58 ` ericonr
2022-01-16 18:58 ` ericonr
2022-01-18 22:52 ` garylaski [this message]
2022-01-18 22:57 ` [PR PATCH] [Updated] " garylaski
2022-01-18 22:58 ` picard: update to 2.7.3 garylaski
2022-01-18 22:58 ` garylaski
2022-01-28  7:49 ` [PR PATCH] [Closed]: " ericonr
2022-01-28  7:50 ` ericonr

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=20220118225248.J10q8D8ozjNR-NUdgxOSOWgBQYJrMM-vNLOdO8tFIL0@z \
    --to=garylaski@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).