From: mintsuki <mintsuki@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] limine: update to 5.20231006.0.
Date: Wed, 18 Oct 2023 01:40:21 +0200 [thread overview]
Message-ID: <20231017234021.qBCb9EZnljEo2KpnMrQuqUCJDZ3SifP09r2hDTdLHsU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46235@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 394 bytes --]
There is an updated pull request by mintsuki against master on the void-packages repository
https://github.com/mintsuki/void-packages limine
https://github.com/void-linux/void-packages/pull/46235
limine: update to 5.20231006.0.
#### Testing the changes
- I tested the changes in this PR: **briefly**
A patch file from https://github.com/void-linux/void-packages/pull/46235.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-limine-46235.patch --]
[-- Type: text/x-diff, Size: 1088 bytes --]
From 6d067614db8692f9afc2ce7487d18bb405d36ece Mon Sep 17 00:00:00 2001
From: mintsuki <mintsuki@protonmail.com>
Date: Sun, 8 Oct 2023 15:21:07 -0500
Subject: [PATCH] limine: update to 5.20231006.0.
---
srcpkgs/limine/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/limine/template b/srcpkgs/limine/template
index efa4b424c726d..24dcdfc754083 100644
--- a/srcpkgs/limine/template
+++ b/srcpkgs/limine/template
@@ -1,6 +1,6 @@
# Template file for 'limine'
pkgname=limine
-version=5.20230917.0
+version=5.20231006.0
revision=1
build_style=gnu-configure
configure_args="--enable-all TOOLCHAIN_FOR_TARGET=llvm"
@@ -10,7 +10,7 @@ maintainer="Mintsuki <mintsuki@protonmail.com>"
license="BSD-2-Clause"
homepage="https://limine-bootloader.org/"
distfiles="https://github.com/limine-bootloader/limine/releases/download/v${version}/limine-${version}.tar.xz"
-checksum=2d9b55e798e951ebd3d4266303e9cefda2ee9f7055a3c877dc7e306f0e94ec91
+checksum=e759bc39a59d07260d5def19bff5cd6e3f6147708e691383af7b09c33d00e347
post_install() {
vlicense LICENSE
next prev parent reply other threads:[~2023-10-17 23:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 0:10 [PR PATCH] limine: update to 5.20230924.0 mintsuki
2023-09-28 12:17 ` [PR PATCH] [Updated] " mintsuki
2023-09-28 21:48 ` [PR PATCH] [Updated] limine: update to 5.20230928.0 mintsuki
2023-09-28 23:06 ` [PR PATCH] [Updated] limine: update to 5.20230928.1 mintsuki
2023-10-06 17:47 ` [PR PATCH] [Updated] limine: update to 5.20230928.2 mintsuki
2023-10-06 18:04 ` [PR PATCH] [Updated] limine: update to 5.20231006.0 mintsuki
2023-10-08 20:21 ` mintsuki
2023-10-17 23:40 ` mintsuki [this message]
2023-10-22 20:08 ` [PR PATCH] [Closed]: " mintsuki
2023-10-22 20:13 [PR PATCH] " mintsuki
2023-10-24 17:17 ` [PR PATCH] [Updated] " mintsuki
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=20231017234021.qBCb9EZnljEo2KpnMrQuqUCJDZ3SifP09r2hDTdLHsU@z \
--to=mintsuki@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).