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
checking dependencies...
Packages (1) bridge-utils-1.7.1-2
Total Removed Size: 0.03 MiB
:: Do you want to remove these packages? [Y/n]
I investigated the libxcrypt-compat package:
paru -Qi libxcrypt-compat
Name : libxcrypt-compat
Version : 4.4.38-1
Description : Modern library for one-way hashing of passwords - legacy API functions
Architecture : x86_64
URL : https://github.com/besser82/libxcrypt/
Licenses : LGPL
Groups : None
Provides : libcrypt.so=1-64
Depends On : libxcrypt
Optional Deps : None
Required By : None
Optional For : None
Conflicts With : None
Replaces : None
Installed Size : 174.02 KiB
Packager : Christian Hesse <[email protected]>
Build Date : Tue 14 Jan 2025 04:23:12 PM CET
Install Date : Thu 16 Jan 2025 10:30:17 PM CET
Install Reason : Installed as a dependency for another package
Install Script : Yes
Validated By : Signature
It's not required or optional for anything, but provides libcrypt.so=1-64. Using pyalpm I extracted installed packages that depend on libcrypt.so in any version:
All of them depend on version 2-64 which isn't what the package provides. This suggests that version isn't taken into account for cleanup logic. After digging through the code I found this:
Yep, another package provides that version. My conclusion - when looking for packages to remove during paru -c, provider versions need to be checked against dependency version requirements.
The text was updated successfully, but these errors were encountered:
Affected Version
paru -V
Description
Have you checked previous issues?
yes
Output
paru -Qdt
paru -c
I investigated the
libxcrypt-compat
package:paru -Qi libxcrypt-compat
It's not required or optional for anything, but provides
libcrypt.so=1-64
. Usingpyalpm
I extracted installed packages that depend onlibcrypt.so
in any version:All of them depend on version
2-64
which isn't what the package provides. This suggests that version isn't taken into account for cleanup logic. After digging through the code I found this:paru/src/util.rs
Line 174 in 55efaab
The code ignores provider version which seems to be taken into account when finding "real orphans".
Just to be sure I checked if anything provides the correct version on my system:
Yep, another package provides that version. My conclusion - when looking for packages to remove during
paru -c
, provider versions need to be checked against dependency version requirements.The text was updated successfully, but these errors were encountered: