Package Details: p4 2024.2.2675662-1

Git Clone URL: https://aur.archlinux.org/p4.git (read-only, click to copy)
Package Base: p4
Description: Perforce's Helix command-line client
Upstream URL: https://www.perforce.com
Keywords: p4 perforce
Licenses: custom:p4
Submitter: queueRAM
Maintainer: meepzh
Last Packager: meepzh
Votes: 30
Popularity: 0.000000
First Submitted: 2009-09-10 01:45 (UTC)
Last Updated: 2024-11-28 05:43 (UTC)

Dependencies (1)

Required by (1)

Sources (3)

Latest Comments

1 2 3 4 5 6 Next › Last »

almir commented on 2021-11-18 15:13 (UTC) (edited on 2021-11-18 15:45 (UTC) by almir)

I get this error when trying to install:

:: PGP keys need importing: -> 7123CB760FF18869, required by: p4 -> E58131C0AEA7B082C6DC4C937123CB760FF18869, required by: p4 :: Importing keys with gpg... gpg: keyserver receive failed: Server indicated a failure -> problem importing keys

EDIT: Solved it with: curl https://package.perforce.com/perforce.pubkey | gpg --import

ByReaL commented on 2020-10-22 16:44 (UTC)

:: PGP keys need importing: -> 7123CB760FF18869, required by: p4 -> E58131C0AEA7B082C6DC4C937123CB760FF18869, required by: p4 :: Importing keys with gpg... gpg: keyserver receive failed: General error problem importing keys

jshap commented on 2020-01-09 21:35 (UTC)

made some changes so pkgver is updated automatically to match what you download, will still be bumping every once in a while but unfortunately there's no good way to tell from their downloads that there was a patch update at all.

fwiw the build never failed for me like the flag message indicated because it's relying on the asc, but general reminder that you need to import those keys :)

jshap commented on 2019-10-16 22:46 (UTC)

Hi. I took over this package.

some small changes without a pkgrel bump b/c all I did was fix the issue where you'd have to delete the p4 binary to repackage the program.

Thank you to all the previous maintainers for your work :)

<deleted-account> commented on 2019-09-01 20:43 (UTC)

@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 (UTC) (edited on 2019-08-13 12:47 (UTC) by sankasan) 

==> 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!

<deleted-account> commented on 2019-08-05 21:13 (UTC)

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

jshap commented on 2019-08-05 20:41 (UTC)

the i686 sha256sum should be d9677042a2e50e90c576c369fe58344ba2da93eb699c97d6417dc4e497a95beb.

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

jshap commented on 2019-08-02 17:48 (UTC) (edited on 2019-08-02 17:57 (UTC) by jshap)

please update with this patch https://gist.github.com/jshap70/b273d9b96dfa6f73dda9d8e7e5c3a805

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

<deleted-account> commented on 2019-04-02 17:37 (UTC)

ByReal, I adopted this package yesterday.

1 2 3 4 5 6 Next › Last »