Paru does not allow user input for conflict resolution when syncing packages

[solonovamax]

Affected Version

paru v2.0.4 - libalpm v15.0.0

Description

Paru does not allow user input for conflict resolution when syncing packages.

Output

When running paru -S ollama (in this instance, ollama-rocm is currently installed, and the ollama package conflicts with it):

resolving dependencies...
looking for conflicting packages...
:: ollama-0.4.3-1 and ollama-rocm-0.4.2-2 are in conflict. Remove ollama-rocm? [y/N] y

Package (2)   Old Version  New Version  Net Change   Download Size

ollama-rocm   0.4.2-2                   -710.58 MiB
extra/ollama               0.4.3-1        34.02 MiB      16.48 MiB

Total Download Size:     16.48 MiB
Total Installed Size:    34.02 MiB
Net Upgrade Size:      -676.56 MiB

:: Proceed with installation? [Y/n] y
:: Retrieving packages...
 ollama-0.4.3-1-x86_64                                    16.5 MiB  5.14 MiB/s 00:03 [################################################] 100%
(1/1) checking keys in keyring                                                       [################################################] 100%
(1/1) checking package integrity                                                     [################################################] 100%
(1/1) loading package files                                                          [################################################] 100%
(1/1) checking for file conflicts                                                    [################################################] 100%
(2/2) checking available disk space                                                  [################################################] 100%
:: Processing package changes...
(1/1) removing ollama-rocm                                                           [################################################] 100%
(1/1) installing ollama                                                              [################################################] 100%
:: Running post-transaction hooks...
(1/4) Creating system user accounts...
(2/4) Reloading system manager configuration...
(3/4) Creating temporary files...
(4/4) Arming ConditionNeedsUpdate...

When it prints the line :: ollama-0.4.3-1 and ollama-rocm-0.4.2-2 are in conflict. Remove ollama-rocm? [y/N], it did allow user-input. Here, I selected "y" and allowed the installation to continue. This is the expected behaviour.

---

When running paru -Sy ollama (in this instance, ollama-rocm is currently installed, and the ollama package conflicts with it):

:: Synchronizing package databases...
 core is up to date
 extra is up to date
 multilib is up to date
 home_ungoogled_chromium_Arch is up to date
:: Resolving dependencies...

Repo (1)      Old Version  New Version    Make Only
extra/ollama               0.4.3-1        No

:: Proceed with installation? [Y/n]: y
resolving dependencies...
looking for conflicting packages...
:: ollama-0.4.3-1 and ollama-rocm-0.4.2-2 are in conflict. Remove ollama-rocm? [y/N]
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: ollama-0.4.3-1 and ollama-rocm-0.4.2-2 are in conflict

When it prints the line :: ollama-0.4.3-1 and ollama-rocm-0.4.2-2 are in conflict. Remove ollama-rocm? [y/N], it does not allow any user input and instead immediately assumes N was supplied/selected.
This behaviour is not expected. It should work the same as when -y is not supplied.

Configs

pacman.conf

I've trimmed my pacman.conf to remove useless comments, for brevity.

#
# /etc/pacman.conf
#
# See the pacman.conf(5) manpage for option and repository directives

Architecture = auto

# Misc options
Color
CheckSpace
VerbosePkgLists
ParallelDownloads = 8
# For stupid networks that throttle per-connection, use a fuck ton of connections
#ParallelDownloads = 128

# By default, pacman accepts packages signed by keys that its local keyring
# trusts (see pacman-key and its man page), as well as unsigned packages.
SigLevel    = Required DatabaseOptional Optional
#LocalFileSigLevel = Optional
LocalFileSigLevel = Never
#RemoteFileSigLevel = Required

# NOTE: You must run `pacman-key --init` before first using pacman; the local
# keyring can then be populated with the keys of all official Arch Linux
# packagers with `pacman-key --populate archlinux`.

# REPOSITORIES

[core]
Include = /etc/pacman.d/mirrorlist

[extra]
Include = /etc/pacman.d/mirrorlist

# If you want to run 32 bit applications on your x86_64 system,
# enable the multilib repositories as required here.

[multilib]
Include = /etc/pacman.d/mirrorlist

[home_ungoogled_chromium_Arch]
SigLevel = Required TrustAll
Server = https://download.opensuse.org/repositories/home:/ungoogled_chromium/Arch/$arch

paru.conf

#
# $PARU_CONF
# /etc/paru.conf
# ~/.config/paru/paru.conf
#
# See the paru.conf(5) manpage for options

#
# GENERAL OPTIONS
#
[options]
PgpFetch
Devel
Provides = all
DevelSuffixes = -git -cvs -svn -bzr -darcs -always -hg -fossil
#AurOnly
#BottomUp

# Remove makedepends after installing package
RemoveMake

# Periodically call sudo to prevent it from timing out
SudoLoop

#UseAsk

# Saves changes to PKGBUILDs
SaveChanges

# Show combined menu for upgrading repo & AUR packages
CombinedUpgrade

CleanAfter

# Show a list of updates, allowing you to skip some
UpgradeMenu

# Print new news during upgrade
NewsOnUpgrade

# Batch installation of AUR packages
BatchInstall

#LocalRepo
#Chroot
#Sign
#SignDb
#KeepRepoCache

#
# Binary OPTIONS
#
[bin]
#FileManager = vifm
#MFlags = --skippgpcheck
#Sudo = doas
BatFlags = --tabs 4 --style plain,changes,grid,rule,numbers --wrap never
Pager = less -S