From: jnbr <jnbr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] findutils: fix tests
Date: Tue, 03 Nov 2020 21:43:01 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26111@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 301 bytes --]
There is a new pull request by jnbr against master on the void-packages repository
https://github.com/jnbr/void-packages findutils
https://github.com/void-linux/void-packages/pull/26111
findutils: fix tests
A patch file from https://github.com/void-linux/void-packages/pull/26111.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-findutils-26111.patch --]
[-- Type: text/x-diff, Size: 966 bytes --]
From 09cc0af3773c879d27668310244b2247b00b5bdf Mon Sep 17 00:00:00 2001
From: Johannes <johannes.brechtmann@gmail.com>
Date: Tue, 3 Nov 2020 21:20:48 +0100
Subject: [PATCH] findutils: fix tests
---
srcpkgs/findutils/template | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/srcpkgs/findutils/template b/srcpkgs/findutils/template
index 2155bdd80bd..dac19bad8de 100644
--- a/srcpkgs/findutils/template
+++ b/srcpkgs/findutils/template
@@ -25,7 +25,9 @@ post_extract() {
pre_check() {
# LFS reccomends disabling this due to to the possibility of looping forever on some machines
# see: http://www.linuxfromscratch.org/lfs/view/development/chapter06/findutils.html
- sed -i 's/test-lock..EXEEXT.//' tests/Makefile.in
+ vsed -i 's/test-lock..EXEEXT.//' gnulib-tests/Makefile
+ # help-version is broken because we do not build locate
+ vsed -i "/tests\/misc\/help-version.sh/d" Makefile
}
post_configure() {
make -C locate dblocation.texi
next reply other threads:[~2020-11-03 20:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 20:43 jnbr [this message]
2020-11-06 20:35 ` [PR PATCH] [Merged]: " jnbr
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-26111@inbox.vuxu.org \
--to=jnbr@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).