From: ACR-Jeff <ACR-Jeff@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: kodi build errors
Date: Sun, 30 Jun 2024 23:08:11 +0200 [thread overview]
Message-ID: <20240630210811.364F826B0F@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-51033@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1051 bytes --]
New comment by ACR-Jeff on void-packages repository
https://github.com/void-linux/void-packages/issues/51033#issuecomment-2198757321
Comment:
> This issue is indirectly resolved by #50183 (see https://github.com/void-linux/void-packages/pull/50183/files#diff-e773acf9a4e8390c3709adf717c186f6856c69ed5c2a6b5850260212d0ba7b98)
Thank you,
I read the Handling-Patches Man page https://github.com/void-linux/void-packages/blob/master/Manual.md#handling-patches
Read through https://github.com/void-linux/void-packages/pull/50183
Followed through with adding the patch you've posted above in reference
https://github.com/void-linux/void-packages/pull/50183/files#diff-e773acf9a4e8390c3709adf717c186f6856c69ed5c2a6b5850260212d0ba7b98
But the same issue occurred,
1. I proceeded to removing any previous build attempts from /hostdir/sources to be sure not to contaminate any further builds
2. cd to/path/void-packages
3. ./xbps-src pkg kodi
4. Same issue occurred
Am I doing something incorrect or missing something to apply the patch, Etc?
next prev parent reply other threads:[~2024-06-30 21:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 9:42 [ISSUE] " ACR-Jeff
2024-06-29 13:59 ` meator
2024-06-30 21:05 ` ACR-Jeff
2024-06-30 21:08 ` ACR-Jeff [this message]
2024-06-30 22:03 ` meator
2024-07-04 2:28 ` ACR-Jeff
2024-07-04 3:36 ` sgn
2024-07-04 8:42 ` ACR-Jeff
2024-07-05 2:24 ` ACR-Jeff
2024-07-05 2:24 ` [ISSUE] [CLOSED] " ACR-Jeff
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=20240630210811.364F826B0F@inbox.vuxu.org \
--to=acr-jeff@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).