From: clyhtsuriva <clyhtsuriva@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Git 2.35.0
Date: Tue, 25 Jan 2022 13:11:39 +0100 [thread overview]
Message-ID: <20220125121139.VmgINo8oEa6quBDuAKubOMlHRPLKm3RoBUAVB2poZ9k@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35227@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1126 bytes --]
New comment by clyhtsuriva on void-packages repository
https://github.com/void-linux/void-packages/pull/35227#issuecomment-1021102225
Comment:
It seems that the patch coming with chroot-git has to be deleted as well. It's the culprit making the checks fail.
```
=> chroot-git-2.35.0_1: patching: 0001-Makefile-fix-parallel-build-race.patch.
1 out of 1 hunk FAILED -- saving rejects to file Makefile.rej
=> ERROR: chroot-git-2.35.0_1: do-patch_00-patches: 'patch -s ${_args} -i ${_patch} 2> /dev/null' exited with 1
=> ERROR: in _process_patch() at common/hooks/do-patch/00-patches.sh:34
=> ERROR: in hook() at common/hooks/do-patch/00-patches.sh:51
=> ERROR: in run_func() at common/xbps-src/shutils/common.sh:21
=> ERROR: in run_pkg_hooks() at common/xbps-src/shutils/common.sh:245
=> ERROR: in run_step() at common/xbps-src/shutils/common.sh:71
=> ERROR: in main() at common/xbps-src/libexec/xbps-src-dopatch.sh:33
Error: Process completed with exit code 1.
```
Edit : I cross-compiled the two packages and briefly tested them and everything seems fine, once the patch for chroot-git removed :)
next prev parent reply other threads:[~2022-01-25 12:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 11:10 [PR PATCH] " sgn
2022-01-25 11:43 ` clyhtsuriva
2022-01-25 11:47 ` clyhtsuriva
2022-01-25 11:51 ` clyhtsuriva
2022-01-25 12:11 ` clyhtsuriva [this message]
2022-01-26 2:11 ` [PR PATCH] [Updated] " sgn
2022-01-26 16:22 ` [PR PATCH] [Merged]: " sgn
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=20220125121139.VmgINo8oEa6quBDuAKubOMlHRPLKm3RoBUAVB2poZ9k@z \
--to=clyhtsuriva@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).