From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: fmt: update to 7.0.1
Date: Tue, 07 Jul 2020 20:05:30 +0200 [thread overview]
Message-ID: <20200707180530.arq3U8SPVPfcfNTUE6B2XK3UiaI8xxtM7CbJ4-9ORk0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23451@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 801 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/23451#issuecomment-655031954
Comment:
Please fix the `python_version` failure. The two files affected by `python_version` appear to be
```
/usr/share/kodi/addons/service.xbmc.versioncheck/service.py
/usr/share/kodi/addons/service.xbmc.versioncheck/lib/viewer.py
```
and, at first glance, appear to be compatible with Python 3. In that case, `python_version=3` is probably acceptable. If you know for a fact that these only work with Python 2, then remove the `#unverified` comment.
Looking at the files, it's not clear to me that they will even run; I don't see where the `xbmc`, `xbmcgui` or `xbmcaddon` modules are provided in any Void package. However, I am wholly unfamiliar with kodi.
next prev parent reply other threads:[~2020-07-07 18:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 16:26 [PR PATCH] " toluschr
2020-07-07 16:55 ` ericonr
2020-07-07 17:09 ` [PR PATCH] [Updated] " toluschr
2020-07-07 17:10 ` toluschr
2020-07-07 18:05 ` ahesford [this message]
2020-07-07 18:11 ` toluschr
2020-07-07 18:17 ` ahesford
2020-07-07 18:25 ` ericonr
2020-07-07 21:02 ` ericonr
2020-07-07 21:02 ` ericonr
2020-07-07 21:17 ` ahesford
2020-07-08 10:41 ` [PR PATCH] [Updated] " toluschr
2020-10-09 19:31 ` [PR PATCH] [Closed]: " 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=20200707180530.arq3U8SPVPfcfNTUE6B2XK3UiaI8xxtM7CbJ4-9ORk0@z \
--to=ahesford@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).