Lib32-util-linux and lib32-util-linux-ng are in conflict

Question

hi
i'm running a 64bit arch linux (with some 32bit apps)
today i got a strange conflict - and the "solution" seems pretty dangerous to me, or am i wrong?
[root:~]# pacman -S multilib/dwarffortress
resolving dependencies...
looking for inter-conflicts...
:: lib32-util-linux and lib32-util-linux-ng are in conflict. Remove lib32-util-linux-ng? [y/N] Y
Remove (1): lib32-util-linux-ng-2.18-3
Total Removed Size: 0.58 MB
Targets (41): lib32-libxfixes-4.0.5-3 lib32-libxdamage-1.1.3-3 lib32-pcre-8.10-3 lib32-dbus-core-1.4.0-2 lib32-glib2-2.26.1-2
lib32-atk-1.32.0-1 lib32-pixman-0.20.2-1 lib32-cairo-1.10.0-3 lib32-pango-1.28.3-1 lib32-util-linux-2.19-1
lib32-e2fsprogs-1.41.14-2 lib32-openssl-1.0.0.d-1 lib32-db-5.1.19-1 lib32-sqlite3-3.7.4-1 lib32-heimdal-1.3.3-3
lib32-ncurses-5.7-6 lib32-readline-6.1.002-3 lib32-libgpg-error-1.9-4 lib32-libgcrypt-1.4.6-3 lib32-gnutls-2.10.4-1
lib32-libtiff-3.9.4-3 lib32-gdk-pixbuf2-2.22.1-1 lib32-libcups-1.4.5-1 lib32-libxcursor-1.1.11-1
lib32-libxrandr-1.3.1-1 lib32-libxi-1.4.1-1 lib32-libxcomposite-0.4.3-1 lib32-gtk2-2.22.1-2 lib32-libdrm-2.4.23-1
lib32-libxxf86vm-1.1.1-1 lib32-libgl-7.10.1-1 lib32-mesa-7.10.1-1 lib32-sdl-1.2.14-8 lib32-sdl_image-1.2.10-3
lib32-flac-1.2.1-7 lib32-libsndfile-1.0.23-2 openal-1.12.854-2 lib32-openal-1.12.854-4 sdl_ttf-2.0.10-1
lib32-sdl_ttf-2.0.10-3 dwarffortress-0.31.21-1
Total Download Size: 9.07 MB
Total Installed Size: 79.96 MB

Answer 1

ulukay wrote:
ngoonee wrote:Firstly, searches are not cached, so noone would be able to view your link properly. However yes somehow I've seen that the other threads on this are not turning up, so I suggest instead searching for 'util-linux', not 'lib32-util-linux', you will find the solution then.
1. thanks for not simply posting a link
2. that search would return threads regarding this problem on 32bit hosts - i run a 64bit host. my main concern is that this would install incompatible 32bit binaries.
1. You're welcome. Self-help is the best kind.
2. If you'd done the search I recommended you would have seen that the problem is not related to arch at all, but is due to upstream renaming.