Github messages for voidlinux
 help / color / mirror / Atom feed
From: the-maldridge <the-maldridge@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: kodi: update to 19.3.
Date: Tue, 05 Apr 2022 02:03:53 +0200	[thread overview]
Message-ID: <20220405000353.52j70Xrp0yresa9ofKYITNQXJh_OsTVgtMBGjptEfGg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34083@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1321 bytes --]

There's a closed pull request on the void-packages repository

kodi: update to 19.3.
https://github.com/void-linux/void-packages/pull/34083

Description:
Update patches to match.  (Is there a way to do that other than cloning the upstream, making the changes by hand, and doing a `git diff`?)

<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
I **briefly** tested the changes in this PR. It installs fine on a Pi 4 (`aarch64`), although there were setup pains — on both `19.0` and `.3` — that forced me toward LibreELEC instead.


<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->

<!-- 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, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl
  - armv7l
  - armv6l-musl
-->


  parent reply	other threads:[~2022-04-05  0:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-14 22:09 [PR PATCH] " Goorzhel
2021-11-14 22:49 ` Goorzhel
2021-11-14 22:49 ` Goorzhel
2021-11-15  1:33 ` Goorzhel
2021-11-15  1:35 ` Goorzhel
2021-11-15  2:29 ` Goorzhel
2021-11-15  6:02 ` [PR PATCH] [Updated] " Goorzhel
2021-11-16 23:52 ` Goorzhel
2021-12-04  4:32 ` ericonr
2021-12-04  4:33 ` [PR PATCH] [Updated] " Goorzhel
2021-12-04  4:39 ` Goorzhel
2021-12-04  4:39 ` Goorzhel
2021-12-04  4:42 ` ericonr
2022-04-04 23:11 ` marmeladema
2022-04-05  0:03 ` the-maldridge [this message]
2022-04-05  0:03 ` the-maldridge

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=20220405000353.52j70Xrp0yresa9ofKYITNQXJh_OsTVgtMBGjptEfGg@z \
    --to=the-maldridge@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).