From: the-maldridge <the-maldridge@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] vboot-utils: Add update check
Date: Sat, 06 Feb 2021 10:19:56 +0100 [thread overview]
Message-ID: <20210206091956.jYr_l_4AfkA-gxKCwT9GL04GtzFIvCbzZzUCmtbUhms@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28510@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 603 bytes --]
There is an updated pull request by the-maldridge against master on the void-packages repository
https://github.com/the-maldridge/void-packages vboot-update
https://github.com/void-linux/void-packages/pull/28510
vboot-utils: Add update check
Adds an update check that parses the git revision. Also removes the need to keep track of a separate git hash. Resolves complaint surfaced in #28507, but does not actually update the package as I have no time nor resources to test the functionality of this package.
A patch file from https://github.com/void-linux/void-packages/pull/28510.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-vboot-update-28510.patch --]
[-- Type: text/x-diff, Size: 1302 bytes --]
From 168ea91b3b5b12f618b22502fe7b6286c94ea5f3 Mon Sep 17 00:00:00 2001
From: Michael Aldridge <maldridge@VoidLinux.org>
Date: Fri, 5 Feb 2021 00:56:53 -0800
Subject: [PATCH] vboot-utils: Add update check
---
srcpkgs/vboot-utils/template | 2 +-
srcpkgs/vboot-utils/update | 3 +++
2 files changed, 4 insertions(+), 1 deletion(-)
create mode 100644 srcpkgs/vboot-utils/update
diff --git a/srcpkgs/vboot-utils/template b/srcpkgs/vboot-utils/template
index 46871f18f25..61068975964 100644
--- a/srcpkgs/vboot-utils/template
+++ b/srcpkgs/vboot-utils/template
@@ -8,7 +8,7 @@ hostmakedepends="pkg-config git"
makedepends="libressl-devel libuuid-devel liblzma-devel libyaml-devel"
short_desc="Verified boot kernel utilities"
maintainer="Enno Boland <gottox@voidlinux.org>"
-license="BSD"
+license="BSD-3-Clause"
homepage="https://chromium.googlesource.com/chromiumos/platform/vboot_reference.git"
CFLAGS='-D_GNU_SOURCE -Wno-error -fcommon'
diff --git a/srcpkgs/vboot-utils/update b/srcpkgs/vboot-utils/update
new file mode 100644
index 00000000000..e360ec80b5c
--- /dev/null
+++ b/srcpkgs/vboot-utils/update
@@ -0,0 +1,3 @@
+site="https://chromium.googlesource.com/chromiumos/platform/vboot_reference.git/+refs?format=TEXT"
+pattern='refs/heads/release-R\K[\d]+-[\d]+'
+version=${version//./-}
next prev parent reply other threads:[~2021-02-06 9:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 8:58 [PR PATCH] " the-maldridge
2021-02-05 9:02 ` [PR PATCH] [Updated] " the-maldridge
2021-02-05 10:16 ` [PR REVIEW] " Gottox
2021-02-05 10:17 ` Gottox
2021-02-05 11:26 ` fosslinux
2021-02-05 11:26 ` fosslinux
2021-02-05 13:33 ` ericonr
2021-02-05 16:44 ` Gottox
2021-02-05 16:45 ` Gottox
2021-02-05 16:47 ` Gottox
2021-02-05 17:02 ` Gottox
2021-02-05 17:40 ` [PR REVIEW] " ericonr
2021-02-05 17:45 ` Gottox
2021-02-05 22:23 ` fosslinux
2021-02-05 22:34 ` Gottox
2021-02-05 22:40 ` Johnnynator
2021-02-05 22:48 ` Gottox
2021-02-06 9:19 ` the-maldridge [this message]
2021-02-06 9:21 ` [PR PATCH] [Updated] " the-maldridge
2021-02-06 9:33 ` [PR PATCH] [Merged]: " the-maldridge
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=20210206091956.jYr_l_4AfkA-gxKCwT9GL04GtzFIvCbzZzUCmtbUhms@z \
--to=the-maldridge@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).