Package Details: r2modman-bin 3.2.18-1

Git Clone URL: https://aur.archlinux.org/r2modman-bin.git (read-only, click to copy)
Package Base: r2modman-bin
Description: A simple and easy to use mod manager for several games using Thunderstore.
Upstream URL: https://github.com/ebkr/r2modmanPlus
Licenses: MIT
Conflicts: r2modman
Provides: r2modman
Submitter: oynyo
Maintainer: oynyo
Last Packager: oynyo
Votes: 47
Popularity: 5.29
First Submitted: 2023-03-25 21:55 (UTC)
Last Updated: 2026-06-25 08:59 (UTC)

Latest Comments

1 2 Next › Last »

oynyo commented on 2026-07-07 12:45 (UTC)

There is indeed no particular reason for the md5sums vs sha256sums, so I can change it as part of the next release.

However, installing from AUR should be putting skepticism on the PKGBUILD and its maintainer anyway. Crosschecking checksums between the AUR and upstream may relieve this, but installing directly from upstream would be better.

gesh commented on 2026-07-06 21:25 (UTC)

Why is the package using md5sums when upstream provides a sha256sum? This redirects trust from upstream to the packager for no good reason.

dreamingweasel commented on 2025-12-06 04:01 (UTC) (edited on 2025-12-06 04:10 (UTC) by dreamingweasel)

Hello, I noticed that http-parser is still a dep on this package, is there any current intention to switch to llhttp per: https://archlinux.org/todo/move-to-llhttp-from-http-parser/ ?

Or is this not possible per the nature of the package?

(Seems like the upstream package (.pacman file) deps http-parser as well, so this might not be possible on the AUR side)

Github issue open here: https://github.com/ebkr/r2modmanPlus/issues/2013

oynyo commented on 2025-09-22 11:49 (UTC)

Reading the latest of this thread (https://bbs.archlinux.org/viewtopic.php?id=293055), it seems that it would be related to overlapping debug symbols that are used by all of those packages. As in the thread, if you don't need the *-debug packages, I would suggest changing /etc/makepkg.conf to adjust this.

zeroz commented on 2025-09-21 23:20 (UTC)

r2modman-bin-debug: /usr/lib/debug/.build-id/df/28017d426455b189e0f1bb054805f3fec8f3e7 exists in filesystem (owned by bitwarden-bin-debug) r2modman-bin-debug: /usr/lib/debug/.build-id/df/28017d426455b189e0f1bb054805f3fec8f3e7.debug exists in filesystem (owned by bitwarden-bin-debug)

The build-id of this package conflicts with others, including bitwarden and mullvad vpn.How is that generated, hash of the electron binary?

oynyo commented on 2024-07-26 06:37 (UTC)

@seanfire99 This seems to be an on-going problem upstream with NVIDIA GPUs: https://github.com/ebkr/r2modmanPlus/issues/1395 https://github.com/ebkr/r2modmanPlus/issues/1383. Hopefully it gets resolved within the next release.

seanfire99 commented on 2024-07-26 06:05 (UTC) (edited on 2024-07-26 06:31 (UTC) by seanfire99)

r2modman starting server on /tmp/app.r2mm starting TLS server false starting server as Unix || Windows Socket [364406:0725/230120.935634:FATAL:gpu_data_manager_impl_private.cc(445)] GPU process isn't usable. Goodbye. Trace/breakpoint trap (core dumped)

running r2modman --no-sandbox fixes the problem launches fine now but i am curios as to why it started doing this when it never did this before

oynyo commented on 2024-01-21 19:58 (UTC)

@nova8x Are these issues new with the latest version? Given that two installations are experiencing the same problem, it would likely be worth it to raise an issue on the upstream and not here.

nova8x commented on 2024-01-20 19:28 (UTC) (edited on 2024-01-20 19:28 (UTC) by nova8x)

I seem to be experiencing some flickering in both this and the appimage officially distributed whilst in the app. The UI lags behind and goes black occasionally. Tried with both --no-sanbox and --in-process-gpu. Plasma-Wayland and nvidia proprietary drivers

1 2 Next › Last »