You are not logged in.
Just activated the multilib repositories. After that i tried to to install Infinality Bundle for 32-bit but confronted with a dependency cycle warning. What is this?:
# pacman -S infinality-bundle-multilib
:: There are 3 members in group infinality-bundle-multilib:
:: Repository infinality-bundle-multilib
1) lib32-cairo-infinality-ultimate 2) lib32-fontconfig-infinality-ultimate
3) lib32-freetype2-infinality-ultimate
Enter a selection (default=all): 3
resolving dependencies...
looking for conflicting packages...warning: dependency cycle detected:
warning: lib32-harfbuzz will be installed before its lib32-freetype2-infinality-ultimate dependency
Packages (13) lib32-bzip2-1.0.6-2 lib32-expat-2.1.0-2 lib32-gcc-libs-4.9.2-3
lib32-glib2-2.42.1-1 lib32-glibc-2.21-2 lib32-harfbuzz-0.9.38-1 lib32-icu-54.1-1
lib32-libdbus-1.8.16-1 lib32-libffi-3.2.1-1 lib32-libpng-1.6.16-1
lib32-pcre-8.36-1 lib32-zlib-1.2.8-1 lib32-freetype2-infinality-ultimate-2.5.5-2
Total Download Size: 14.17 MiB
Total Installed Size: 58.59 MiB
:: Proceed with installation? [Y/n] Last edited by Paingiver (2015-03-01 14:48:14)
Offline
Not a Pacman issue, moving to AUR Issues...
Offline
It's a true dependency cycle. Don't worry about it.
Offline
It's a true dependency cycle. Don't worry about it.
True dependency cycle? What does that means?
Offline
True dependency cycle? What does that means?
It means that these two packages, directly or indirectly, are mutually dependent. Normally pacman installs dependencies of packages before the package itself, but this creates a catch-22 when packages depend on each other. In these cases, pacman is allowed to temporarily ignore (--assume-installed) one of the mutually dependent packages to install the other, as long as it is sure that both of them can be installed within the same pacman invocation. At least that's my understanding.
Offline
Paingiver wrote:True dependency cycle? What does that means?
It means that these two packages, directly or indirectly, are mutually dependent. Normally pacman installs dependencies of packages before the package itself, but this creates a catch-22 when packages depend on each other. In these cases, pacman is allowed to temporarily ignore (--assume-installed) one of the mutually dependent packages to install the other, as long as it is sure that both of them can be installed within the same pacman invocation. At least that's my understanding.
Great explanation. thanks. Marking as solved.
Offline