Arch Linux User Repository

The actual version of the source it's derived from is indeed 9.10, but here it's a derivative from derivative 9.10-1.plucky version (though official one at that).

@alllexx88 The format of 9.10-1 in 9.10-1.plucky is [epoch:]upstream_version[-debian_revision], which is the special format that ubuntu inherit from debian. We don't need the debian_revision part.

Maybe you can generate both the server, and the desktop package from your PKGBUILD?

Of course, this is what I expect.

For now, I've added you here as a co-maintainer, since you're maintaining the server already anyway :)

Thanks for the trust. I'm glad to collaborate and will handle the next steps.

Oh my markdown format :(

@lzx3in Sorry for my late response: I forgot to turn on the notifications. Currently this package uses this deb file: https://ftp.postgresql.org/pub/pgadmin/pgadmin4/apt/plucky/dists/pgadmin4/main/binary-amd64/pgadmin4-desktop_9.10-1.plucky_amd64.deb

The actual version of the source it's derived from is indeed 9.10, but here it's a derivative from derivative 9.10-1.plucky version (though official one at that). They changed naming convention from pgadmin4-desktop_9.9_amd64.deb to pgadmin4-server_9.10-1.plucky_amd64.deb. I see you're building pgadmin4-server from source. Maybe you can generate both the server, and the desktop package from your PKGBUILD? Then we can take this one down. For now, I've added you here as a co-maintainer, since you're maintaining the server already anyway :)

I really hope to keep the entire pgAdmin4 package series consistent. If you're too busy, I'm willing to help.

@alllexx88 The pkgver should be "9.10", rather than "9.10.1" or "9.10-1". This issue has affected the package pgadmin4-bin. Its​ script can't find the package pgadmin-desktop that​ has pkgver "9.10".

I don't know if this helps, but proton-mail-bin-debug is suffering from the same issue that @domnek just described:

$ yay -S proton-mail-bin

... snip ...

Package (2)            Old Version  New Version  Net Change

proton-mail-bin        1.9.0-1      1.9.1-2       10.94 MiB
proton-mail-bin-debug               1.9.1-2        2.74 MiB

... snip ...

error: failed to commit transaction (conflicting files)
proton-mail-bin-debug: /usr/lib/debug/.build-id/0f/d60263ae423cc17f40668f900829657636fd90 exists in filesystem (owned by pgadmin4-desktop-debug)
proton-mail-bin-debug: /usr/lib/debug/.build-id/0f/d60263ae423cc17f40668f900829657636fd90.debug exists in filesystem (owned by pgadmin4-desktop-debug)
... and some more ...

Errors occurred, no packages were upgraded.
 -> error installing: [/home/vetkat/.cache/yay/proton-mail-bin/proton-mail-bin-1.9.1-2-x86_64.pkg.tar.zst /home/vetkat/.cache/yay/proton-mail-bin/proton-mail-bin-debug-1.9.1-2-x86_64.pkg.tar.zst] - exit status 1

I get this error during installation:

error: failed to commit transaction (conflicting files)
pgadmin4-desktop-debug: /usr/lib/debug/.build-id/02/844564051eeda47ad13b0dab67cd6ee00a65a6 exists in filesystem (owned by teams-for-linux-debug)
pgadmin4-desktop-debug: /usr/lib/debug/.build-id/02/844564051eeda47ad13b0dab67cd6ee00a65a6.debug exists in filesystem (owned by teams-for-linux-debug)
pgadmin4-desktop-debug: /usr/lib/debug/.build-id/61/c57f8c481a2444341d59f049e793c4d2d65ff3 exists in filesystem (owned by teams-for-linux-debug)
pgadmin4-desktop-debug: /usr/lib/debug/.build-id/61/c57f8c481a2444341d59f049e793c4d2d65ff3.debug exists in filesystem (owned by teams-for-linux-debug)
pgadmin4-desktop-debug: /usr/lib/debug/.build-id/7f/018d2b5eec4a20a54a29df4bfbfbfd9d82f3dd exists in filesystem (owned by teams-for-linux-debug)
pgadmin4-desktop-debug: /usr/lib/debug/.build-id/7f/018d2b5eec4a20a54a29df4bfbfbfd9d82f3dd.debug exists in filesystem (owned by teams-for-linux-debug)
pgadmin4-desktop-debug: /usr/lib/debug/.build-id/c9/57ecc373e560d9bb51a63cf32078f702187a63 exists in filesystem (owned by teams-for-linux-debug)
pgadmin4-desktop-debug: /usr/lib/debug/.build-id/c9/57ecc373e560d9bb51a63cf32078f702187a63.debug exists in filesystem (owned by teams-for-linux-debug)
pgadmin4-desktop-debug: /usr/lib/debug/.build-id/dc/bf1da896bdd82b64981a0786db0e1c512ea3b3 exists in filesystem (owned by teams-for-linux-debug)
pgadmin4-desktop-debug: /usr/lib/debug/.build-id/dc/bf1da896bdd82b64981a0786db0e1c512ea3b3.debug exists in filesystem (owned by teams-for-linux-debug)
pgadmin4-desktop-debug: /usr/lib/debug/.build-id/e0/24f4dbec53fb077abd6bd68d93f05251481dc9 exists in filesystem (owned by teams-for-linux-debug)
pgadmin4-desktop-debug: /usr/lib/debug/.build-id/e0/24f4dbec53fb077abd6bd68d93f05251481dc9.debug exists in filesystem (owned by teams-for-linux-debug)
Errors occurred, no packages were upgraded.

Suggest renaming this package pgadmin4-desktop-bin especially since pgadmin4-server is now building from source.

92% [0] sealing asset processing TerserPlugin ==> ERROR: build() failed. Aborted... -> build error: pgadmin4-server exited with status 4

==> Building package pgadmin4-desktop 9.8-1 (Wed Oct 22 2025 17:57:17) ==> Checking runtime dependencies... ==> Missing dependencies: -> pgadmin4-server ==> Checking build-time dependencies... ==> ERROR: Failed to resolve all dependencies. -> build error: pgadmin4-desktop exited with status 8 -> The following packages could not be installed. Manual intervention required: pgadmin4-desktop - exit status 8 pgadmin4-server - exit status 4

@lzx3in thanks for the heads-up, I fixed the checksum. The python issue you were having is because of the pgadmin4-server package, it has been recently upgraded, and should be fine now.

P.S. ah, it's been you who upgraded it :)

I've been working with the source build version provided by @maroider for a while, and it's quite good.

I'm glad to see that a new version has been released in the AUR, but I've encountered a previous issue again:

Error: spawn /usr/pgadmin4/venv/bin/python3 ENOENT

After checking, I found that /usr/pgadmin4/venv/bin/python3 is a soft link pointing to /usr/bin/python3.12, but my Python3 has been updated to version 3.13.

Clearly, under the current packaging strategy that reuses .deb files, we can never completely resolve this issue. It would be better to switch to using source builds from now on.