You are not logged in.
before i tried to install r2 bin, i had r2 appimage. i uninstalled it with a pacman -Rns, but it doesnt seem to have gone away.
error: failed to commit transaction (conflicting files)
r2modman-bin-debug: /usr/lib/debug/.build-id/1c/8d6ea21bf1a0f617f57cf6cf311b87b05ecd97 exists in filesystem (owned by vysor-bin-debug)
r2modman-bin-debug: /usr/lib/debug/.build-id/1c/8d6ea21bf1a0f617f57cf6cf311b87b05ecd97.debug exists in filesystem (owned by vysor-bin-debug)
r2modman-bin-debug: /usr/lib/debug/.build-id/22/0b49934c2e80edc92322baead00b57bd5f6219 exists in filesystem (owned by vysor-bin-debug)
r2modman-bin-debug: /usr/lib/debug/.build-id/22/0b49934c2e80edc92322baead00b57bd5f6219.debug exists in filesystem (owned by vysor-bin-debug)
r2modman-bin-debug: /usr/lib/debug/.build-id/44/8a07f59b13491266431a3ae922b2975406231d exists in filesystem (owned by vysor-bin-debug)
r2modman-bin-debug: /usr/lib/debug/.build-id/44/8a07f59b13491266431a3ae922b2975406231d.debug exists in filesystem (owned by vysor-bin-debug)
r2modman-bin-debug: /usr/lib/debug/.build-id/ba/5897986ef27da9eb639f792d833e17493f5f8f exists in filesystem (owned by vysor-bin-debug)
r2modman-bin-debug: /usr/lib/debug/.build-id/ba/5897986ef27da9eb639f792d833e17493f5f8f.debug exists in filesystem (owned by vysor-bin-debug)
r2modman-bin-debug: /usr/lib/debug/.build-id/e7/49795ba61b6b991ef0de6fa0bea087d12dac81 exists in filesystem (owned by vysor-bin-debug)
r2modman-bin-debug: /usr/lib/debug/.build-id/e7/49795ba61b6b991ef0de6fa0bea087d12dac81.debug exists in filesystem (owned by vysor-bin-debug)
Errors occurred, no packages were upgraded.
-> error installing: [/home/max/.cache/yay/r2modman-bin/r2modman-bin-3.2.0-1-x86_64.pkg.tar.zst /home/max/.cache/yay/r2modman-bin/r2modman-bin-debug-3.2.0-1-x86_64.pkg.tar.zst] - exit status 1
Offline
Do you need the debug package?
Mod note: moving to AUR Issues
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
im sorry, but how would i install the debug package?
Offline
You're trying to install r2modman-bin-debug, which conflicts with vysor-bin-debug. Do you need either?
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
i dont need vysor-bin-debug
Offline
solution i found was deleting the files in conflict, thanks
Offline
That is not a solution at all. Don't ever delete files owned by packages.
You said you didn't need the -debug packages, so take that one minor logical step further, if you don't need them, why are they installed and why are you trying to install more? Think it through before doing something dumb.
Offline
why are they installed and why are you trying to install more?
because:
- /etc/makepkg.conf by default contains the flag to build debug packages
- hence when yay as aur help calls makepkg it builds debug packages
- hence yay as aur helper installs debug packages along as they were build during makepkg call
- the wiki in typical archwiki fashion doesn't explain this to newbies but expects you to know this and to know that one option is to disable the debug flag in makepkg.conf
- this would also happen when not using an aur helper but calling the regular makepkg -si yourself because again it's nowhere properly explained that this builds and installs debug packages with default makepkg.conf
so - I myself see two options:
- properly extend the wiki to properly explain this
- change standard makepkg.conf to have the debug flag disabled by default (which likely came up in the past with a long argue about why it's there by default and why this won't be chanfed)
tldr: OP correctly started this in NC because they obvious don't know any better - moving this topic to aur because an aur package and helper are involved (which btw doesn't really matter for the base problem of OP being a newbie and doesn't know thier way around arch/linux) was the wrong move - which, as the wiki not properly explain, is typical mod behaviour here
or - to come full circle back around: because OP is a noob and made some noob mistake because no proper help was given
Offline
- properly extend the wiki to properly explain this
- use makepkg -rs as default flags
- run ls *.zst and choose what to install
- short note about split & debug packages
- use pacman -U to install
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline