Search Criteria
Package Details: python-asyncclick 8.1.8-2
Package Actions
Git Clone URL: | https://aur.archlinux.org/python-asyncclick.git (read-only, click to copy) |
---|---|
Package Base: | python-asyncclick |
Description: | Composable command line interface toolkit, async version |
Upstream URL: | https://github.com/python-trio/asyncclick |
Licenses: | BSD |
Submitter: | wuestengecko |
Maintainer: | wuestengecko |
Last Packager: | wuestengecko |
Votes: | 0 |
Popularity: | 0.000000 |
First Submitted: | 2021-08-19 13:12 (UTC) |
Last Updated: | 2025-01-07 16:19 (UTC) |
Dependencies (11)
- python (python37AUR, python311AUR, python310AUR)
- python-anyio
- git (git-gitAUR, git-glAUR) (make)
- python-build (make)
- python-flit-core (make)
- python-installer (make)
- python-wheel (make)
- python-pytest (check)
- python-trio (check)
- python-curio (optional) – Alternative async event loop
- python-trio (optional) – Alternative async event loop
Latest Comments
wuestengecko commented on 2025-01-07 21:25 (UTC)
I'm not sure what you mean. I did bump the pkgrel, so the package is at version
8.1.8-2
instead of8.1.8-1
now. Both are packaging upstream version 8.1.8, but -2 is considered newer, and therefore clearly the "right" one.If you were talking about the Git repo, I've gone ahead and opened an issue to make the maintainers there aware of this, but that's about all I can do about this :)
gbin commented on 2025-01-07 19:44 (UTC)
no worries but now there are 2 versions of the same package in the mirrors etc.. and people might wonder which one is the right one. I would bump it.
wuestengecko commented on 2025-01-07 18:43 (UTC)
@gbin You need to delete the old
asyncclick-8.1.8.tar.gz
source tarball.There was some mixup happening on the asyncclick Github, and the click release tag got pushed into the asyncclick repo. This PKGBUILD used to grab the source straight from the latest Github tag, and because that was now basically pointing to the wrong package, it had downloaded the wrong source. If you delete that, it will simply download the correct one from PyPI.
It doesn't look like there was anything malicious here. It was the real click release, without any changes, so it really just looks like a mistake. Sadly I didn't catch that in time, because I don't have
python-click
installed on the machine where I build, and I didn't get around to fully test this release on one that does before pushing.gbin commented on 2025-01-07 18:26 (UTC) (edited on 2025-01-07 18:28 (UTC) by gbin)
oh Lord ... This is how you freak out everyone, I would release a proper asyncclick-8.1.8.1 python package.
gbin commented on 2025-01-07 18:22 (UTC)
gbin commented on 2025-01-07 18:20 (UTC) (edited on 2025-01-07 18:20 (UTC) by gbin)
wait still not out of the woods:
gbin commented on 2025-01-07 18:18 (UTC)
@wuestengecko thanks for the quick reaction, I was totally confused :).
wuestengecko commented on 2025-01-07 16:19 (UTC)
Whoops. Looks like something has gone wrong with the release, it actually packaged click and not asyncclick. 8.1.8-2 is fixed.
vaygr commented on 2025-01-07 15:57 (UTC)
Latest update conflicts with
python-click
.