You are not logged in.

#1 2020-05-19 15:40:54

JeanLucJ
Member
Registered: 2019-03-08
Posts: 45

[Solved] Two depency cycles in less than a week

Hello,

Last week, while upgrading, I had a warning about a depency cycle between freetype2 and lib32-freetype2, though both where in the list of packages to be upgraded though pacman -Syu.
I fixed that by upgrading freetype2 only by hand, then lib32-freetype2, pacman -Syu did work with no error afterwards for 5-6 days

Today, I have the same exact situation with two other paquets :

warning: dependency cycle detected:
warning: eglexternalplatform will be installed before its egl-wayland dependency

even though they both seem ready to update :

  GNU nano 4.9.2                                                                                                                     logup                                                                                                                              
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...

Packages (180) apr-1.7.0-3  apr-util-1.6.1-7  aspell-0.60.8-2  atkmm-2.28.0-2  blas-3.9.0-3  cairomm-1.12.2-4  cdparanoia-10.2-8  celt0.5.1-0.5.1.3-5  cups-pk-helper-0.2.6-4  djvulibre-3.5.27-6  dotconf-1.3-6  egl-wayland-1.1.4-3  eglexternalplatform-1.1-2  [... long list of other paquets]

Since I use arch for more than two years now, have not seen that warning yet, I may have broke something, though I am at a loss where.
Wiki/google search of this error suggests that one dependency is more up to date than the main paquet, but egl-wayland-1.1.4-3  eglexternalplatform-1.1-2 are the latest version according to a package search, and they were compiled by the same maintener, at almost the same time...

Could you please point me in the right direction?
Or is it something very minor that can be safely ignored?

Thanks!

Last edited by JeanLucJ (2020-05-20 07:55:31)

Offline

#2 2020-05-19 15:43:29

loqs
Member
Registered: 2014-03-06
Posts: 10,644

Re: [Solved] Two depency cycles in less than a week

It can be ignored.

Offline

#3 2020-05-19 15:49:50

JeanLucJ
Member
Registered: 2019-03-08
Posts: 45

Re: [Solved] Two depency cycles in less than a week

loqs wrote:

It can be ignored.

Thanks for the answer.
Because I'm curious : Any idea why I would have two warnings in a week, for the first time, after 2 years with no such warning?

Offline

#4 2020-05-19 16:07:27

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 9,708
Website

Re: [Solved] Two depency cycles in less than a week

Please post the output of

pacman -Qi eglexternalplatform egl-wayland

Sakura:-
Mobo: MSI X299 TOMAHAWK ARCTIC // Processor: Intel Core i7-7820X 3.6GHz // GFX: nVidia GeForce GTX 970 // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 5x 1TB HDD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

#5 2020-05-19 16:16:10

JeanLucJ
Member
Registered: 2019-03-08
Posts: 45

Re: [Solved] Two depency cycles in less than a week

WorMzy wrote:

Please post the output of

pacman -Qi eglexternalplatform egl-wayland
Name            : eglexternalplatform
Version         : 1.1-1
Description     : EGL External Platform interface
Architecture    : any
URL             : https://github.com/NVIDIA/eglexternalplatform
Licenses        : MIT
Groups          : None
Provides        : None
Depends On      : libegl
Optional Deps   : None
Required By     : egl-wayland
Optional For    : None
Conflicts With  : None
Replaces        : None
Installed Size  : 17.33 KiB
Packager        : Jan Alexander Steffens (heftig) <jan.steffens@gmail.com>
Build Date      : Sat Nov 23 18:37:40 2019
Install Date    : Sun Nov 24 09:05:47 2019
Install Reason  : Installed as a dependency for another package
Install Script  : No
Validated By    : Signature

