From: sirkhancision <sirkhancision@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] wine: fix path to patchinstall in wine-staging
Date: Wed, 22 Mar 2023 07:30:46 +0100 [thread overview]
Message-ID: <20230322063046.3VESmqBI51tq7RdLDL0lYxC0a792060Ftxhpua0Yz9A@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42912@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 540 bytes --]
There is an updated pull request by sirkhancision against master on the void-packages repository
https://github.com/sirkhancision/void-packages wine-staging
https://github.com/void-linux/void-packages/pull/42912
wine: fix path to patchinstall in wine-staging
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### Local build testing
- I built this PR locally for my native architecture, x86_64-glibc
Resolves #42911
A patch file from https://github.com/void-linux/void-packages/pull/42912.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-wine-staging-42912.patch --]
[-- Type: text/x-diff, Size: 673 bytes --]
From 65dc4b05d8e1148e534fa41c68930de834424e75 Mon Sep 17 00:00:00 2001
From: sirkhancision <jsantiago12tone@gmail.com>
Date: Tue, 21 Mar 2023 21:06:03 -0300
Subject: [PATCH] wine: fix path to patchinstall in wine-staging
---
srcpkgs/wine/template | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/srcpkgs/wine/template b/srcpkgs/wine/template
index f2af67df507d..e715f8f559b2 100644
--- a/srcpkgs/wine/template
+++ b/srcpkgs/wine/template
@@ -76,7 +76,7 @@ fi
post_patch() {
if [ "${build_option_staging}" ]; then
- "../wine-staging-${_pkgver}/patches/patchinstall.sh" --all
+ "../wine-staging-${_pkgver}/staging/patchinstall.py" --all
fi
}
next prev parent reply other threads:[~2023-03-22 6:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 0:10 [PR PATCH] " sirkhancision
2023-03-22 2:24 ` [PR REVIEW] " sgn
2023-03-22 2:26 ` sirkhancision
2023-03-22 2:27 ` sirkhancision
2023-03-22 6:29 ` sirkhancision
2023-03-22 6:30 ` sirkhancision [this message]
2023-03-26 7:22 ` [PR PATCH] [Merged]: " Hoshpak
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=20230322063046.3VESmqBI51tq7RdLDL0lYxC0a792060Ftxhpua0Yz9A@z \
--to=sirkhancision@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).