Package Details: p4 2019.1.1751184-2

Git Clone URL: (read-only)
Package Base: p4
Description: Perforce command line client
Upstream URL:
Keywords: p4 perforce
Licenses: custom:p4
Submitter: queueRAM
Maintainer: aaronm-cloudtek
Last Packager: aaronm-cloudtek
Votes: 29
Popularity: 0.076986
First Submitted: 2009-09-10 01:45
Last Updated: 2019-08-05 21:11

Latest Comments

1 2 3 4 5 Next › Last »

aaronm-cloudtek commented on 2019-09-01 20:43

@sankasan The package builds and validates the sources just fine for me. The sha256sum_x86_64 is correct. Do you have an old copy of the p4 binary in the directory you are building from?

sankasan commented on 2019-08-13 12:46

==> Making package: p4 2019.1.1751184-2 (Tue Aug 13 14:45:14 2019)
==> Retrieving sources...
  -> Found LICENSE
  -> Found p4
==> Validating source files with sha256sums...
    LICENSE ... Passed
==> Validating source_x86_64 files with sha256sums...
    p4 ... FAILED
==> ERROR: One or more files did not pass the validity check!

aaronm-cloudtek commented on 2019-08-05 21:13

Oops, thanks. Fixed. makepkg --geninteg didn't do what I expected there.

jshap commented on 2019-08-05 20:41

the i686 sha256sum should be d9677042a2e50e90c576c369fe58344ba2da93eb699c97d6417dc4e497a95beb.

alternatively use the .asc because it's much safer.

jshap commented on 2019-08-02 17:48

please update with this patch

... alternatively just make me maintainer considering I only just realized I made the last patch too haha

aaronm-cloudtek commented on 2019-04-02 17:37

ByReal, I adopted this package yesterday.

ByReaL commented on 2019-04-02 16:40

i can adopt it, how would you like to go about it? usually it's easy if package is orphan but this one is still flagged as active.

peder2tm commented on 2019-04-01 18:30

Feel free to adopt the package. I stopped using perforce so I am not really interested in maintaining the package.

ByReaL commented on 2019-04-01 18:16

ERROR: One or more files did not pass the validity check!

jshap commented on 2019-01-14 21:24

hey @peder2tm, I think you applied the patch to bump the version to 2018.2.1660568 but forgot to update the .SRCINFO ( so an update was never published.