Closed Aetf closed 2 years ago
Actually, even when not skip upgrading the aur package, the same panic happens:
$ RUST_BACKTRACE=full cargo run
Finished dev [unoptimized + debuginfo] target(s) in 0.09s
Running `target/debug/paru`
no new news
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
aur is up to date
multilib is up to date
:: Looking for AUR upgrades
:: Looking for devel upgrades
9 extra/alsa-card-profiles 1:0.3.43-1 -> 1:0.3.43-5
8 extra/libical 3.0.12-1 -> 3.0.13-1
7 extra/pipewire 1:0.3.43-1 -> 1:0.3.43-5
6 extra/pipewire-alsa 1:0.3.43-1 -> 1:0.3.43-5
5 extra/pipewire-jack 1:0.3.43-1 -> 1:0.3.43-5
4 extra/pipewire-pulse 1:0.3.43-1 -> 1:0.3.43-5
3 community/crun 1.4-1 -> 1.4.1-1
2 community/fuse-overlayfs 1.8-1 -> 1.8.1-1
1 aur/latte-dock-git r5852.2b039e12-1 -> r5853.e326dddb-1
:: Packages to exclude (eg: 1 2 3, 1-3):
::
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: PkgNotFound', /dev/shm/aetf/workspace/paru/src/upgrade.rs:340:46
To provide more context, I think this may be related to the previous paru -Syu
run, where in addition to those pipewire updates in the offical repos, there are extra-cmake-modules-git
and latte-dock-git
from AUR.
However, this run of paru
failed because pipewire-jack
now conflicts with jack2
, and paru automatically failed the prompt without me getting a chance to confirm the removal:
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
:: pipewire-jack and jack2 are in conflict (jack). Remove jack2? [y/N]
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: pipewire-jack and jack2 are in conflict
Now wondering why I didn't get a chance to confirm, I rerun parun -Syu
and got the panic reported in the beginning.
You paru conf shows the local repo options commented out. Is that correct?
It's enabled at the bottom:
# Custom options from ansible
[options]
BottomUp
RemoveMake
SudoLoop
CombinedUpgrade
CleanAfter
UpgradeMenu
NewsOnUpgrade
LocalRepo
Chroot
# END ANSIBLE MANAGED BLOCK
Oh right i saw the [bin] line and glossed over. Doesn't matter, fixed it anyway :P
Affected Version
paru -V:
paru v1.9.2 - libalpm v13.0.1
Also affects latest
master
commit: 501e0baDescription
I have the local AUR repository and chroot build enabled. Today, when doing a normal
paru -Syu
, I wanted to skip the AUR package upgrade temporarily, and the panic occurs.Have you checked previous issues? Not found in open issues.
Output
Output when running from source to show backtrace:
I have no
~/.config/paru/paru.conf
, only/etc/paru.conf
My
pacman.conf
is splitted across multiple files:/etc/pacman.conf