From: avoidr <avoidr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] base-files: vkpurge: fix parameter expansion in list_kernels()
Date: Sat, 15 Aug 2020 21:51:31 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24298@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 595 bytes --]
There is a new pull request by avoidr against master on the void-packages repository
https://github.com/avoidr/void-packages vkpurge
https://github.com/void-linux/void-packages/pull/24298
base-files: vkpurge: fix parameter expansion in list_kernels()
This fixes next-kernels from having too much string of their versions
stripped.
Next-kernel versions have the format "vmlinu[xz]-<ver>-next-<date>".
Thus, the string was wrongly shortened to "<date>", instead of the
correct "<ver>-next-<date>".
A patch file from https://github.com/void-linux/void-packages/pull/24298.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-vkpurge-24298.patch --]
[-- Type: text/x-diff, Size: 980 bytes --]
From 24aac5d8aacbf79a7926ff7d0f5f0d32b2503a4e Mon Sep 17 00:00:00 2001
From: avoidr <avoidr@posteo.de>
Date: Sat, 15 Aug 2020 21:10:54 +0200
Subject: [PATCH] base-files: vkpurge: fix parameter expansion in
list_kernels()
This fixes next-kernels from having too much string of their versions
stripped.
Next-kernel versions have the format "vmlinu[xz]-<ver>-next-<date>".
Thus, the string was wrongly shortened to "<date>", instead of the
correct "<ver>-next-<date>".
---
srcpkgs/base-files/files/vkpurge | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/srcpkgs/base-files/files/vkpurge b/srcpkgs/base-files/files/vkpurge
index 5519147b905..131587e5af6 100644
--- a/srcpkgs/base-files/files/vkpurge
+++ b/srcpkgs/base-files/files/vkpurge
@@ -26,7 +26,7 @@ list_kernels() {
case "$installed" in
*"$k"*) continue ;;
esac
- kver=${k##*-}
+ kver=${k#*-}
case "$kver" in
"$running") ;;
"*") ;; # /boot isn't mounted -> no vmlinu[xz]
next reply other threads:[~2020-08-15 19:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-15 19:51 avoidr [this message]
2020-08-15 19:58 ` ericonr
2020-08-15 21:12 ` avoidr
2020-08-15 21:15 ` [PR PATCH] [Updated] " avoidr
2020-08-17 0:46 ` ahesford
2020-08-18 20:33 ` q66
2020-08-18 20:46 ` ahesford
2020-08-19 0:32 ` avoidr
2020-08-19 0:52 ` ahesford
2020-08-19 1:02 ` [PR PATCH] [Closed]: " ahesford
2020-08-19 1:45 ` avoidr
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-24298@inbox.vuxu.org \
--to=avoidr@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).