Package Details: python310 3.10.14-2

Git Clone URL: https://aur.archlinux.org/python310.git (read-only, click to copy)
Package Base: python310
Description: Next generation of the python high-level scripting language, version 3.10
Upstream URL: https://www.python.org/
Licenses: custom
Provides: python
Submitter: soh
Maintainer: soh
Last Packager: soh
Votes: 20
Popularity: 0.58
First Submitted: 2023-05-04 00:47 (UTC)
Last Updated: 2024-04-28 13:19 (UTC)

Dependencies (20)

Required by (13073)

Sources (1)

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

MarsSeed commented on 2023-10-09 12:13 (UTC) (edited on 2023-10-09 12:16 (UTC) by MarsSeed)

Please kindly rename this package to python-3.10 to conform to Arch package naming guidelines (to the requirement that calls for attaching only the major version number directly to the package name, which in this case is 3 - three -, not 310 - three hundred and ten).

Also please remove the provides field. It is useless, and this package is not a drop-in replacement of repo's python package. Also, AUR helpers don't support versioned provides lookup.

Some good examples from repo:

Thank you in advance for your cooperation, and for maintaining this package.

lachesis commented on 2023-09-14 19:21 (UTC) (edited on 2023-09-14 19:21 (UTC) by lachesis)

I still receive the gpg error warning, even using yay. It tries to import 3 other keys:

:: PGP keys need importing:
 -> 0D96DF4D4110E5C43FBFB17F2D347EA6AA65421D, required by: python310
 -> E3FF2839C048B25C084DEBE9B26995E310250568, required by: python310
 -> A035C8C19219BA821ECEA86B64E628F8D684696D, required by: python310

Manually importing the key as requested works just fine, but why doesn't yay do that for me?

soh commented on 2023-06-18 14:45 (UTC)

@Jonny-Doe This seems to a benign warning. Also check here: https://bbs.archlinux.org/viewtopic.php?id=241153

Jonny-Doe commented on 2023-06-11 12:07 (UTC)

While building package, it throws a warning like this:

WARNING: Package contains reference to $srcdir

kaputtnik commented on 2023-05-13 08:33 (UTC)

@soh

Thanks that solved it.

soh commented on 2023-05-13 08:17 (UTC) (edited on 2023-05-13 08:18 (UTC) by soh)

@ kaputtnik If you run into this when using makepkg -si:

==> Verifying source file signatures with gpg...
    Python-3.10.11.tar.xz ... FAILED (unknown public key FFE87404168BD847)
==> ERROR: One or more PGP signatures could not be verified!

Simply running this will solve your problem

$ gpg --recv-key FFE87404168BD847
gpg: /home/user/.gnupg/trustdb.gpg: trustdb created
gpg: key 64E628F8D684696D: public key "Pablo Galindo Salgado <pablogsal@gmail.com>" imported
gpg: Total number processed: 1
gpg:               imported: 1

Use an AUR helper like yay, paru will also help.

diestl commented on 2023-05-11 15:13 (UTC)

@kaputtnik, you need to fetch the signing key used to sign the python 3.10 release. According to the download page from python.org, this is a key belonging to Pablo Galindo Salgado (https://www.python.org/downloads/).

You can fetch and import that key into your keyring with curl <url> | gpg --import -. The url you'll find on that download page.

kaputtnik commented on 2023-05-07 11:22 (UTC)

I get this gpg related error:

$:> LC_ALL=C makepkg ==> Making package: python310 3.10.11-1 (Sun May 7 13:14:51 2023) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Found Python-3.10.11.tar.xz -> Found Python-3.10.11.tar.xz.asc ==> Validating source files with sha512sums... Python-3.10.11.tar.xz ... Passed Python-3.10.11.tar.xz.asc ... Skipped ==> Verifying source file signatures with gpg... Python-3.10.11.tar.xz ... FAILED (unknown public key FFE87404168BD847) ==> ERROR: One or more PGP signatures could not be verified!

esh commented on 2023-05-06 21:38 (UTC)

Worked great for me, I simply installed the package using Paru. Thanks for making it available so quickly after 3.11 went into [core]. :)

soh commented on 2023-05-05 03:31 (UTC) (edited on 2023-05-05 03:34 (UTC) by soh)

@carsme

Could you figure out the real cause of unable to retrieving GPG key? At least in two of my machines I managed to successfully makepkg and gpg --recv-keys A035C8C19219BA821ECEA86B64E628F8D684696D. Maybe configuring auto-key-retrieve could help.

« First ‹ Previous 1 2 3 4 Next › Last »