pacman: "warning: dependency cycle detected"

sleepy_cat · 2017-07-06 14:29:59

When I trying to update my Arch Linux, a "warning: dependency cycle detected" message came across.

[phew ~]: sudo pacman -Syu
[sudo] password for phew:
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
warning: dependency cycle detected:
warning: systemd will be installed before its device-mapper dependency
Packages (26) boost-libs-1.64.0-3 device-mapper-2.02.172-1 fcitx-qt5-1.1.0-3 grep-3.1-1 hostapd-2.6-5 iso-codes-3.75-1 libbsd-0.8.5-1 libcups-2.2.4-1
libgcrypt-1.7.8-1 libnl-3.3.0-1 libpng-1.6.30-1 libsystemd-233-7 linux-4.11.7-1 linux-headers-4.11.7-1 lvm2-2.02.172-1 mesa-17.1.4-1
mkinitcpio-busybox-1.26.1-1 pacman-mirrorlist-20170628-1 psmisc-23.1-1 python2-2.7.13-3 qt5-base-5.9.1-2 systemd-233-7 systemd-sysvcompat-233-7
texinfo-6.4-1 unrar-1:5.5.6-1 wpa_supplicant-1:2.6-7
Total Download Size: 117.92 MiB
Total Installed Size: 377.46 MiB
Net Upgrade Size: -17.10 MiB
:: Proceed with installation? [Y/n]

I remembered that when the "Net Upgrade Size" is negative number, bad things will happen(like the libgcrypt will be corrupted, which many programs will be unusable)

So what am I gonna to do to solve the dependency cycle issue.

Thanks you guys, :-D

Last edited by sleepy_cat (2017-07-06 14:40:13)

V1del · 2017-07-06 14:36:45

Shouldn't be an issue on an existing install, however the device-mapper version has an issue on new installs, so if you want to be safe you might want to wait for your mirror to sync the 2.02.172-2 pkgrel version of device-mapper, which should also have solved that dependency conflict. A lower install net-size doesn't necessarily have to be bad though.

Last edited by V1del (2017-07-06 14:37:17)

sleepy_cat · 2017-07-06 14:41:51

V1del wrote:

Shouldn't be an issue on an existing install, however the device-mapper version has an issue on new installs, so if you want to be safe you might want to wait for your mirror to sync the 2.02.172-2 pkgrel version of device-mapper, which should also have solved that dependency conflict. A lower install net-size doesn't necessarily have to be bad though.

How long time that gonna be waiting for?

2ManyDogs · 2017-07-06 15:10:56

You can check mirror status here: https://www.archlinux.org/mirrors/status/

skeevy420 · 2017-07-06 15:41:17

I'd like to add that there are a lot of things that can result in a Negative Net Upgrade Size. For some examples of good reasons for a Negative, a GUI program optimizing its images will almost always result in a negative because it'll be shipping with smaller images, if the program had its code cleaned up or GCC has been updated, those can both result in smaller code size, and most of my programs compiled with my native architecture are smaller than the repository versions (mainly applies to AUR helper upgrades, but it's worth mentioning).

There are just too many variables involved to use the Upgrade Size as a determination of a bad or good upgrade process. It can give clues, but that's about it (like a 2 package upgrade suddenly gaining or losing multiple gigabytes of storage....something obviously isn't right about that). In my experiences, anytime there are more than 20 packages being upgraded, fluctuations of + or - 150mb are commonplace.

A Negative Net Upgrade Size in and of itself is neither good nor bad, it is what it is.

Arch Linux

#1 2017-07-06 14:29:59

pacman: "warning: dependency cycle detected"

#2 2017-07-06 14:36:45

Re: pacman: "warning: dependency cycle detected"

#3 2017-07-06 14:41:51

Re: pacman: "warning: dependency cycle detected"

#4 2017-07-06 15:10:56

Re: pacman: "warning: dependency cycle detected"

#5 2017-07-06 15:41:17

Re: pacman: "warning: dependency cycle detected"

Board footer