Remove python-vdf-solstice warning when updating

Hello everyone,

When I update the system, both in garuda-update or garuda-rani, I get this warning:

(11/22) Checking for package with missing dependencies...

Package "python-vdf-solstice" has files in directory "/usr/lib/python3.12" that are ignored by the current Python interpreter

(12/22) Updating initramfs with dracut
:: Building initramfs for linux-zen (6.16.2-zen1-1-zen)
:: Building fallback initramfs for linux-zen (6.16.2-zen1-1-zen)
(13/22) Updating linux initcpios...
(14/22) Refreshing PackageKit...

I would like to clean it up. I know it’s not an error, but you know, you always want to know why things happen on your system and be able to clean it up, at least for me.

I think it just means that there are files that are not part of the program itself, but rather user licenses, old configurations, and things like that. At least that’s what I’ve been able to find out. This is its content:

╰─λ ls -R /usr/lib/python3.12/
drwxr-xr-x - root 28 dic  2024  site-packages

/usr/lib/python3.12/site-packages:
drwxr-xr-x - root 17 ago  2024 vdf
drwxr-xr-x - root 17 ago  2024 vdf-3.5.dist-info

/usr/lib/python3.12/site-packages/vdf:
drwxr-xr-x    - root 17 ago  2024 __pycache__
.rw-rw-r--  19k root 29 jul  2024 __init__.py
.rw-rw-r-- 7,1k root 29 jul  2024 vdict.py

/usr/lib/python3.12/site-packages/vdf/__pycache__:
.rw-rw-r-- 23k root 29 jul  2024 __init__.cpython-312.opt-1.pyc
.rw-rw-r-- 23k root 29 jul  2024 __init__.cpython-312.pyc
.rw-rw-r-- 14k root 29 jul  2024 vdict.cpython-312.opt-1.pyc
.rw-rw-r-- 14k root 29 jul  2024 vdict.cpython-312.pyc

/usr/lib/python3.12/site-packages/vdf-3.5.dist-info:
.rw-rw-r-- 1,1k root 29 jul  2024 LICENSE
.rw-rw-r-- 6,0k root 29 jul  2024 METADATA
.rw-rw-r--  577 root 29 jul  2024 RECORD
.rw-rw-r--    4 root 29 jul  2024 top_level.txt
.rw-rw-r--   92 root 29 jul  2024 WHEEL
.rw-rw-r--    1 root 29 jul  2024 zip-safe

Can that entire directory be deleted, since it’s from an old version? If not, how can it be removed? Any recommendations for cleaning up that warning?

My garuda-inxi:

