Package Details: python-blake3 1.0.5-1

Git Clone URL: https://aur.archlinux.org/python-blake3.git (read-only, click to copy)
Package Base: python-blake3
Description: Python bindings for the BLAKE3 cryptographic hash function
Upstream URL: https://github.com/oconnor663/blake3-py
Keywords: blake3 hash python
Licenses: Apache-2.0, CC0-1.0
Submitter: gmes78
Maintainer: gmes78 (oconnor663)
Last Packager: gmes78
Votes: 4
Popularity: 0.98
First Submitted: 2020-02-29 18:31 (UTC)
Last Updated: 2025-07-11 03:57 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

WwPvWLcBrUubxgJQ commented on 2025-01-11 17:00 (UTC)

@oconnor663 I have waited a week for the validity check error to go away, but no luck. I have cleared the cache, and nothing seems to be helping. Am I doing something wrong? I understand it was published twice and that is likely causing my mirror to be outdated. Do you think it could be fixed by republishing it as 1.0.1-2 to correct all of the mirrors' caches.

gmes78 commented on 2025-01-11 02:08 (UTC) (edited on 2025-01-11 02:12 (UTC) by gmes78)

@micwoj92 @oconnor663 I looked into converting this package to use python-build/python-install a couple of times in the past, but I ran into some issues (I don't exactly recall what they were, but it may have had to do with an incompatibility between the versions of the Maturin build system in the repos and the one required by the pyproject.toml, though that might have changed since), which is why it hasn't been done. I can take another look at it.

@oconnor663 python-build is a tool for building PEP 517 projects. It allows for a more straightforward packaging workflow, instead of having to wrangle pip into doing what we want. See here, here and here.

oconnor663 commented on 2025-01-10 22:50 (UTC)

@micwoj92 could you say more (much, much more) about your recommendation? I'm hearing about python-build and python-installer for the first time, so I don't have any context. Is this a personal preference thing, or an Arch packaging best practices thing? Does python-build support packages written entirely in Rust? Etc.

micwoj92 commented on 2025-01-10 22:26 (UTC)

Please switch to standard build using python-build and python-installer.

oconnor663 commented on 2025-01-04 16:08 (UTC)

@Nestor_013 thanks for reporting, I've corrected the hash. We released v1.0.1 twice upstream, which is what caused this hiccup. We probably shouldn't do that again :)

Nestor_013 commented on 2025-01-04 15:09 (UTC) (edited on 2025-01-04 15:11 (UTC) by Nestor_013)

Hi, I got a

==> Validating source files with sha512sums...
    blake3-py-1.0.1.tar.gz ... FAILED
==> ERROR: One or more files did not pass the validity check!

Using makepkg -g the shasum is:

sha512sums=('54d2b0b3aef48dfde6f15d3cfb7a4ebd4549ca8bedbb8b4a95fc882e4a08ed1beb1ad53f62042f0de3792fa1a9177f287e6c8f6c65aa4e7414210549bc67ec77')

oconnor663 commented on 2023-06-07 06:11 (UTC)

Thanks! Pushed.

gmes78 commented on 2023-06-07 04:01 (UTC)

@oconnor663 Sure thing.

(I didn't see your previous message, sorry about that. You can go ahead and make that change.)

oconnor663 commented on 2023-06-07 03:57 (UTC)

I'd be happy to be a co-maintainer of this package if you like. I'd like to bump the pkgrel to celebrate Python 3.11, and I can also add the virtualenv check below.

oconnor663 commented on 2022-12-28 17:03 (UTC)

@kseistrup interesting! I picked the Python AUR package with the most votes (python-pynput) and tried installing that in a venv, and that runs into a vaguely similar issue. In that case the package fails to build, though, which is probably better than passing the build and installing nonsense. Maybe we could insert an extra check something like this?

if [[ -n "$VIRTUAL_ENV" ]]; then
    echo 'ERROR: $VIRTUAL_ENV is set, which means the build is running in a virtual Python environment.'
    echo 'ERROR: Rerun the build in a fresh terminal, using the default/system Python environment.'
    exit 1
fi