From: mintsuki <mintsuki@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] limine: update to 5.20230819.0.
Date: Sat, 19 Aug 2023 22:08:58 +0200 [thread overview]
Message-ID: <20230819200858.4x5vRrqUacbDSptJLsUAQRi4gB8QqHOOyCLcgXZsSU4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45546@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/45546
limine: update to 5.20230819.0.
#### Testing the changes
- I tested the changes in this PR: **briefly**
A patch file from https://github.com/void-linux/void-packages/pull/45546.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-limine-45546.patch --]
[-- Type: text/x-diff, Size: 1089 bytes --]
From 35137170d42df27d96751d4e0466133225ebe421 Mon Sep 17 00:00:00 2001
From: mintsuki <mintsuki@protonmail.com>
Date: Sat, 19 Aug 2023 15:08:49 -0500
Subject: [PATCH] limine: update to 5.20230819.0.
---
srcpkgs/limine/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/limine/template b/srcpkgs/limine/template
index 2b50b37491e61..433d71d749e7b 100644
--- a/srcpkgs/limine/template
+++ b/srcpkgs/limine/template
@@ -1,6 +1,6 @@
# Template file for 'limine'
pkgname=limine
-version=5.20230804.0
+version=5.20230819.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=5eb40b11717cc85cba292506280c06498a07bd42e09fbdc200ec9368fa511683
+checksum=d81c3082f5cbd6bd19ab69ebe8ea96fe9f66833ee86e06728047000404a43b5e
post_install() {
vlicense LICENSE
next prev parent reply other threads:[~2023-08-19 20:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 16:06 [PR PATCH] limine: update to 5.20230811.0 mintsuki
2023-08-19 20:01 ` [PR PATCH] [Updated] " mintsuki
2023-08-19 20:08 ` mintsuki [this message]
2023-08-19 20:22 ` limine: update to 5.20230819.0 mintsuki
2023-08-30 5:45 ` [PR PATCH] [Updated] " mintsuki
2023-08-30 5:56 ` limine: update to 5.20230830.0 mintsuki
2023-09-04 19:14 ` leahneukirchen
2023-09-04 19:19 ` leahneukirchen
2023-09-04 19:19 ` [PR PATCH] [Merged]: " leahneukirchen
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=20230819200858.4x5vRrqUacbDSptJLsUAQRi4gB8QqHOOyCLcgXZsSU4@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).