Github messages for voidlinux
 help / color / mirror / Atom feed
From: benalb <benalb@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] doomretro: update to 5.1.
Date: Tue, 12 Dec 2023 08:13:06 +0100	[thread overview]
Message-ID: <20231212071306.oP1KTK_RezNrPEYOgZAcKa4bLTqQrScugsxB24Rql14@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47673@inbox.vuxu.org>

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

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

https://github.com/benalb/void-packages doomretro
https://github.com/void-linux/void-packages/pull/47673

doomretro: update to 5.1.
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**

<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-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, (X86_64-LIBC)


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

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

From b27515e6cc4ff0509111656b2685f29fad885a07 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Benjam=C3=ADn=20Albi=C3=B1ana?= <benalb@gmail.com>
Date: Sun, 10 Dec 2023 08:55:37 +0100
Subject: [PATCH] doomretro: update to 5.1.1.

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

diff --git a/srcpkgs/doomretro/template b/srcpkgs/doomretro/template
index cd2cac37113fb..3e2c212354252 100644
--- a/srcpkgs/doomretro/template
+++ b/srcpkgs/doomretro/template
@@ -1,6 +1,6 @@
 # Template file for 'doomretro'
 pkgname=doomretro
-version=5.0.7
+version=5.1.1
 revision=1
 build_style=cmake
 hostmakedepends="pkg-config"
@@ -11,4 +11,4 @@ license="GPL-3.0-or-later"
 homepage="https://www.doomretro.com"
 changelog="https://raw.githubusercontent.com/bradharding/doomretro/master/releasenotes.md"
 distfiles="https://github.com/bradharding/doomretro/archive/v${version}.tar.gz"
-checksum=ef2b8d88d69522b69a1173903729bcdbb1d984a6e3f363b71e1a92e830774b81
+checksum=7aa760d058e9f29891e13fdb720c8e307f60c992e64f0deff7447b6138ed2275

  reply	other threads:[~2023-12-12  7:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-10  7:57 [PR PATCH] " benalb
2023-12-12  7:13 ` benalb [this message]
2023-12-16  8:32 ` [PR PATCH] [Closed]: doomretro: update to 5.1.1 benalb

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=20231212071306.oP1KTK_RezNrPEYOgZAcKa4bLTqQrScugsxB24Rql14@z \
    --to=benalb@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).