Created attachment 1490325 [details] output of dnf module list Description of problem: F29 Workstation as well on Server. Issuing "dnf update" on a fresh install I get no errors. An immediately subsequent update lead to $ sudo dnf update Last metadata expiration check: 0:04:13 ago on Wed 03 Oct 2018 11:34:54 PM CEST. Dependencies resolved. Problem 1: cannot install the best update candidate for package libnghttp2-1.33.0-1.fc29.x86_64 - package libnghttp2-1.33.0-1.module_2177+2526c218.x86_64 is excluded Problem 2: cannot install the best update candidate for package libpeas-1.22.0-9.fc29.x86_64 - package libpeas-1.22.0-9.module_2123+73a9ef6f.x86_64 is excluded Problem 3: cannot install the best update candidate for package libpeas-gtk-1.22.0-9.fc29.x86_64 - package libpeas-gtk-1.22.0-9.module_2123+73a9ef6f.x86_64 is excluded Problem 4: cannot install the best update candidate for package libpeas-loader-python3-1.22.0-9.fc29.x86_64 - package libpeas-loader-python3-1.22.0-9.module_2123+73a9ef6f.x86_64 is excluded Problem 5: cannot install the best update candidate for package perl-HTTP-Tiny-0.076-1.fc29.noarch - package perl-HTTP-Tiny-0.076-1.module_2073+eebc5b71.noarch is excluded Nothing to do. Complete! Version-Release number of selected component (if applicable): dnf-3.6.1-1.fc29.noarch libsolv-0.6.35-3.fc29.x86_64 I've attached the output of "dnf module list"
Created attachment 1490326 [details] debugdata directory This tar contains the debugdata directory produced by the "dnf update --debugsolver" command
I believe that this is a duplicate of 1616118 *** This bug has been marked as a duplicate of bug 1616118 ***