You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ pikaur -Vq
:: warning:
Read damn arch-wiki before borking your computer:
https://wiki.archlinux.org/title/Arch_User_Repository
(Also, don't report any issues to pikaur, if ure seeing this message)
Pikaur v1.23
Pacman v6.1.0 - libalpm v14.0.0 - pyalpm v0.10.6
Description:
I'm doing a system-wide upgrade on a machine with aur/gdb-multiarch installed. The gdb-multiarch package lists gdb-common with a strict version number as a dependency. Therefore, a trivial pikaur -Syu will result in an unresolvable dependency error as gdb-common will get upgraded to a new version in the same transaction. Hence, I'm using the --assume-installed option from pacman to get over it. Surprisingly, pikaur seems to append an --assume_installed option to the pacman command, which leads to an unrecognized option error. I'm unsure whether it was a valid option historically, but patching it out is recommended.
Attached log:
$ pikaur -Syu --assume-installed=gdb-common=14.2
pacman: unrecognized option '--assume_installed'
Command 'pacman --color=always --assume-installed gdb-common=14.2 --sync --assume_installed --sysupgrade --ignore electron22 --ignore spotify --ignore ceph-libs' failed to execute.
Do you want to retry? [Y/n] n
Do you want to proceed? [y/N] n
The text was updated successfully, but these errors were encountered:
Description:
I'm doing a system-wide upgrade on a machine with
aur/gdb-multiarch
installed. Thegdb-multiarch
package listsgdb-common
with a strict version number as a dependency. Therefore, a trivialpikaur -Syu
will result in an unresolvable dependency error asgdb-common
will get upgraded to a new version in the same transaction. Hence, I'm using the--assume-installed
option from pacman to get over it. Surprisingly, pikaur seems to append an--assume_installed
option to the pacman command, which leads to an unrecognized option error. I'm unsure whether it was a valid option historically, but patching it out is recommended.Attached log:
The text was updated successfully, but these errors were encountered: