Arch Linux User Repository

It no longer builds for me using the latest release :(

==> Validating source files with sha256sums...

p4v.desktop ... Passed

p4admin.desktop ... Passed

p4merge.desktop ... Passed

LICENSE ... Passed

20200606-p4v-2020.1.1946989.tgz ... FAILED

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

Failed to build p4v

I've noticed that if you use p4v to launch anything qt, p4v's qt conflicts with with the system one with a log filled with things like

kde-open5: /usr/share/p4v/lib/libQt5Core.so.5: version `Qt_5.14' not found (required by kde-open5)

That includes launching web browser for swarm reviews, using any QT text editors, etc.

Trying to set export LD_LIBRARY_PATH=/usr/lib (which gets appended to p4v's own export LD_LIBRARY_PATH in the p4v file) doesn't help at all because the linker still sees the first libraries and gives up.

p4v is probably built against Ubuntu or Debian, so it works fine there because the libraries match (besides not being able to find its own plugins after startup, but that's a different problem).

like aur/p4 I made some changes so pkgver is updated automatically to match what you download mainly for my own convenience, however unlike that package this one does not ship with an asc so the checksum verif. will still fail until I manually update the package... :(

@aurius sorry, I just fixed it. guess my previous comment to @geirThomassen is defunct lol

Just tried to install with pikaur and got:

==> Validating source files with sha256sums...
p4v.desktop ... Passed
p4admin.desktop ... Passed
p4merge.desktop ... Passed
LICENSE ... Passed
p4v-2019.2.1856742.tgz ... Passed
==> Extracting sources...
-> Extracting p4v-2019.2.1856742.tgz with bsdtar
==> Entering fakeroot environment...
==> Starting package()...
/home/user/.cache/pikaur/build/p4v/PKGBUILD: line 29: cd: /home/user/.cache/pikaur/build/p4v/src/p4v-2019.2.1856742/: No such file or directory
==> ERROR: A failure occurred in package().
Aborting...

Command 'makepkg --force' failed to execute.

-----

When listed the "/home/user/.cache/pikaur/build/p4v/src" got:

drwxr-xr-x 3 user user 4096 Nov 20 22:34 .
drwxr-xr-x 4 user user 4096 Nov 20 22:34 ..
lrwxrwxrwx 1 user user 44 Nov 20 22:34 LICENSE -> /home/user/.cache/pikaur/build/p4v/LICENSE
lrwxrwxrwx 1 user user 52 Nov 20 22:34 p4admin.desktop -> /home/user/.cache/pikaur/build/p4v/p4admin.desktop
lrwxrwxrwx 1 user user 52 Nov 20 22:34 p4merge.desktop -> /home/user/.cache/pikaur/build/p4v/p4merge.desktop
lrwxrwxrwx 1 user user 59 Nov 20 22:34 p4v-2019.2.1856742.tgz -> /home/user/.cache/pikaur/build/p4v/p4v-2019.2.1856742.tgz
drwxr-xr-x 4 user user 4096 Nov 13 22:11 p4v-2019.2.1883366
lrwxrwxrwx 1 user user 48 Nov 20 22:34 p4v.desktop -> /home/user/.cache/pikaur/build/p4v/p4v.desktop

@GeirThomassen updating, but where did your 2019.2.1883366 come from? even on the new binary checking the version gets me Rev. Helix P4V/LINUX26X86_64/2019.2/1856742, so I'm just going to bump pkgrel.

edit: nevermind I figured it out lol... ignore this comment

@dront78 yeah I get that it still works, but I'd rather just not mess with it on a package basis, sorry. I'll just distribute what they do.

If you want to keep this package from ever installing that file though, you can symlink it to /dev/null with sudo ln -s /dev/null /usr/share/p4v/lib/P4VResources/skins/Default.qss, and then in your pacman.conf [options] section you can add NoUpgrade = usr/share/p4v/lib/P4VResources/skins/Default.qss and from now on whenever the package is updated it will keep the file as being "empty" and p4v will default to your system theme :)

@jshap the hack is still working.
: > /usr/share/p4v/lib/P4VResources/skins/Default.qss
p4v will use the desktop skin after restart in KDE.
For the non-qt I think you can create a symlink to your skin. PS. dark theme has better color theme in diff util. shame, it is still not possible to setup like in any modern app.
Finally, I ended up with switching to the DarkTheme.css which has a zero file size :)

@dront78 I messed around with doing that for the default skin file, but on non-qt based platforms it ends up looking very bad.

Fortunately 19.2 now has a native dark theme (edit->preferences->display->color scheme) though so maybe try that out? Although sadly it doesn't look like we can register custom themes either grumble grumble