Package Details: trenchbroom-bin 2024.1-2

Git Clone URL: https://aur.archlinux.org/trenchbroom-bin.git (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: https://trenchbroom.github.io/
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: 0.101871
First Submitted: 2022-04-21 01:20 (UTC)
Last Updated: 2024-03-08 22:09 (UTC)

Latest Comments

1 2 Next › Last »

Retro_Gamer commented on 2024-09-20 13:29 (UTC)

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.

cj54 commented on 2024-09-10 05:42 (UTC)

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

Yoplitein commented on 2024-09-10 05:33 (UTC)

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"
 }

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

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..lol. 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.