From: benalb <benalb@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] crispy-doom: update to 5.11.1.
Date: Thu, 10 Feb 2022 18:36:19 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35512@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1056 bytes --]
There is a new pull request by benalb against master on the void-packages repository
https://github.com/benalb/void-packages crispy-doom
https://github.com/void-linux/void-packages/pull/35512
crispy-doom: update to 5.11.1.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
-->
<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](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)
- 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/35512.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-crispy-doom-35512.patch --]
[-- Type: text/x-diff, Size: 1117 bytes --]
From 172b5349fe743243997b409f6113ac2545dcbd5f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Benjam=C3=ADn=20Albi=C3=B1ana?= <benalb@gmail.com>
Date: Thu, 10 Feb 2022 18:35:12 +0100
Subject: [PATCH] crispy-doom: update to 5.11.1.
---
srcpkgs/crispy-doom/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/crispy-doom/template b/srcpkgs/crispy-doom/template
index a995edf9bf92..acd3fd216a33 100644
--- a/srcpkgs/crispy-doom/template
+++ b/srcpkgs/crispy-doom/template
@@ -1,6 +1,6 @@
# Template file for 'crispy-doom'
pkgname=crispy-doom
-version=5.10.3
+version=5.11.1
revision=1
wrksrc="crispy-doom-crispy-doom-${version}"
build_style=gnu-configure
@@ -11,7 +11,7 @@ maintainer="Benjamín Albiñana <benalb@gmail.com>"
license="GPL-2.0-or-later"
homepage="https://github.com/fabiangreffrath/crispy-doom"
distfiles="https://github.com/fabiangreffrath/crispy-doom/archive/crispy-doom-${version}.tar.gz"
-checksum=eef8dc26e8952b23717be3b20239fda4ee59842511328387766d1c8fe8252f6b
+checksum=7c5bb36393dec39b9732e53963dadd6bcc3bd193370c4ec5b1c0121df3b38faa
CFLAGS="-fcommon"
next reply other threads:[~2022-02-10 17:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 17:36 benalb [this message]
2022-02-10 19:10 ` [PR PATCH] [Merged]: " 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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35512@inbox.vuxu.org \
--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).