Name            : egl-wayland
Version         : 1.1.4-2
Description     : EGLStream-based Wayland external platform
Architecture    : x86_64
URL             : https://github.com/NVIDIA/egl-wayland
Licenses        : MIT
Groups          : None
Provides        : None
Depends On      : wayland  eglexternalplatform
Optional Deps   : None
Required By     : nvidia-utils
Optional For    : None
Conflicts With  : None
Replaces        : None
Installed Size  : 60.92 KiB
Packager        : Jan Alexander Steffens (heftig) <jan.steffens@gmail.com>
Build Date      : Sat Nov 23 18:44:05 2019
Install Date    : Sun Nov 24 09:05:47 2019
Install Reason  : Installed as a dependency for another package
Install Script  : No
Validated By    : Signature

BTW I do full sys upgrade on a daily basis

Offline

#6 2020-05-19 16:31:28

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 9,708
Website

Re: [Solved] Two depency cycles in less than a week

So you're not running the latest versions. I'm also not seeing this cyclic dependency on my system -- eglexternalplatform's dependency tree doesn't contain egl-wayland.

Please run

# pacman -Syu --debug 2>&1 | tee /tmp/pacman-debug.log

and upload the resultant file to a pastebin.


Sakura:-
Mobo: MSI X299 TOMAHAWK ARCTIC // Processor: Intel Core i7-7820X 3.6GHz // GFX: nVidia GeForce GTX 970 // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 5x 1TB HDD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

#7 2020-05-19 16:41:46

JeanLucJ
Member
Registered: 2019-03-08
Posts: 45

Re: [Solved] Two depency cycles in less than a week

I have updated my system since loqs said it was pretty harmless.

Will that command still ouput something usefull?

Last edited by JeanLucJ (2020-05-19 17:30:13)

Offline

#8 2020-05-19 18:30:00

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 23,479
Website

Re: [Solved] Two depency cycles in less than a week

JeanLucJ wrote:

I fixed that by upgrading freetype2 only by hand, then lib32-freetype2

No, that didn't fix anything, because it wasn't broken.  You did, however, temporarily break quite a bit with a partial upgrade.  You apparently resolved this quickly with a proper upgrade, so it was no concern.  But none of this was necessary.

If the initial full system upgrade failed for some reason, you'd have to actually tell us what that reason was - it was not the dependency cycle.


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

Offline

#9 2020-05-19 19:05:47

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 9,708
Website

Re: [Solved] Two depency cycles in less than a week

JeanLucJ wrote:

I have updated my system since loqs said it was pretty harmless.

Will that command still ouput something usefull?

No, but I've figured out where that cyclic dependency is:

eglexternalplatform -> libglvnd (libegl) -> nvidia-utils (opengl-driver) -> egl-wayland -> eglexternalplatform

This cycle was introduced by this commit] changing eglexternalplatform's dependency from 'mesa' to the virtual 'libegl' dependency. The reason you're seeing it now is because that commit wasn't ever included in a package release until the pkgrel was bumped three days ago.

Last edited by WorMzy (2020-05-19 19:06:21)


Sakura:-
Mobo: MSI X299 TOMAHAWK ARCTIC // Processor: Intel Core i7-7820X 3.6GHz // GFX: nVidia GeForce GTX 970 // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 5x 1TB HDD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

#10 2020-05-20 07:55:17

JeanLucJ
Member
Registered: 2019-03-08
Posts: 45

Re: [Solved] Two depency cycles in less than a week

WorMzy wrote:
JeanLucJ wrote:

I have updated my system since loqs said it was pretty harmless.

Will that command still ouput something usefull?

No, but I've figured out where that cyclic dependency is:

eglexternalplatform -> libglvnd (libegl) -> nvidia-utils (opengl-driver) -> egl-wayland -> eglexternalplatform

This cycle was introduced by this commit] changing eglexternalplatform's dependency from 'mesa' to the virtual 'libegl' dependency. The reason you're seeing it now is because that commit wasn't ever included in a package release until the pkgrel was bumped three days ago.

Thanks.

So it seems it's not related to me, and I had two dependancies cycles in a very short time by pure chance.

Regards,

Offline

Board footer

Powered by FluxBB