I tried to upgrade to this update using Koji, and I got the following dnf problems
Problem 1: cannot install the best update candidate for package gimp-2:2.10.6-2.fc29.i686 - nothing provides /usr/bin/python22 needed by gimp-2:2.10.8-4.fc29.i686 Problem 2: problem with installed package gimp-2:2.10.6-2.fc29.i686 - package gimp-2:2.10.6-2.fc29.i686 requires gimp-libs(x86-32) = 2:2.10.6-2.fc29, but none of the providers can be installed - cannot install both gimp-libs-2:2.10.8-4.fc29.i686 and gimp-libs-2:2.10.6-2.fc29.i686 - cannot install the best update candidate for package gimp-libs-2:2.10.6-2.fc29.i686 - package gimp-2:2.10.6-2.module_2129+8576126a.i686 is excluded - nothing provides /usr/bin/python22 needed by gimp-2:2.10.8-4.fc29.i686
gimp-2:2.10.8-4.fc29 requires /usr/bin/python22 which gimp-2.10.6-2 didn't. /usr/bin/python22 isn't provided by anything in F29. sudo dnf repoquery --whatprovides /usr/bin/python22 returns nothing.
I haven't seen any denials since upgrading to 3.14.2-42 a day ago.
4.18.17 has run fine. I deleted the rescue kernel recently because it hadn't been updated since I installed Fedora and ran grub2-mkconfig. A rescue kernel was generated when I installed 4.18.17, and that rescue kernel was added as the first line of the the grub menu. The old rescue kernel was listed after the regular kernels in grub.
I upgraded to lmdb-libs 0.9.22-4.fc29 and its debug packages from Koji yesterday. I haven't seen any baloo_file crashes after running several sessions of Plasma with baloo_file autostarted for longer than 30 minutes by which baloo_file usually would have crashed before. Thanks for the update.
I haven't seen the denial of systemd-user-ru from reading dbus-1 I reported in #1644313 or any others since upgrading to 3.14.2-41. Thanks.
60.3.0 has run normally except when it was first started when logged in with a secondary user about 20 tabs opened for individual language packs asking if each language pack should be enabled. I reported more details about that issue at https://bugzilla.redhat.com/show_bug.cgi?id=1645360
Plasma, dolphin, konsole, kinfocenter, kate and other KDE applications have run normally with KF5 5.51.0. baloo_file 5.51.0 crashed twice due to a failed assertion rc == 0 in mdb_page_dirty at mdb.c:2127-2128 in liblmdb.so.0.0.0 in the lmdb-libs package. I've seen baloo_file crash many times with previous KF5 versions as have many others so the crash isn't specific to 5.51.0. I mentioned in the report I filed about a fix for lmdb-libs which might resolve those crashes. https://bugzilla.redhat.com/show_bug.cgi?id=1645114
I'm unsure if #1645114 should be reassigned from kf5-baloo to lmdb.
@vondruch This update and the others submitted in the last 5 days for F29 still have pending status. I was updating ruby and other packages from Koji since those updates haven't been pushed to updates-testing. My previous comment was just to inform the maintainers that they might consider increasing the release of rubygem-json and version of rubygem-rdoc if those subpackages were intended to be upgraded with the rest of this update.
I upgraded to systemd-239-6.git9f3aed1.fc29 from Koji. When I logged into Plasma twice after the systemd update, I saw the following denial of systemd-user-ru reading dbus-1 both times. I put the details in the report at https://bugzilla.redhat.com/show_bug.cgi?id=1644313 systemd seems to be running normally otherwise.
When I ran sudo dnf upgrade on this update's rpms from Koji I got the following messages Package rubygem-json of higher version already installed, cannot update it. Package rubygem-rdoc of higher version already installed, cannot update it.
rubygem-json-2.1.0-99.fc29 in this update has a lower release than rubygem-json-2.1.0-106.fc29 which I have installed. https://koji.fedoraproject.org/koji/buildinfo?buildID=1124292
rubygem-rdoc-6.0.1-99.fc29 in this update has a lower version than rubygem-rdoc-6.0.3-3.fc29 which I have installed. https://koji.fedoraproject.org/koji/buildinfo?buildID=1124463
63 has run normally.
4.18.16 has run normally.
4.18.15 has run normally.
I installed scap-workbench-1.2.0-2 without getting the error I noted in #1640283. I ran the Standard System Security Profile for Fedora scan in scap-workbench-1.2.0-2 which completed though some errors related to a directory something like /tmp/openscap not being found occurred. Thanks.
The crashes I reported in #1638767 and #1638784 haven't happened with 3.30.3 from Koji. 3.30.3 has run normally otherwise.
Running sudo dnf upgrade --refresh I got the following errors
Problem 1: cannot install both unbound-libs-1.7.3-9.fc29.i686 and unbound-libs-1.8.1-1.fc29.i686 - package gnutls-dane-3.6.4-3.fc29.i686 requires libunbound.so.2, but none of the providers can be installed - cannot install the best update candidate for package unbound-libs-1.8.1-1.fc29.i686 - cannot install the best update candidate for package gnutls-dane-3.6.4-2.fc29.i686 Problem 2: package unbound-1.8.1-1.fc29.i686 requires libunbound.so.8, but none of the providers can be installed - package unbound-1.8.1-1.fc29.i686 requires unbound-libs(x86-32) = 1.8.1-1.fc29, but none of the providers can be installed - cannot install both unbound-libs-1.7.3-9.fc29.i686 and unbound-libs-1.8.1-1.fc29.i686 - package gnutls-dane-3.6.4-3.fc29.i686 requires libunbound.so.2, but none of the providers can be installed - package gnutls-devel-3.6.4-3.fc29.i686 requires gnutls-dane(x86-32) = 3.6.4-3.fc29, but none of the providers can be installed - cannot install the best update candidate for package unbound-1.8.1-1.fc29.i686 - cannot install the best update candidate for package gnutls-devel-3.6.4-2.fc29.i686 Problem 3: package python3-unbound-1.8.1-1.fc29.i686 requires libunbound.so.8, but none of the providers can be installed - package python3-unbound-1.8.1-1.fc29.i686 requires unbound-libs(x86-32) = 1.8.1-1.fc29, but none of the providers can be installed - cannot install both unbound-libs-1.7.3-9.fc29.i686 and unbound-libs-1.8.1-1.fc29.i686 - package gnutls-dane-3.6.4-3.fc29.i686 requires libunbound.so.2, but none of the providers can be installed - package gnutls-utils-3.6.4-3.fc29.i686 requires gnutls-dane(x86-32) = 3.6.4-3.fc29, but none of the providers can be installed - cannot install the best update candidate for package python3-unbound-1.8.1-1.fc29.i686 - cannot install the best update candidate for package gnutls-utils-3.6.4-2.fc29.i686 Problem 4: package python2-unbound-1.8.1-1.fc29.i686 requires libunbound.so.8, but none of the providers can be installed - package python2-unbound-1.8.1-1.fc29.i686 requires unbound-libs(x86-32) = 1.8.1-1.fc29, but none of the providers can be installed - cannot install both unbound-libs-1.7.3-9.fc29.i686 and unbound-libs-1.8.1-1.fc29.i686 - package gnutls-dane-3.6.4-3.fc29.i686 requires libunbound.so.2, but none of the providers can be installed - package gnutls-utils-3.6.4-3.fc29.i686 requires libgnutls-dane.so.0, but none of the providers can be installed - package gnutls-utils-3.6.4-3.fc29.i686 requires libgnutls-dane.so.0(DANE_0_0), but none of the providers can be installed - package libvirt-client-4.7.0-1.fc29.i686 requires gnutls-utils, but none of the providers can be installed - package gnutls-dane-3.6.4-2.fc29.i686 requires gnutls(x86-32) = 3.6.4-2.fc29, but none of the providers can be installed - package gnutls-utils-3.6.4-2.fc29.i686 requires gnutls(x86-32) = 3.6.4-2.fc29, but none of the providers can be installed - package gnutls-dane-3.6.4-1.fc29.i686 requires gnutls(x86-32) = 3.6.4-1.fc29, but none of the providers can be installed - package gnutls-utils-3.6.4-1.fc29.i686 requires gnutls(x86-32) = 3.6.4-1.fc29, but none of the providers can be installed - cannot install both gnutls-3.6.4-3.fc29.i686 and gnutls-3.6.4-2.fc29.i686 - cannot install both gnutls-3.6.4-1.fc29.i686 and gnutls-3.6.4-3.fc29.i686 - cannot install the best update candidate for package python2-unbound-1.8.1-1.fc29.i686 - cannot install the best update candidate for package libvirt-client-4.7.0-1.fc29.i686 - cannot install the best update candidate for package gnutls-3.6.4-2.fc29.i686 Problem 5: package libreswan-3.27-1.fc29.i686 requires libunbound.so.8, but none of the providers can be installed - cannot install both unbound-libs-1.7.3-9.fc29.i686 and unbound-libs-1.8.1-1.fc29.i686 - package gnutls-dane-3.6.4-3.fc29.i686 requires libunbound.so.2, but none of the providers can be installed - package gnutls-devel-3.6.4-3.fc29.i686 requires gnutls-dane(x86-32) = 3.6.4-3.fc29, but none of the providers can be installed - package openvas-libraries-devel-9.0.2-3.fc29.i686 requires pkgconfig(gnutls) >= 2.12, but none of the providers can be installed - package gnutls-devel-3.6.4-2.fc29.i686 requires gnutls-c++(x86-32) = 3.6.4-2.fc29, but none of the providers can be installed - package gnutls-devel-3.6.4-1.fc29.i686 requires gnutls-c++(x86-32) = 3.6.4-1.fc29, but none of the providers can be installed - cannot install both gnutls-c++-3.6.4-3.fc29.i686 and gnutls-c++-3.6.4-2.fc29.i686 - cannot install both gnutls-c++-3.6.4-1.fc29.i686 and gnutls-c++-3.6.4-3.fc29.i686 - cannot install the best update candidate for package openvas-libraries-devel-9.0.2-3.fc29.i686 - cannot install the best update candidate for package libreswan-3.27-1.fc29.i686 - cannot install the best update candidate for package gnutls-c++-3.6.4-2.fc29.i686 ...
Skipping packages with conflicts: (add '--best --allowerasing' to command line to force their upgrade): gnutls i686 3.6.4-1.fc29 fedora 870 k gnutls i686 3.6.4-3.fc29 updates-testing 871 k gnutls-c++ i686 3.6.4-1.fc29 fedora 27 k gnutls-c++ i686 3.6.4-3.fc29 updates-testing 27 k unbound-libs i686 1.7.3-9.fc29 fedora 489 k Skipping packages with broken dependencies: gnutls-dane i686 3.6.4-1.fc29 fedora 25 k gnutls-dane i686 3.6.4-3.fc29 updates-testing 25 k gnutls-devel i686 3.6.4-1.fc29 fedora 2.1 M gnutls-devel i686 3.6.4-3.fc29 updates-testing 2.1 M gnutls-utils i686 3.6.4-1.fc29 fedora 299 k gnutls-utils i686 3.6.4-3.fc29 updates-testing 299 k
gnutls-dane-3.6.4-3 requires libunbound.so.2 but unbound-libs-1.8.1-1 in updates-testing provides libunbound.so.8 Rebuilding gnutls to use libunbound.so.8 from unbound-libs-1.8.1-1 as was done in gnutls-3.6.4-2.fc29 at FEDORA-2018-7be27ff1d8 and adding it to that update might resolve at least some of the errors.
I downgraded from the 1.3.0 rpms I built to 1.3.0_alpha2-2. Then, I upgraded to 1:1.3.0-3 from Koji without any errors. Thanks for the update.
When I wrote %{name} followed by the * operator, the text after * showed up as italicized unintentionally. I just changed all the Requires lines involving openscap packages to include %{epoch} including those of the following form: Requires: %{name}%{?_isa} = %{epoch}:%{version}-%{release} Requires: %{name}-scanner%{?_isa} = %{epoch}:%{version}-%{release} Requires: %{name}-devel%{?_isa} = %{epoch}:%{version}-%{release} Requires: %{name}-engine-sce%{?_isa} = %{epoch}:%{version}-%{release} Requires: %{name} = %{epoch}:%{version}-%{release}
@jcerny I downloaded the openscap git repo with fedpkg clone openscap --branch f29 -a . I installed thsoe build requirements in openscap.spec I didn't already have. I changed change all of the Requires lines in openscap.spec matching Requires: %{name} = %{version}-%{release} to Requires: %{name}= %{epoch}:%{version}-%{release}. I built the openscap packages using fedpkg --release f29 local which showed many gcc warnings, but the packages were all built correctly. I used sudo dnf upgrade on the packages I built, and they upgraded without any errors. I could provide more information if that would help.
gimp-2.10.8-1.fc29 didn't require /usr/bin/python22 while gimp-2.10.8-2.fc29 and later required /usr/bin/python22. The commit titled "use versionized Python interpreter path" might be related to the requirement of /usr/bin/python22 https://src.fedoraproject.org/rpms/gimp/c/0e386fde5050bd3c136079df817a1bf9008cb8c3?branch=f29
Replacing the requirement on /usr/bin/python22 with /usr/bin/python2.7 or removing it might resolve the dnf problems.