Package Details: p4d 2020.2-1

Git Clone URL: (read-only, click to copy)
Package Base: p4d
Description: Minimal Perforce Server
Upstream URL:
Keywords: core helix p4 perforce
Licenses: custom:p4d
Submitter: andrewboktor
Maintainer: Nora
Last Packager: Nora
Votes: 4
Popularity: 0.000000
First Submitted: 2014-11-07 22:27 (UTC)
Last Updated: 2021-01-31 23:59 (UTC)

Latest Comments

1 2 Next › Last »

veridiam commented on 2020-06-28 22:35 (UTC) (edited on 2020-06-28 22:35 (UTC) by veridiam)

seems to encounter SIGSEGV errors whenever a user tries to connect

Perforce server error: Process 585726 exited on a signal 11!

ultdev commented on 2016-09-15 15:11 (UTC)

New version of p4d is available: Rev. P4D/LINUX26X86_64/2016.1/1437038 (2016/09/08). Here's the new sha256sum: ee6608741321fd3b88c9123109a444c0e696d80375313526dae4f3cfc1e50833

Naatan commented on 2016-03-10 17:10 (UTC)

sha256sum: f7d4c2cacd79658441d56ced9b210c7fc975af7265b28e373e280ad094fb3081

andrewboktor commented on 2015-09-26 03:54 (UTC)

Can you please abandon the package so that I can resume maintaining it?

andrewboktor commented on 2015-04-07 18:24 (UTC)

Yes, thank you for catching that. Package updated.

ultdev commented on 2015-04-07 17:09 (UTC)

It looks like the checksum change is due to a new release of p4d on 4/1/15; here's the output from p4d -V: Rev. P4D/LINUX26X86_64/2014.2/1033284 (2015/04/01).

andrewboktor commented on 2015-04-07 17:09 (UTC)

sha1sum fixed

ultdev commented on 2015-04-07 17:05 (UTC)

Thanks! Also, the sha1sum for p4d needs to be updated; it should be "92f2f2847b32c0669c1a187dbfe4fc48de3c8b90"

andrewboktor commented on 2015-04-04 21:43 (UTC)

I just updated the package to solve the "run-as-root" issue. Now all perforce files are owned by perforce:p4admin which are created during install. You'll have to change ownership of your files manually.

ultdev commented on 2015-03-10 19:39 (UTC)

The perforce server should not be run as root (see "UNIX: Run p4d as a nonprivileged user": Can you add support to the PKGBUILD for creating a new perforce user/group (if it doesn't already exist) and running the server as this user instead?