From: icp1994 <icp1994@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] chroot-grep: patch out problematic warnings in egrep and fgrep.
Date: Thu, 12 Jan 2023 08:27:06 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41593@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 493 bytes --]
There is a new pull request by icp1994 against master on the void-packages repository
https://github.com/icp1994/void-packages egrep
https://github.com/void-linux/void-packages/pull/41593
chroot-grep: patch out problematic warnings in egrep and fgrep.
This mirrors the changes from grep in https://github.com/void-linux/void-packages/commit/ef5ffe4d696b31041c272be92e912fb454c075ac into chroot-grep.
A patch file from https://github.com/void-linux/void-packages/pull/41593.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-egrep-41593.patch --]
[-- Type: text/x-diff, Size: 1476 bytes --]
From 6aab3a8f07f8dcc4a12bcacc07ec49720e01d961 Mon Sep 17 00:00:00 2001
From: icp <pangolin@vivaldi.net>
Date: Thu, 12 Jan 2023 01:37:31 +0530
Subject: [PATCH] chroot-grep: patch out problematic warnings in egrep and
fgrep.
---
.../chroot-grep/patches/efgrep-remove-warning.patch | 10 ++++++++++
srcpkgs/chroot-grep/template | 2 +-
2 files changed, 11 insertions(+), 1 deletion(-)
create mode 100644 srcpkgs/chroot-grep/patches/efgrep-remove-warning.patch
diff --git a/srcpkgs/chroot-grep/patches/efgrep-remove-warning.patch b/srcpkgs/chroot-grep/patches/efgrep-remove-warning.patch
new file mode 100644
index 000000000000..6371301688f0
--- /dev/null
+++ b/srcpkgs/chroot-grep/patches/efgrep-remove-warning.patch
@@ -0,0 +1,10 @@
+since 3.8, egrep and fgrep print a warning which can cause many issues with
+programs not expecting this behaviour
+
+--- a/src/egrep.sh
++++ b/src/egrep.sh
+@@ -1,4 +1,3 @@
+ #!@SHELL@
+ cmd=${0##*/}
+-echo "$cmd: warning: $cmd is obsolescent; using @grep@ @option@" >&2
+ exec @grep@ @option@ "$@"
diff --git a/srcpkgs/chroot-grep/template b/srcpkgs/chroot-grep/template
index 6a99116d4b5d..7b68ca9348b8 100644
--- a/srcpkgs/chroot-grep/template
+++ b/srcpkgs/chroot-grep/template
@@ -1,7 +1,7 @@
# Template file for 'chroot-grep'
pkgname=chroot-grep
version=3.8
-revision=1
+revision=2
bootstrap=yes
build_style=gnu-configure
configure_args="--disable-perl-regexp --disable-nls ac_cv_path_GREP=grep"
next reply other threads:[~2023-01-12 7:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 7:27 icp1994 [this message]
2023-01-12 7:28 ` paper42
2023-01-12 7:32 ` icp1994
2023-01-12 17:15 ` [PR PATCH] [Merged]: " Vaelatern
2023-01-12 18:30 ` paper42
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-41593@inbox.vuxu.org \
--to=icp1994@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).