Arch Linux

Description:

I noticed that 'pactree' produces different results for local and sync databases:

$ pactree -d1 gptfdisk
gptfdisk
├─gcc-libs
├─popt
├─lib32-util-linux provides libuuid.so <---difference
└─ncurses provides libncursesw.so

$ pactree -sd1 gptfdisk
gptfdisk
├─gcc-libs
├─popt
├─libutil-linux provides libuuid.so <---difference
└─ncurses provides libncursesw.so

The package 'gptfdisk' explicitly depends on 'libuuid.so=1-64'

$ pacman -Qi gptfdisk | grep Depends
Depends On: gcc-libs popt libuuid.so=1-64 libncursesw.so=6-64
^^^^^^^^^^^^^^^

There are two providers for 'libuuid.so':

$ pacman -Qi libutil-linux | grep Provides
Provides: libuuid.so=1-64 libblkid.so=1-64 libfdisk.so=1-64 libmount.so=1-64
^^^^^^^^^^^^^^^
$ pacman -Qi lib32-util-linux | grep Provides
Provides: libuuid.so=1-32 libblkid.so=1-32 libfdisk.so=1-32 libmount.so=1-32
^^^^^^^^^^^^^^^
When traversing the 'gptfdisk's dependency tree 'pactree' should use 'libutil-linux'. And it finds it by explicitly specifying the version. But without version it chooses lib32-util-linux.

$ pactree -d0 libuuid.so=1-64
libutil-linux provides libuuid.so=1-64

$ pactree -d0 libuuid.so
lib32-util-linux provides libuuid.so

So, in such cases, 'pactree' prints an incorrect dependency tree for the local database.


Package versions:
pacman 5.1.0-2
pacman-contrib 1.0.0-2

Forum's topic:
https://bbs.archlinux.org/viewtopic.php?pid=1791951