Package Details: python-p4python 2018.2.1743033-2

Git Clone URL: https://aur.archlinux.org/python-p4python.git (read-only, click to copy)
Package Base: python-p4python
Description: Interface to Perforce API for Python 3
Upstream URL: https://www.perforce.com/perforce/doc.current/manuals/p4script/03_python.html
Licenses: custom
Submitter: WhittlesJr
Maintainer: None
Last Packager: adytzu2007
Votes: 0
Popularity: 0.000000
First Submitted: 2017-05-05 18:59 (UTC)
Last Updated: 2021-12-15 11:51 (UTC)

Latest Comments

1 2 Next › Last »

adytzu2007 commented on 2021-12-15 11:52 (UTC)

Update the p4api version, should work now. Thanks.

micwoj92 commented on 2021-12-15 08:50 (UTC) (edited on 2021-12-15 08:50 (UTC) by micwoj92) 

==> Validating source files with sha256sums...
    python-p4python-2018.2.1743033.tar.gz ... Passed
    p4api.tgz ... FAILED

adytzu2007 commented on 2019-11-05 22:54 (UTC)

Updated, thanks.

lostgoat commented on 2019-11-01 21:44 (UTC)

The p4api tarball has again updated to 2018.1.1852931

adytzu2007 commented on 2019-09-13 19:27 (UTC)

Updated, thanks for the heads up.

lostgoat commented on 2019-09-13 18:56 (UTC)

Hi,

The current package fails to build because the p4api tarball has been updated with the following:

-p4apiver=2018.1.1660568
+p4apiver=2018.1.1738923
...
-            'e1c9e08b4db0b333510ae814e316e506c48f7eb80b654367bed003096ea8a5ec')
+            'caa06e47fde11c5918524a1248fa51c7a08e597b01fb0d62a8cf85d95b359bb5')

WhittlesJr commented on 2017-08-17 15:40 (UTC)

There are a number of suggestions in the forum thread now.

WhittlesJr commented on 2017-08-17 13:53 (UTC)

Well now I'm not so sure. Moving the conversation here: https://bbs.archlinux.org/viewtopic.php?pid=1731077#p1731077

WhittlesJr commented on 2017-08-17 13:38 (UTC)

I'm kinda with you on the counter-intuitiveness there. Others have complained about similar things, like taking twice as long to build large packages on slow systems (although surprisingly I have not seen anyone complain about python3/2). With python-setuputils and python2-setuputils as makedepends for this and pyalsaaudio, AUR helpers will install python2 if it's not there already, and at least this way it's not a surprise if you're manually building. But because I'm sympathetic, I'd say go ahead and submit a spinoff package like python2-p4python-python2only or something better-named. I think your use case is perhaps not typical but is still valid.

f0ff886f commented on 2017-08-17 13:12 (UTC)

So I'm not an expert on the normal way to do it in this case. python-pyalsaaudio would also fail building on my install, where I don't have python2, and choosing to always build python2 packages seems counter-intuitive when there is no interdependancy between 2 and 3. Regarding the flags, openssl-1.0 should be a makedepends because the .so will link to libssl.so.1.1.0 if it doesn't find the 1.0 lib at link time. Lastly, I reported this upstream so hopefully the ssl issue will go away one day: https://forums.perforce.com/index.php?/topic/5457-will-p4python-be-updated-to-support-openssl-11x/

1 2 Next › Last »