Arch Linux User Repository

20250106:

Updated to current TrenchBroom 2024.2.r26 This is actually a few commits past official 2024.2 release due to some bugs with texture *.wad handling found after it was released. This PKGBUILD won't be updated again unless some unknown major bug is discovered.

As always for the most up-to-date bleeding edge commits use the AUR trenchbroom-git entry

For Quake 2 remaster mappers I have a 3rd party TrenchBroom game support Quake2RE add-on it here on GitHub.

If you need general Quake, Quake 2, or Quake 3 mapping help please come visit the Map-Center discord. All skill levels welcome!

@Retro_Gamer: new version of the package is failing to build for me, seems like a git checkout error. this is the output paru gives me:

==> Extracting sources...
  -> Creating working copy of trenchbroom git repo...
Cloning into 'trenchbroom'...
done.
fatal: invalid reference: origin/4753-2

@ronjouch ah shoot! Yeah, not intentional, I goof with a copy/paste or 2. Fixing now and updating again. I really appreciate the feedback! Thanks.

EDIT: Should be fixed now.

@Retro_Gamer: package bug report: latest update from today January 6 incorrectly resolves to a version older than the previous version, resulting in older version superseding the new version and AUR helper update failing to happen. This is what yay shows:

trenchbroom-bin: local (2024.1-2) is newer than AUR (v2024.2.r26.g1877724f3-1)

(I think the culprit is the the pkgrel that you lowered from 2 to 1. Should keep it at 2, or bump it to 3)

Also, was the move from 2024... to v2024... intentional?

20250106:

Updated to current TrenchBroom 2024.2.r26 This is actually a few commits past official 2024.2 release due to some bugs with texture *.wad handling found after it was released. This PKGBUILD won't be updated again unless some unknown major bug is discovered.

As always for the most up-to-date bleeding edge commits use the AUR trenchbroom-git entry

For Quake 2 remaster mappers I have a 3rd party TrenchBroom game support Quake2RE add-on it here on GitHub.

If you need general Quake, Quake 2, or Quake 3 mapping help please come visit the Map-Center discord. All skill levels welcome!

That is a weird coincidence. Seems fine on my end from the terminal using yay -S trenchbroom-bin

Glad you got it working with pamac.

Well this was a strange coincidence. I was just about to post that I was also affected by the sudo issue on Manjaro, so I created an account and refreshed the page. Then I see that Yoplitein posted that they figured out the issue 3 minutes ago. Somewhere out there, someone is doing the same thing as me on the same OS. Small world.

Anyway, pamac build trenchbroom-bin was successful for me. Pamac asks for my sudo password later on and the process completes successfully. Previously, sudo pamac build trenchbroom-bin exited with the following error.

x ./usr/share/mime/packages/trenchbroom.xml
sudo: The "no new privileges" flag is set, which prevents sudo from running as root.
sudo: If sudo is running in a container, you may need to adjust the container configuration to disable the flag.
==> ERROR: A failure occurred in prepare().
    Aborting...
Finished with result: exit-code
Main processes terminated with: code=exited, status=4/NOPERMISSION

I also get an error related to the sudo ln in prepare():

sudo: /etc/sudo.conf is owned by uid 65534, should be 0
sudo: The "no new privileges" flag is set, which prevents sudo from running as root.
sudo: If sudo is running in a container, you may need to adjust the container configuration to disable the flag.

which I suspect is caused by packages being built in a fakeroot.

I fixed this by instead updating the library name in the executable using patchelf. My patch:

diff --git a/PKGBUILD b/PKGBUILD
index d20ac51..999509c 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -15,2 +15,3 @@ conflicts=('trenchbroom' 'trenchbroom-git')
 depends=("freeimage" "freetype2" "mesa" "libgl" "freeglut" "libxxf86vm" "glew" "glm" "tinyxml2")
+makedepends=("patchelf")
 source=("https://github.com/TrenchBroom/TrenchBroom/releases/download/v$pkgver/$_pkgname-$_pkgver.deb")
@@ -24,4 +25,4 @@ prepare() {
   bsdtar xvf "$pkgname-$pkgver/data.tar.gz" -C "$pkgname-$pkgver-files"
-  # Ubuntu TB2024.1 requires libtinyxml2.so.9 / Arch is on 10, look for a valid symlink of 9, if none, create one from current libtinyxml2.10.0.0
-  if [ ! -e "/usr/lib/libtinyxml2.so.9" ]; then sudo ln -s "/usr/lib/libtinyxml2.so.10.0.0" "/usr/lib/libtinyxml2.so.9"; else echo "complete"; fi
+  # Ubuntu TB2024.1 requires libtinyxml2.so.9 / Arch is on 10
+  patchelf --replace-needed libtinyxml2.so.9 libtinyxml2.so.10 "$pkgname-$pkgver-files/usr/bin/trenchbroom"
 }

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.

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().
    Aborting...

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.