System:
Kernel: 6.16.2-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=1b079d8b-58a3-4533-8245-22b97207f1e1 rw rootflags=subvol=@
pcie_aspm=off quiet loglevel=3
Desktop: KDE Plasma v: 6.4.4 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
Distro: Garuda base: Arch Linux
Machine:
Type: Desktop System: Gigabyte product: Z390 AORUS PRO v: N/A serial: N/A
Mobo: Gigabyte model: Z390 AORUS PRO-CF serial: N/A
uuid: 032e02b4-0499-05ed-6b06-c80700080009 UEFI: American Megatrends v: F14b
date: 06/12/2025
CPU:
Info: model: Intel Core i9-9900K socket: LGA1151 (U3E1) note: check bits: 64
type: MT MCP arch: Coffee Lake gen: core 9 level: v3 note: check built: 2018
process: Intel 14nm family: 6 model-id: 0x9E (158) stepping: 0xD (13)
microcode: 0x104
Topology: cpus: 1x dies: 1 clusters: 8 cores: 8 threads: 16 tpc: 2
smt: enabled cache: L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 2 MiB
desc: 8x256 KiB L3: 16 MiB desc: 1x16 MiB
Speed (MHz): avg: 3985 min/max: 800/5000 base/boost: 4700/8300 scaling:
driver: intel_pstate governor: powersave volts: 1.3 V ext-clock: 100 MHz
cores: 1: 3985 2: 3985 3: 3985 4: 3985 5: 3985 6: 3985 7: 3985 8: 3985
9: 3985 10: 3985 11: 3985 12: 3985 13: 3985 14: 3985 15: 3985 16: 3985
bogomips: 115200
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA TU104 [GeForce RTX 2080 SUPER] vendor: Gigabyte
driver: nvidia v: 580.76.05 alternate: nouveau,nvidia_drm
non-free: 550-570.xx+ status: current (as of 2025-04; EOL~2026-12-xx)
arch: Turing code: TUxxx process: TSMC 12nm FF built: 2018-2022 pcie:
gen: 2 speed: 5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s ports:
active: none off: DP-2,DP-3 empty: DP-1,HDMI-A-1,Unknown-2 bus-ID: 01:00.0
chip-ID: 10de:1e81 class-ID: 0300
Display: unspecified server: X.Org v: 24.1.8 with: Xwayland v: 24.1.8
compositor: kwin_wayland driver: X: loaded: nvidia
unloaded: modesetting,nouveau alternate: fbdev,nv,vesa
gpu: nv_platform,nvidia,nvidia-nvswitch display-ID: :1 screens: 1
Screen-1: 0 s-res: 4268x1440 s-dpi: 96 s-size: 1129x381mm (44.45x15.00")
s-diag: 1192mm (46.91")
Monitor-1: DP-2 note: disabled pos: primary,top-right
model: Asus ROG PG279Q serial: <filter> built: 2017 res: mode: 2560x1440
hz: 120 scale: 100% (1) dpi: 109 gamma: 1.2 size: 598x336mm (23.54x13.23")
diag: 686mm (27") ratio: 16:9 modes: max: 2560x1440 min: 640x480
Monitor-2: DP-3 note: disabled pos: bottom-l model: Philips 191EL
serial: <filter> built: 2010 res: mode: 1708x960 hz: 60 scale: 100% (1)
dpi: 106 gamma: 1.2 size: 410x230mm (16.14x9.06") diag: 470mm (18.5")
ratio: 16:9 modes: max: 1366x768 min: 640x480
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia
inactive: wayland,device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 580.76.05
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 2080
SUPER/PCIe/SSE2 memory: 7.81 GiB
API: Vulkan v: 1.4.321 layers: 12 device: 0 type: discrete-gpu name: NVIDIA
GeForce RTX 2080 SUPER driver: nvidia v: 580.76.05 device-ID: 10de:1e81
surfaces: N/A device: 1 type: cpu name: llvmpipe (LLVM 20.1.8 256 bits)
driver: mesa llvmpipe v: 25.2.1-arch1.1 (LLVM 20.1.8)
device-ID: 10005:0000 surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: corectrl, nvidia-settings,
nvidia-smi wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: NVIDIA TU104 HD Audio vendor: Gigabyte driver: snd_hda_intel
v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.1
chip-ID: 10de:10f8 class-ID: 0403
Device-2: Creative Labs CA0132 Sound Core3D [Sound Blaster Recon3D /
Z-Series BlasterX AE-5 Plus] driver: snd_hda_intel v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 1102:0012 class-ID: 0403
API: ALSA v: k6.16.2-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 1.4.7 status: n/a (root, process) with:
1: pipewire-pulse status: active 2: wireplumber status: active
3: pipewire-alsa type: plugin 4: pw-jack type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Ethernet I219-V vendor: Gigabyte driver: e1000e v: kernel
port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15bc class-ID: 0200
IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd
Drives:
Local Storage: total: 3.18 TiB used: 1.48 TiB (46.3%)
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Crucial model: CT1000P5SSD8
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: P4CR313 temp: 41.9 C
scheme: GPT
SMART: yes health: PASSED on: 227d 13h cycles: 6,700
read-units: 66,506,052 [34.0 TB] written-units: 47,533,817 [24.3 TB]
ID-2: /dev/sda maj-min: 8:0 vendor: Crucial model: CT500MX500SSD1
family: Micron Client SSDs size: 465.76 GiB block-size: physical: 512 B
logical: 512 B sata: 3.3 speed: 6.0 Gb/s tech: SSD serial: <filter>
fw-rev: 023 temp: 46 C scheme: GPT
SMART: yes state: enabled health: PASSED on: 1y 55d 23h cycles: 8734
written: 13.22 TiB
ID-3: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST2000DM001-1CH164
family: Barracuda 7200.14 (AF) size: 1.82 TiB block-size: physical: 4096 B
logical: 512 B sata: 3.1 speed: 6.0 Gb/s tech: HDD rpm: 7200
serial: <filter> fw-rev: CC27 temp: 40 C scheme: MBR
SMART: yes state: enabled health: PASSED on: 2y 78d 5h cycles: 9507
read: 51.67 TiB written: 36.87 TiB Pre-Fail: attribute: Spin_Retry_Count
value: 100 worst: 100 threshold: 97
Partition:
ID-1: / raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 243.28 GiB (52.3%) fs: btrfs block-size: 4096 B dev: /dev/sda2
maj-min: 8:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 612 KiB (0.2%) fs: vfat block-size: 512 B dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 243.28 GiB (52.3%) fs: btrfs block-size: 4096 B dev: /dev/sda2
maj-min: 8:2
ID-4: /var/log raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 243.28 GiB (52.3%) fs: btrfs block-size: 4096 B dev: /dev/sda2
maj-min: 8:2
ID-5: /var/tmp raw-size: 465.46 GiB size: 465.46 GiB (100.00%)
used: 243.28 GiB (52.3%) fs: btrfs block-size: 4096 B dev: /dev/sda2
maj-min: 8:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 62.72 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 39.0 C pch: 55.0 C mobo: 35.0 C
Fan Speeds (rpm): cpu: 0 fan-2: 0 fan-3: 0
Power: 12v: N/A 5v: N/A 3.3v: 3.36 vbat: 3.07
Info:
Memory: total: 64 GiB available: 62.72 GiB used: 5.55 GiB (8.8%)
Processes: 392 Power: uptime: 54m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 25.02 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1940 libs: 568 tools: octopi,pacseek,pamac,paru
Compilers: gcc: 15.2.1 Shell: Bash (sudo) v: 5.3.3 running-in: konsole
inxi: 3.3.38
Garuda (2.8.1-2):
System install date:     2024-08-17
Last full system update: 2025-08-22
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       Yes
Failed units:            run-media-MULTIMEDIA.mount
--- System Health Check Report ---
23/23 checks run in 0.73 seconds ⌛
Powered by garuda-health 🦅

--- LOW ---
- Failed systemd services found: run-media-MULTIMEDIA.mount

Current is python 3.13.7.1.
python-vdf-solstice is only avaible on github. (work only with python 3.12)
python-vdf (for working with Valve’s VDF text format)
Install this if needed with sudo pacman -S python-vdf
Current it install inside folder/ files /usr/lib/python3.13
With paru -R python-vdf-solstice (if installed) or manual deletion should this solve your problem.

4 Likes

Thanks for the information, it’s been great. It has enlightened me about the different versions of python-vdf.

In the end, I decided to look in pacseek first and found that only python-vdf-solstice was installed. So I told it to install python-vdf, and voilà, it first asked me to uninstall python-vdf-solstice because it was conflicting. I said yes, and it just deleted the directory for version 3.12, removed the old version, and now I don’t get any warnings when updating.

Pacseek is awesome. Put pacseek in your life! Hahaha.

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.