Arch Linux

sLLiK

Member

Registered: 2011-09-10

Posts: 9

Dependency cycle (as expected) caused by libglvnd+mesa changes

Just did a recent pacman -Syu and discovered the changes related to libglvnd that have been in testing were just pushed.  I've read elsewhere that these changes cause a dependency cycle, but it's worth asking for those like myself - what's the best and safest method of forcing this upgrade to go through with no negative outcome?  --force on mesa and libglvnd?  It also looks like a similar condition exists via multilib as well:

:: Starting full system upgrade...
:: Replace lib32-nvidia-libgl with multilib/lib32-nvidia-utils? [Y/n] y
:: Replace nvidia-libgl with extra/nvidia-utils? [Y/n] y
resolving dependencies...
looking for conflicting packages...
warning: dependency cycle detected:
warning: mesa will be installed before its libglvnd dependency
warning: dependency cycle detected:
warning: nvidia-utils will be installed before its libglvnd dependency
warning: dependency cycle detected:
warning: nvidia-utils will be installed before its libglvnd dependency
warning: dependency cycle detected:
warning: lib32-mesa will be installed before its lib32-libglvnd dependency
warning: dependency cycle detected:
warning: lib32-nvidia-utils will be installed before its lib32-libglvnd dependency

---

Archlinux, finch, git, mutt, pmus, rvm, tmux, urxvtc, vim, weechat and wmfs..... intellectual nirvana achieved.

Trilby

Inspector Parrot

Registered: 2011-11-29

Posts: 29,523

Website

Re: Dependency cycle (as expected) caused by libglvnd+mesa changes

No, don't force anything.  If you needed to use '--force' this would be clearly and explicitly stated in a full pacman command in the news item.  Just use pacman -Syu and answer "y" as you did to the prompts (or just hit enter).

I presume you had a problem doing this, but you cut off all the output that would actually show a problem.  Those are only warnings in the output you showed, and pacman will go forward just fine with those warnings.

---

"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

phonky

Member

Registered: 2008-12-19

Posts: 69

Re: Dependency cycle (as expected) caused by libglvnd+mesa changes

Indeed I have a problem with that now.

After pacman -Syu, I got these warnings:

warning: dependency cycle detected:
warning: mesa will be installed before its libglvnd dependency
warning: dependency cycle detected:
warning: lib32-libglvnd will be installed before its lib32-mesa dependency

But then, installation fails with the following message:

(150/150) checking for file conflicts                                                                                                           [########################################################################################] 100%
error: failed to commit transaction (conflicting files)
libglvnd: /usr/lib/libEGL.so exists in filesystem
libglvnd: /usr/lib/libEGL.so.1 exists in filesystem
libglvnd: /usr/lib/libEGL.so.1.0.0 exists in filesystem
libglvnd: /usr/lib/libGL.so exists in filesystem
libglvnd: /usr/lib/libGL.so.1 exists in filesystem
libglvnd: /usr/lib/libGLESv1_CM.so exists in filesystem
libglvnd: /usr/lib/libGLESv1_CM.so.1 exists in filesystem
libglvnd: /usr/lib/libGLESv2.so exists in filesystem
libglvnd: /usr/lib/libGLESv2.so.2 exists in filesystem
libglvnd: /usr/lib/libGLESv2.so.2.0.0 exists in filesystem
lib32-libglvnd: /usr/lib32/libEGL.so exists in filesystem
lib32-libglvnd: /usr/lib32/libEGL.so.1 exists in filesystem
lib32-libglvnd: /usr/lib32/libEGL.so.1.0.0 exists in filesystem
lib32-libglvnd: /usr/lib32/libGL.so exists in filesystem
lib32-libglvnd: /usr/lib32/libGL.so.1 exists in filesystem
lib32-libglvnd: /usr/lib32/libGLESv1_CM.so exists in filesystem
lib32-libglvnd: /usr/lib32/libGLESv1_CM.so.1 exists in filesystem
lib32-libglvnd: /usr/lib32/libGLESv2.so exists in filesystem
lib32-libglvnd: /usr/lib32/libGLESv2.so.2 exists in filesystem
lib32-libglvnd: /usr/lib32/libGLESv2.so.2.0.0 exists in filesystem
Errors occurred, no packages were upgraded.

I checked here:
https://wiki.archlinux.org/index.php/Pa … 9.22_error

But I wonder if there's a cleaner solution to this than renaming files?

phonky

Member

Registered: 2008-12-19

Posts: 69

Re: Dependency cycle (as expected) caused by libglvnd+mesa changes

Never mind: found the solution here:
https://forum.manjaro.org/t/another-err … es/20918/4

Trilby

Inspector Parrot

Registered: 2011-11-29

Posts: 29,523

Website

Re: Dependency cycle (as expected) caused by libglvnd+mesa changes

So you're using Manjaro?  Please be sure to post your questions on their forums from now on.  These forums are for arch linux only:
https://wiki.archlinux.org/index.php/Co … .2Aonly.2A

---

"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman