Package Details: trenchbroom-bin 2024.1-2

Git Clone URL: (read-only, click to copy)
Package Base: trenchbroom-bin
Description: TrenchBroom is a free (GPLv3+), cross platform level editor for Quake-engine based games. This is the Ubuntu Release version of TrenchBroom 2024.1 repackaged for Arch.
Upstream URL:
Keywords: editor game graphics level
Licenses: GPL3
Conflicts: trenchbroom, trenchbroom-git
Provides: trenchbroom
Submitter: hilton
Maintainer: Retro_Gamer
Last Packager: Retro_Gamer
Votes: 10
Popularity: 1.06
First Submitted: 2022-04-21 01:20 (UTC)
Last Updated: 2024-03-08 22:09 (UTC)

Latest Comments

Retro_Gamer commented on 2024-03-08 22:28 (UTC) (edited on 2024-03-09 01:38 (UTC) by Retro_Gamer)

I am unsure what your issue could be unless you are on a restricted user account. Guessing it's an odd pamac issue. I just installed into Manjaro as normal, Pamac will ask for your password, enter it, and it should finish up the installation.

99cents commented on 2024-03-05 13:36 (UTC)

installing v2023.1 with pamac on Manjaro (perhaps a pamac issue?)...

x ./usr/share/mime/packages/trenchbroom.xml
sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper
sudo: a password is required
==> ERROR: A failure occurred in prepare().

Retro_Gamer commented on 2024-03-02 00:13 (UTC) (edited on 2024-03-02 04:03 (UTC) by Retro_Gamer)

Thank you! It is great you are jumping in and learning, as am I. As the TrenchBroom community manager I just wanted to have control or co-control of the 2 pkgbuilds on the AUR. Purely to make sure they are kept up to date as changes in Arch or TrenchBroom happen.

Not that you made any mistakes in your PKGBUILD, but IMO this should always be the last current official release build which in this case is Trenchbroom 2023.1.

By updating this to TrenchBroom v2024.1-RC2-Release it's a WIP built already out of date. By promoting it you promote an unstable version. Not that it is unstable, but in the sense there are bugs in 2024.1 RC2 that have already been fixed in the most recent commits to TrenchBroom's main branch which could be built using trenchbroom-git.

keutain commented on 2024-02-29 17:34 (UTC)

Hello Retro_Gamer,

I'm sorry i'm starting to learn contributing to the AUR and found this orphaned package. You can have it of course, i will disown it.

Just for me to learn, where did i made mistakes ? It's was flagged as out of date so i took the last release on Github. It's not builded here, since I think that <package>-bin must no be build by the PKGBUILD (contrary to <package> and <package>-git)

Retro_Gamer commented on 2024-02-29 14:54 (UTC) (edited on 2024-02-29 15:02 (UTC) by Retro_Gamer)

I tried and someone already took It's now updated to the out of date 2024.1-RC2.

My pkgbuild builds a newer build with fewer bugs. At this point you might as well just build the most current build with trenchbroom-git

hilton commented on 2024-02-27 12:54 (UTC)

Oh I'm sorry 99cents, I missed your comment. I disowned for Retro_Gamer to take over.

99cents commented on 2024-01-17 03:06 (UTC)

$ trenchbroom
trenchbroom: error while loading shared libraries: cannot open shared object file: No such file or directory

there is no libtinyxml2 in Arch or the AUR

hilton commented on 2022-06-28 14:10 (UTC)

Hello, I'm not sure where the problem is. This icon file is already being installed by this PKGBUILD, so it should already be tracked by pacman on the last version, but it seems that this file is somehow not owned by this package in your system. Can you try checking who owns this file?

pacman -Qo /usr/share/icons/hicolor/512x512/apps/trenchbroom.png

If this file is not owned by any other package you will have to manually delete this png and then install this package. I don't see how this PKGBUILD would leave this file hanging though, cheers!

dwango commented on 2022-06-28 09:52 (UTC)

error: failed to commit transaction (conflicting files)
trenchbroom-bin: /usr/share/icons/hicolor/512x512/apps/trenchbroom.png exists in filesystem
Errors occurred, no packages were upgraded.

Perhaps this can be automated / fixed somehow?