Package Details: p4 2024.2.2726408-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: 2025-04-04 11:17 (UTC)

Dependencies (1)

Required by (1)

Sources (3)

Latest Comments

1 2 3 4 5 6 Next › Last »

Chats commented on 2025-04-04 21:57 (UTC)

Thanks meepzh, that's fixed it! :)

meepzh commented on 2025-04-04 11:21 (UTC)

Sorry for the issue, please try again Chats. I've updated the PKGBUILD.

When Perforce updated their release notes in February, I was still getting the older version of p4. Maybe there was an issue with my build back then, but I'll have another look next time. It should be building correctly now.

Chats commented on 2025-04-04 10:59 (UTC) (edited on 2025-04-04 11:00 (UTC) by Chats)

Hi there, Getting this error when trying running makepkg:

==> Making package: p4 2024.2.2697822-1 (Fri 04 Apr 2025 21:59:30)
==> Retrieving sources...
  -> Found LICENSE
  -> Found 24.2-20250404-p4
  -> Found 24.2-20250404-p4.asc
==> Validating source files with sha256sums...
    LICENSE ... Passed
    24.2-20250404-p4 ... FAILED
    24.2-20250404-p4.asc ... Skipped
==> ERROR: One or more files did not pass the validity check!

ringuren commented on 2025-01-10 20:35 (UTC) (edited on 2025-01-10 20:39 (UTC) by ringuren)

Patch for the latest p4 binary checksum: 

diff --git a/PKGBUILD b/PKGBUILD
index d1a4f41..1865fc7 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -3,7 +3,7 @@

 pkgname=p4
 _version=2024.2
-pkgver=2024.2.2675662
+pkgver=2024.2.2697822
 pkgrel=1

 pkgdesc="Perforce's Helix command-line client"
@@ -21,7 +21,7 @@ source=(LICENSE


 sha256sums=('c4ed3aef62b1bbf2d16ce4cceb65dc49ab9635b38e2fed0a595fe259283a9f32'
-            'ee9cd514717dc7ef7d3f2fffb91d67b625291e740dcd72ba929a4c93ed0944c7'
+            'd9163d7b7c863978a4874356b9f985e5a785f1ca1e520ce8dc86e3c16189d966'
             'SKIP')

 # Perforce Software (Package Signing) <support+packaging@perforce.com>

Command to apply all in one step:

echo -e 'diff --git a/PKGBUILD b/PKGBUILD
index d1a4f41..1865fc7 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -3,7 +3,7 @@

 pkgname=p4
 _version=2024.2
-pkgver=2024.2.2675662
+pkgver=2024.2.2697822
 pkgrel=1

 pkgdesc="Perforce\'s Helix command-line client"
@@ -21,7 +21,7 @@ source=(LICENSE


 sha256sums=(\'c4ed3aef62b1bbf2d16ce4cceb65dc49ab9635b38e2fed0a595fe259283a9f32\'
-            \'ee9cd514717dc7ef7d3f2fffb91d67b625291e740dcd72ba929a4c93ed0944c7\'
+            \'d9163d7b7c863978a4874356b9f985e5a785f1ca1e520ce8dc86e3c16189d966\'
             \'SKIP\')

 # Perforce Software (Package Signing) <support+packaging@perforce.com>' | git apply

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!

1 2 3 4 5 6 Next › Last »