From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: wxWidgets: correct patch
Date: Tue, 11 Jan 2022 21:39:32 +0100 [thread overview]
Message-ID: <20220111203932.Ce9Ts_3PHpcFeZUbWe2f98XqzzS2t1TYSHAb1DlWL4c@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34963@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1351 bytes --]
There's a closed pull request on the void-packages repository
wxWidgets: correct patch
https://github.com/void-linux/void-packages/pull/34963
Description:
Tweak the wxWidgets patches so that they apply cleanly to Makefile.in
Unclear why it's needed, perhaps patch(1) has now less tolerance for whitespace mixups.
Without these changes, the patches report fuzz and failure for Makefile.in:
patching file Makefile.in
Hunk #1 succeeded at 15279 with fuzz 2 (offset 21 lines).
patching file Makefile.in
Hunk #1 FAILED at 16177.
Hunk #2 succeeded at 16187 (offset 34 lines).
Hunk #3 succeeded at 16204 (offset 34 lines).
1 out of 3 hunks FAILED -- saving rejects to file Makefile.in.rej
patching file build/bakefiles/wx.bkl
patching file src/common/translation.cpp
patching file utils/wxrc/Makefile.in
Hunk #1 succeeded at 119 (offset -6 lines).
#### Testing the changes
- I tested the changes in this PR: **briefly**
<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration)
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
next prev parent reply other threads:[~2022-01-11 20:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-09 14:42 [PR PATCH] " chexum
2022-01-09 14:44 ` [PR PATCH] [Updated] " chexum
2022-01-09 16:09 ` newbluemoon
2022-01-11 20:39 ` ericonr [this message]
2022-01-11 20:39 ` ericonr
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=20220111203932.Ce9Ts_3PHpcFeZUbWe2f98XqzzS2t1TYSHAb1DlWL4c@z \
--to=ericonr@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).