From: Goorzhel <Goorzhel@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: python3-click: update to 8.1.3.
Date: Wed, 22 Jun 2022 04:28:34 +0200 [thread overview]
Message-ID: <20220622022834.nNV8jFHzMlBBpYnicYusxBTBYhVwSXssJ1WXVNSqU-4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37629@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1681 bytes --]
New comment by Goorzhel on void-packages repository
https://github.com/void-linux/void-packages/pull/37629#issuecomment-1162558643
Comment:
`fava` has adopted PEP 517 sometime between 1.18 and 1.21. Updating it leads to another brick wall, however:
<details>
<summary>git diff srcpkgs/fava/template</summary>
```diff
diff --git a/srcpkgs/fava/template b/srcpkgs/fava/template
index 9b0f83e540..87339be552 100644
--- a/srcpkgs/fava/template
+++ b/srcpkgs/fava/template
@@ -3,3 +3,3 @@ pkgname=fava
-version=1.18
-revision=2
-build_style=python3-module
+version=1.21
+revision=1
+build_style=python3-pep517
@@ -9 +9 @@ depends="python3-Babel python3-Cheroot python3-Flask-Babel python3-Flask
- python3-simplejson python3-Werkzeug python3-aiohttp"
+ python3-simplejson python3-Werkzeug python3-aiohttp python3-wheel"
@@ -16 +16 @@ distfiles="${PYPI_SITE}/f/fava/fava-${version}.tar.gz"
-checksum=21336b695708497e6f00cab77135b174c51feb2713b657e0e208282960885bf5
+checksum=d1a1422848e65e7eb275d80d322f6de2bcea1dc37b5412e8cf72c483d6a998d6
```
</details>
```
=> fava-1.21_1: running do_check ...
ImportError while loading conftest '/builddir/fava-1.21/tests/conftest.py'.
tests/conftest.py:19: in <module>
from fava.application import _load_file
build/lib/fava/application.py:40: in <module>
from fava import __version__ as fava_version
E ImportError: cannot import name '__version__' from 'fava' (/builddir/fava-1.21/build/lib/fava/__init__.py)
=> ERROR: fava-1.21_1: do_check: 'PYTHONPATH="$PWD/build/lib" python3 -m pytest tests -k 'not cli and not static_url'' exited with 4
=> ERROR: in do_check() at srcpkgs/fava/template:20
```
next prev parent reply other threads:[~2022-06-22 2:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 0:14 [PR PATCH] " Goorzhel
2022-06-21 0:14 ` Goorzhel
2022-06-21 0:38 ` Goorzhel
2022-06-22 2:28 ` Goorzhel [this message]
2022-06-22 2:39 ` Goorzhel
2022-06-22 2:39 ` Goorzhel
2022-06-22 3:46 ` Goorzhel
2022-06-22 11:53 ` leahneukirchen
2022-06-22 12:11 ` leahneukirchen
2022-06-24 1:05 ` Goorzhel
2022-06-24 1:06 ` [PR PATCH] [Updated] " Goorzhel
2022-06-24 2:50 ` Goorzhel
2022-06-24 3:03 ` Goorzhel
2022-06-24 3:04 ` Goorzhel
2022-06-24 15:36 ` ahesford
2022-06-24 16:48 ` [PR PATCH] [Updated] " leahneukirchen
2022-06-24 18:45 ` paper42
2022-06-24 18:49 ` leahneukirchen
2022-06-24 19:28 ` icp1994
2022-06-24 19:38 ` [PR PATCH] [Updated] " leahneukirchen
2022-06-24 19:52 ` [PR PATCH] [Merged]: " leahneukirchen
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=20220622022834.nNV8jFHzMlBBpYnicYusxBTBYhVwSXssJ1WXVNSqU-4@z \
--to=goorzhel@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).