Github messages for voidlinux
 help / color / mirror / Atom feed
From: zen0bit <zen0bit@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] legenadry: update to 0.20.32
Date: Fri, 06 Jan 2023 15:24:58 +0100	[thread overview]
Message-ID: <20230106142458.sz0Ukn7OF5sAMwHLJxPOWw4JsW0XKhoTu6qkZFGpAmY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41492@inbox.vuxu.org>

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

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

https://github.com/oSoWoSo/VUR legendary
https://github.com/void-linux/void-packages/pull/41492

legenadry: update to 0.20.32
#### Testing the changes
- I tested the changes in this PR: **briefly**

#### Local build testing
- I built this PR locally for my native architecture, (x64 glibc)

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

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

From 7f97e52e884ebc934679bbc713f8fece7aa89286 Mon Sep 17 00:00:00 2001
From: zenobit <zen@osowoso.xyz>
Date: Fri, 6 Jan 2023 14:32:41 +0100
Subject: [PATCH] legenadry: update to 0.20.32

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

diff --git a/srcpkgs/legendary/template b/srcpkgs/legendary/template
index 6684f066ead5..36efd1ce0854 100644
--- a/srcpkgs/legendary/template
+++ b/srcpkgs/legendary/template
@@ -1,6 +1,6 @@
 # Template file for 'legendary'
 pkgname=legendary
-version=0.20.31
+version=0.20.32
 revision=1
 build_style=python3-module
 hostmakedepends="python3-setuptools"
@@ -10,5 +10,5 @@ maintainer="Lorem <notloremipsum@protonmail.com>"
 license="GPL-3.0-or-later"
 homepage="https://github.com/derrod/legendary"
 distfiles="https://github.com/derrod/legendary/archive/${version}.tar.gz"
-checksum=2dd1087d5d6718209afb275499602376211db82eb4bec0be38f2f8a502ed5e06
+checksum=eb74f1476923aa1fe800fcf9b91fde4fe5ab9c027fa72a69313cf483e34fdec8
 make_check=no # doesn't contain any tests

  parent reply	other threads:[~2023-01-06 14:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-06 13:34 [PR PATCH] " zen0bit
2023-01-06 14:16 ` [PR PATCH] [Updated] " zen0bit
2023-01-06 14:24 ` zen0bit [this message]
2023-01-06 19:20 ` [PR PATCH] [Merged]: " Johnnynator

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=20230106142458.sz0Ukn7OF5sAMwHLJxPOWw4JsW0XKhoTu6qkZFGpAmY@z \
    --to=zen0bit@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).