Package Details: python2 2.7.18-11

Git Clone URL: https://aur.archlinux.org/python2.git (read-only, click to copy)
Package Base: python2
Description: A high-level scripting language
Upstream URL: https://www.python.org/
Licenses: PSF-2.0
Conflicts: python
Submitter: jelly
Maintainer: micwoj92
Last Packager: micwoj92
Votes: 76
Popularity: 2.01
First Submitted: 2022-09-23 10:01 (UTC)
Last Updated: 2024-06-17 22:01 (UTC)

Pinned Comments

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 .. 19 Next › Last »

TheJackofClubs commented on 2024-03-04 03:38 (UTC)

ok, so the really long build time is unnecessary? thanks

micwoj92 commented on 2024-03-03 18:04 (UTC)

AUR allows precompiled packages.

TheJackofClubs commented on 2024-03-03 17:57 (UTC)

it took 38m 26s to update just python2 because of those tests. its packages like this that makes me wish aur allowed precompiled packages.

kIERO commented on 2024-03-02 20:01 (UTC)

Are these mflags permanent, as in when updating the package they are applied? or not

yay -S python2 --mflags "--nocheck"

If they are not, is there any config file to assign mflags to a package directly?

begemot69 commented on 2024-03-02 16:47 (UTC)

@Bluebomber182 Thank you !!! вимкнув тести і зібрався пакунок!!!

maid commented on 2024-02-25 12:01 (UTC)

0:08:33 load avg: 1.06 [340/400] test_threadedtempfile -- test_threaded_import failed 0:08:33 load avg: 1.06 [341/400] test_threading -- test_threadedtempfile failed

Build freeze and stay 2 hours on last string with a significant load on the CPU.

gfwgfw commented on 2024-02-24 02:40 (UTC)

@Bluebomber182 It still running tests under Manjaro.

"I skip the testing by typing this yay command yay -S python2 --mflags "--nocheck"

My yay version info: yay v12.2.0 - libalpm v13.0.2

cidelcampeador commented on 2024-02-23 16:10 (UTC)

I am having an error today:

 :: PGP keys need importing:
 -> C01E1CAD5EA2C4F0B8E3571504C367C218ADD4FF, required by: python2
:: Import? [Y/n]
:: Importing keys with gpg...
gpg: Note: signatures using the SHA1 algorithm are rejected
gpg: key 0x04C367C218ADD4FF: 5 bad signatures
gpg: key 0x04C367C218ADD4FF: no valid user IDs
gpg: this may be caused by a missing self-signature
gpg: Total number processed: 1
gpg:           w/o user IDs: 1
 -> problem importing keys

same happens when importing to the keyring manually: 

~►gpg --recv-keys 04C367C218ADD4FF                                                
gpg: Note: signatures using the SHA1 algorithm are rejected
gpg: key 0x04C367C218ADD4FF: 5 bad signatures
gpg: key 0x04C367C218ADD4FF: no valid user IDs
gpg: this may be caused by a missing self-signature
gpg: Total number processed: 1
gpg:           w/o user IDs: 1

the key is however imported without problems to pacman's keyring:

~►sudo pacman-key --recv-keys C01E1CAD5EA2C4F0B8E3571504C367C218ADD4FF            
gpg: key 04C367C218ADD4FF: "Benjamin Peterson <bp@benjamin.pe>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1

any ideas?

Nyyr commented on 2024-02-03 13:16 (UTC)

@Bluebomber182 Thank you, on systems with ZFS and normalized to UTF-8 only there are 4 checks that fail (don't remember exactly, mpath, pep277 or something). I used to edit the sources to skip these tests but this simple workaround was a time saver :-)

Bluebomber182 commented on 2024-02-03 06:01 (UTC)

I skip the testing by typing this yay command

yay -S python2 --mflags "--nocheck"

« First ‹ Previous 1 2 3 4 5 6 7 8 .. 19 Next › Last »