From: Chocimier <Chocimier@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] hooks/99-pkglint.sh: make missing shlib entry not a warning
Date: Thu, 21 Apr 2022 18:36:56 +0200 [thread overview]
Message-ID: <20220421163656.J0xVX5s4AIa4ziwZu-oJlQPTx5DwpBq6uI6yD8Teq9k@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32774@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 449 bytes --]
There is an updated pull request by Chocimier against master on the void-packages repository
https://github.com/Chocimier/void-packages-org shlibs-warning
https://github.com/void-linux/void-packages/pull/32774
hooks/99-pkglint.sh: make missing shlib entry not a warning
Message is useful, but when it is a warning, clueless people add *any* missing entry.
A patch file from https://github.com/void-linux/void-packages/pull/32774.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-shlibs-warning-32774.patch --]
[-- Type: text/x-diff, Size: 853 bytes --]
From 114d15196d3fc0a875027267e27af3baf801953f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Piotr=20W=C3=B3jcik?= <chocimier@tlen.pl>
Date: Tue, 31 Aug 2021 21:00:01 +0200
Subject: [PATCH] hooks/99-pkglint.sh: make missing shlib entry not a warning
---
common/hooks/pre-pkg/99-pkglint.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/common/hooks/pre-pkg/99-pkglint.sh b/common/hooks/pre-pkg/99-pkglint.sh
index ea73c961ec5b..325938f5d541 100644
--- a/common/hooks/pre-pkg/99-pkglint.sh
+++ b/common/hooks/pre-pkg/99-pkglint.sh
@@ -182,7 +182,7 @@ hook() {
if [ -z "$found" ]; then
_myshlib="${libname}.so"
[ "${_myshlib}" != "${rev}" ] && _myshlib+=".${rev}"
- msg_warn "${pkgver}: ${_myshlib} not found in common/shlibs!\n"
+ msg_normal "${pkgver}: ${_myshlib} not found in common/shlibs.\n"
fi;
}
done
next prev parent reply other threads:[~2022-04-21 16:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 19:02 [PR PATCH] " Chocimier
2022-04-21 16:36 ` Chocimier [this message]
2022-04-22 19:55 ` [PR PATCH] [Merged]: " Chocimier
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=20220421163656.J0xVX5s4AIa4ziwZu-oJlQPTx5DwpBq6uI6yD8Teq9k@z \
--to=chocimier@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).