From: hk0O7 <hk0O7@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: kodi-addon-inputstream-adaptive: update to 19.0.7
Date: Wed, 18 Oct 2023 00:48:37 +0200 [thread overview]
Message-ID: <20231017224837.4TTtTHYha03k9n6nGDJLWs4MLnCrq4XGKpVEGK9995g@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46429@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1586 bytes --]
New comment by hk0O7 on void-packages repository
https://github.com/void-linux/void-packages/pull/46429#issuecomment-1767313356
Comment:
As suspected, check build jobs keep [failing](https://github.com/void-linux/void-packages/actions/runs/6484183866/job/17767201133#step:7:14) due to the first [tags](https://github.com/xbmc/inputstream.adaptive/tags) page `$url` (in [update_check.sh](https://github.com/void-linux/void-packages/blob/master/common/xbps-src/shutils/update_check.sh)) not returning any `href`s matching the default pattern (`$rx`). This is both because it doesn't match version numbers followed by Kodi release names and because the latest version for Matrix is too old to show up there (only from the second page onwards as of now).
As per the [manual](https://github.com/void-linux/void-packages/blob/master/common/xbps-src/shutils/update_check.sh) I've tried using `$vdsuffix` but `update_check.sh` will only use it for the _common_ `$distfiles` URLs (like `*github.com*` in this case), so I've also tried a whole `$pattern` based on the default one:
```
pattern='/archive/refs/tags/(v?|\Q'"${pkgname}"'\E[-_])?\K[\d.]+\Q'"-${_kodi_release}"'\E(?=\.tar\.gz")'
```
which does match when I try switching the `$_kodi_release` to `Nexus` or `Omega` (with the current `Matrix` one still yielding `NO VERSION found for kodi-addon-inputstream-adaptive`).
So it looks like we have no choice other than to disable the update check until we finally update [kodi](https://github.com/void-linux/void-packages/tree/master/srcpkgs/kodi) to the current stable release.
next prev parent reply other threads:[~2023-10-17 22:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 13:16 [PR PATCH] Update template hk0O7
2023-10-04 13:21 ` abenson
2023-10-04 16:13 ` [PR PATCH] [Updated] kodi-addon-inputstream-adaptive: update to 19.0.7 hk0O7
2023-10-04 16:49 ` hk0O7
2023-10-04 16:57 ` hk0O7
2023-10-04 18:30 ` [PR PATCH] [Updated] " hk0O7
2023-10-04 18:38 ` hk0O7
2023-10-04 19:19 ` hk0O7
2023-10-04 19:24 ` hk0O7
2023-10-05 18:49 ` hk0O7
2023-10-11 14:45 ` [PR PATCH] [Updated] " hk0O7
2023-10-11 14:50 ` hk0O7
2023-10-17 22:48 ` hk0O7 [this message]
2023-10-17 23:04 ` [PR PATCH] [Updated] " hk0O7
2023-10-25 15:46 ` hk0O7
2023-10-25 15:49 ` hk0O7
2023-10-25 16:00 ` hk0O7
2023-11-02 11:39 ` hk0O7
2024-02-01 1:45 ` github-actions
2024-02-04 21:01 ` hk0O7
2024-05-05 1:46 ` github-actions
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=20231017224837.4TTtTHYha03k9n6nGDJLWs4MLnCrq4XGKpVEGK9995g@z \
--to=hk0o7@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).