Fedora 33 compose report: 20200914.n.0 changes
by Fedora Rawhide Report
OLD: Fedora-33-20200913.n.0
NEW: Fedora-33-20200914.n.0
===== SUMMARY =====
Added images: 2
Dropped images: 0
Added packages: 0
Dropped packages: 0
Upgraded packages: 1
Downgraded packages: 0
Size of added packages: 0 B
Size of dropped packages: 0 B
Size of upgraded packages: 5.54 MiB
Size of downgraded packages: 0 B
Size change of upgraded packages: 1.40 KiB
Size change of downgraded packages: 0 B
===== ADDED IMAGES =====
Image: SoaS raw-xz armhfp
Path: Spins/armhfp/images/Fedora-SoaS-armhfp-33-20200914.n.0-sda.raw.xz
Image: Container_Base docker ppc64le
Path: Container/ppc64le/images/Fedora-Container-Base-33-20200914.n.0.ppc64le.tar.xz
===== DROPPED IMAGES =====
===== ADDED PACKAGES =====
===== DROPPED PACKAGES =====
===== UPGRADED PACKAGES =====
Package: gnome-initial-setup-3.38.0-2.fc33
Old package: gnome-initial-setup-3.37.91.1-2.fc33
Summary: Bootstrapping your OS
RPMs: gnome-initial-setup
Size: 5.54 MiB
Size change: 1.40 KiB
Changelog:
* Sun Sep 06 2020 Kalev Lember <klember(a)redhat.com> - 3.37.92-1
- Update to 3.37.92
- Drop upstreamed honor-firstboot-disabled.patch
* Thu Sep 10 2020 Kalev Lember <klember(a)redhat.com> - 3.38.0-1
- Update to 3.38.0
* Fri Sep 11 2020 Ray Strode <rstrode(a)redhat.com> - 3.38.0-2
- Remove weird, unnecessary g_idle_add which are triggering
some weird, not fully understood bug.
Resolves: #1875140
===== DOWNGRADED PACKAGES =====
3 years, 7 months
Enable EarlyOOM on Fedora KDE - Fedora 33 Self-Contained Change proposal
by Ben Cotton
https://fedoraproject.org/wiki/Changes/KDEEarlyOOM
== Summary ==
As [[Changes/EnableEarlyoom|Fedora Workstation did in F32]], install
earlyoom package, and enable it by default. If both RAM and swap go below
10% free, earlyoom issues SIGTERM to the process with the largest
oom_score. If both RAM and swap go below 5% free, earlyoom issues SIGKILL
to the process with the largest oom_score. The idea is to recover from out
of memory situations sooner, rather than the typical complete system hang
in which the user has no other choice but to force power off.
== Owner ==
* Name: [[User:bcotton|Ben Cotton]]
* Email: bcotton(a)redhat.com
== Detailed Description ==
Shamelessly copied from Workstation, which did it in the last release:
Certain workloads have heavy memory demands, quickly consume all of RAM,
and start to heavily page out to swap. (Heavy paging, is often called "swap
thrashing" for added descriptive effect, probably because it's noticeable
and annoying). Incidental swap usage is a good thing, it frees up memory
for active pages used by a process. Heavy swap usage quickly leads to a
very negative UX, because it's slow, even on modern SSDs. Due to installer
defaults, the swap partition is made the same size as available memory (at
install time), which can be huge. This just extends swap thrashing time.
On the one hand, we want this resource hungry job to complete. On the other
hand, we want our system to be responsive while that other work is going
on. But once the GUI stutters or even comes to an apparent stand still
(hang), we're really wishing the kernel oom-killer would kick in and free
up memory, so we can start over (maybe using memory or thread limiting
options - which arguably should be more intelligently figured out, and that
too is a work in progress but beyond the scope of this feature).
However, once in a heavy swap scenario, it's relatively common the system
gets stuck in it, where GUI interactivity is terrible to non-existent, and
also the kernel oom-killer doesn't trigger. From a certain point of view,
this is working as intended. The kernel oom-killer is concerned about
keeping the kernel running. It's not at all concerned about user space
responsiveness.
Instead of the system becoming completely unresponsive for tens of minutes,
hours or days, this feature expects that an offending process (determined
by oom_score, same as the kernel oom-killer) will be killed off within
seconds or a few minutes.
== Benefit to Fedora ==
KDE users will be able to take advantage of the benefits Workstation users
got from enabling earlyOOM in Fedora 32:
* improved user experience by more quickly regaining control over one's
system, rather than having to force power off in low-memory situations
where there's aggressive swapping. Once a system becomes unresponsive, it's
completely reasonable for the user to assume the system is lost, but that
includes high potential for data loss.
* reducing forced poweroff as the main work around will increase data
collection, improving understanding of low memory situations and how to
handle them better
* earlyoom first sends SIGTERM to the chosen process, so it has a chance of
a proper shutdown, unlike the kernel's oom-killer
== Scope ==
* Proposal owners:
** Modify {{code|
https://pagure.io/fedora-comps/blob/master/f/comps-f33.xml.in}} to include
earlyoom package for in {{code|kde-desktop}} section.
** Add {{code|
https://src.fedoraproject.org/rpms/fedora-release/blob/master/f/80-kde.pr...
to include:
<pre>
# enable earlyoom by default on KDE
enable earlyoom.service
</pre>
* Other developers: None, unless KDE-based Spins/Labs want to opt out
* Release engineering: N/A
* Policies and guidelines: N/A
* Trademark approval: N/A
== Upgrade/compatibility impact ==
earlyoom.service will be enabled on upgrade. An upgraded system should
exhibit the same behaviors as a newly-installed system.
== How To Test ==
* Fedora 31/32 KDE users can test today:
** {{code|sudo dnf install earlyoom}}
** {{code|sudo systemctl enable --now earlyoom}}
And then attempt to cause an out of memory situation. Examples:
** {{code|tail /dev/zero}}
** https://lkml.org/lkml/2019/8/4/15
== User Experience ==
earlyoom sends SIGTERM to processes based on oom_score when both memory and
swap have less than 10% free and SIGKILL when below 5%.
== Dependencies ==
None
== Contingency Plan ==
* Contingency mechanism: (What to do? Who will do it?) Owner reverts
changes
* Contingency deadline: Final freeze
* Blocks release? No
== Documentation ==
* {{code|man earlyoom}}
* https://github.com/rfjakob/earlyoom
* https://www.kernel.org/doc/gorman/html/understand/understand016.html
== Release Notes ==
The earlyoom service is now enabled by default in Fedora KDE.
The earlyoom service monitors system memory usage. If free memory falls
below a set limit, earlyoom terminates an appropriate process to free up
memory. As a result, the system does not become unresponsive for long
periods of time in low-memory situations.
The following is the default earlyoom configuration:
* If both RAM and swap go below 10% free, earlyoom sends the SIGTERM signal
to the process with the largest oom_score.
* If both RAM and swap go below 5% free, earlyoom sends the SIGKILL signal
to the process with the largest oom_score.
For more information, see the earlyoom man page.
--
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
3 years, 7 months
Is there a Qt5 rebuild in progress?
by Miro Hrončok
Hello,
dozens of my packages suddenly fail to resolve build dependencies with things
like the ones below.
Is there a Qt5 rebuild in progress?
This build seem to be tagged in a side tag and also in f34:
https://koji.fedoraproject.org/koji/buildinfo?buildID=1608618
Is that on purpose?
------------------------
Problem: package qt5-qtscript-devel-5.14.2-4.fc33.x86_64 requires
qt5-qtscript(x86-64) = 5.14.2-4.fc33, but none of the providers can be installed
- package qt5-qtscript-devel-5.14.2-4.fc33.x86_64 requires
libQt5Script.so.5()(64bit), but none of the providers can be installed
- package qt5-qtscript-devel-5.14.2-4.fc33.x86_64 requires
libQt5ScriptTools.so.5()(64bit), but none of the providers can be installed
- conflicting requests
- nothing provides libQt5Core.so.5(Qt_5.14.2_PRIVATE_API)(64bit) needed by
qt5-qtscript-5.14.2-4.fc33.x86_64
- nothing provides libQt5Widgets.so.5(Qt_5.14.2_PRIVATE_API)(64bit) needed by
qt5-qtscript-5.14.2-4.fc33.x86_64
- nothing provides qt5-qtbase(x86-64) = 5.14.2 needed by
qt5-qtscript-5.14.2-4.fc33.x86_64
Problem: package qt5-qtxmlpatterns-devel-5.14.2-3.fc33.x86_64 requires
qt5-qtxmlpatterns(x86-64) = 5.14.2-3.fc33, but none of the providers can be
installed
- package qt5-qtxmlpatterns-devel-5.14.2-3.fc33.x86_64 requires
libQt5XmlPatterns.so.5()(64bit), but none of the providers can be installed
- package qt5-qtxmlpatterns-devel-5.14.2-3.fc33.x86_64 requires
libQt5XmlPatterns.so.5(Qt_5)(64bit), but none of the providers can be installed
- conflicting requests
- nothing provides libQt5Core.so.5(Qt_5.14.2_PRIVATE_API)(64bit) needed by
qt5-qtxmlpatterns-5.14.2-3.fc33.x86_64
- nothing provides libQt5Qml.so.5(Qt_5.14.2_PRIVATE_API)(64bit) needed by
qt5-qtxmlpatterns-5.14.2-3.fc33.x86_64
- nothing provides qt5-qtbase(x86-64) = 5.14.2 needed by
qt5-qtxmlpatterns-5.14.2-3.fc33.x86_64
Problem: conflicting requests
- nothing provides libQt5Gui.so.5(Qt_5.14.2_PRIVATE_API)(64bit) needed by
qt5-qttools-devel-5.14.2-3.fc33.x86_64
Problem: package pcl-devel-1.11.0-4.fc33.x86_64 requires vtk-devel, but none of
the providers can be installed
- package vtk-devel-8.2.0-23.fc34.x86_64 requires cmake(Qt5UiPlugin), but none
of the providers can be installed
- conflicting requests
- nothing provides libQt5Gui.so.5(Qt_5.14.2_PRIVATE_API)(64bit) needed by
qt5-qttools-devel-5.14.2-3.fc33.x86_64
Problem: package qt5-qtsvg-devel-5.14.2-3.fc33.x86_64 requires qt5-qtsvg(x86-64)
= 5.14.2-3.fc33, but none of the providers can be installed
- package qt5-qtsvg-devel-5.14.2-3.fc33.x86_64 requires libQt5Svg.so.5()(64bit),
but none of the providers can be installed
- conflicting requests
- nothing provides libQt5Gui.so.5(Qt_5.14.2_PRIVATE_API)(64bit) needed by
qt5-qtsvg-5.14.2-3.fc33.x86_64
- nothing provides libQt5Core.so.5(Qt_5.14.2_PRIVATE_API)(64bit) needed by
qt5-qtsvg-5.14.2-3.fc33.x86_64
- nothing provides libQt5Widgets.so.5(Qt_5.14.2_PRIVATE_API)(64bit) needed by
qt5-qtsvg-5.14.2-3.fc33.x86_64
- nothing provides qt5-qtbase(x86-64) = 5.14.2 needed by
qt5-qtsvg-5.14.2-3.fc33.x86_64
Problem: package qt5-qttools-static-5.14.2-3.fc33.x86_64 requires
qt5-qttools-devel(x86-64) = 5.14.2-3.fc33, but none of the providers can be
installed
- conflicting requests
- nothing provides libQt5Gui.so.5(Qt_5.14.2_PRIVATE_API)(64bit) needed by
qt5-qttools-devel-5.14.2-3.fc33.x86_64
Problem: package qt5-qtxmlpatterns-devel-5.14.2-3.fc33.x86_64 requires
qt5-qtxmlpatterns(x86-64) = 5.14.2-3.fc33, but none of the providers can be
installed
- package qt5-qtxmlpatterns-devel-5.14.2-3.fc33.x86_64 requires
libQt5XmlPatterns.so.5()(64bit), but none of the providers can be installed
- package qt5-qtxmlpatterns-devel-5.14.2-3.fc33.x86_64 requires
libQt5XmlPatterns.so.5(Qt_5)(64bit), but none of the providers can be installed
- conflicting requests
- nothing provides libQt5Core.so.5(Qt_5.14.2_PRIVATE_API)(64bit) needed by
qt5-qtxmlpatterns-5.14.2-3.fc33.x86_64
- nothing provides libQt5Qml.so.5(Qt_5.14.2_PRIVATE_API)(64bit) needed by
qt5-qtxmlpatterns-5.14.2-3.fc33.x86_64
- nothing provides qt5-qtbase(x86-64) = 5.14.2 needed by
qt5-qtxmlpatterns-5.14.2-3.fc33.x86_64
Problem: package qt5-qtgamepad-devel-5.14.2-3.fc33.x86_64 requires
libQt5Gamepad.so.5()(64bit), but none of the providers can be installed
- package qt5-qtgamepad-devel-5.14.2-3.fc33.x86_64 requires
qt5-qtgamepad(x86-64) = 5.14.2-3.fc33, but none of the providers can be installed
- conflicting requests
- nothing provides libQt5Core.so.5(Qt_5.14.2_PRIVATE_API)(64bit) needed by
qt5-qtgamepad-5.14.2-3.fc33.x86_64
- nothing provides qt5-qtbase(x86-64) = 5.14.2 needed by
qt5-qtgamepad-5.14.2-3.fc33.x86_64
Problem: package qt5-qtmultimedia-devel-5.14.2-3.fc33.x86_64 requires
libQt5Multimedia.so.5()(64bit), but none of the providers can be installed
- package qt5-qtmultimedia-devel-5.14.2-3.fc33.x86_64 requires
libQt5MultimediaWidgets.so.5()(64bit), but none of the providers can be installed
- package qt5-qtmultimedia-devel-5.14.2-3.fc33.x86_64 requires
libQt5MultimediaGstTools.so.5()(64bit), but none of the providers can be installed
- package qt5-qtmultimedia-devel-5.14.2-3.fc33.x86_64 requires
libQt5MultimediaQuick.so.5()(64bit), but none of the providers can be installed
- package qt5-qtmultimedia-devel-5.14.2-3.fc33.x86_64 requires
qt5-qtmultimedia(x86-64) = 5.14.2-3.fc33, but none of the providers can be installed
- conflicting requests
- nothing provides libQt5Gui.so.5(Qt_5.14.2_PRIVATE_API)(64bit) needed by
qt5-qtmultimedia-5.14.2-3.fc33.x86_64
- nothing provides libQt5Core.so.5(Qt_5.14.2_PRIVATE_API)(64bit) needed by
qt5-qtmultimedia-5.14.2-3.fc33.x86_64
- nothing provides qt5-qtbase(x86-64) = 5.14.2 needed by
qt5-qtmultimedia-5.14.2-3.fc33.x86_64
Problem: package python3-uranium-4.7.1-1.fc34.noarch requires python3-qt5, but
none of the providers can be installed
- conflicting requests
- nothing provides libQt5Core.so.5(Qt_5.15)(64bit) needed by
python3-qt5-5.15.0-2.fc34.x86_64
- nothing provides libQt5Quick.so.5(Qt_5.15.1_PRIVATE_API)(64bit) needed by
python3-qt5-5.15.0-2.fc34.x86_64
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
3 years, 7 months
F32 -> F33 upgrade
by Marcin Juszkiewicz
I assume that there will be a proper thread for testing such upgrade
some time after Beta point but I had some time today I checked will it
work.
On my system it looks like deja-dup/duply/duplicity have a problem with
dependencies:
[root@puchatek ~]# LANGUAGE=C dnf distrosync --releasever 33
Last metadata expiration check: 0:18:13 ago on nie, 13 wrz 2020, 13:50:13.
Error:
Problem 1: problem with installed package python3-google-api-client-1:1.6.7-11.fc32.noarch
- python3-google-api-client-1:1.6.7-11.fc32.noarch does not belong to a distupgrade repository
- nothing provides python3-google-api-core >= 1.18.0 needed by python3-google-api-client-1:1.10.0-2.fc33.noarch
Problem 2: package duplicity-0.8.15-2.fc33.x86_64 requires python3-PyDrive, but none of the providers can be installed
- problem with installed package duplicity-0.8.15-2.fc32.x86_64
- package python3-PyDrive-1.3.1-13.fc33.noarch requires python3.9dist(google-api-python-client) >= 1.2, but none of the providers can be installed
- python3-PyDrive-1.3.1-12.fc32.noarch does not belong to a distupgrade repository
- duplicity-0.8.15-2.fc32.x86_64 does not belong to a distupgrade repository
- nothing provides python3-google-api-core >= 1.18.0 needed by python3-google-api-client-1:1.10.0-2.fc33.noarch
Problem 3: problem with installed package python3-PyDrive-1.3.1-12.fc32.noarch
- package python3-PyDrive-1.3.1-12.fc32.noarch requires python(abi) = 3.8, but none of the providers can be installed
- package python3-PyDrive-1.3.1-13.fc33.noarch requires python3.9dist(google-api-python-client) >= 1.2, but none of the providers can be installed
- python3-3.8.5-5.fc32.x86_64 does not belong to a distupgrade repository
- nothing provides python3-google-api-core >= 1.18.0 needed by python3-google-api-client-1:1.10.0-2.fc33.noarch
Problem 4: package duply-2.2.2-2.fc33.noarch requires duplicity, but none of the providers can be installed
- package duplicity-0.8.15-2.fc33.x86_64 requires python3-PyDrive, but none of the providers can be installed
- package duplicity-0.8.15-2.fc32.x86_64 requires python(abi) = 3.8, but none of the providers can be installed
- package python3-PyDrive-1.3.1-12.fc32.noarch requires python3.8dist(oauth2client) >= 4, but none of the providers can be installed
- package python3-3.8.5-5.fc32.x86_64 requires python3-libs(x86-64) = 3.8.5-5.fc32, but none of the providers can be installed
- problem with installed package duply-2.2.2-1.fc32.noarch
- package python3-PyDrive-1.3.1-13.fc33.noarch requires python3.9dist(google-api-python-client) >= 1.2, but none of the providers can be installed
- python3-oauth2client-4.1.3-10.fc32.noarch does not belong to a distupgrade repository
- python3-libs-3.8.5-5.fc32.x86_64 does not belong to a distupgrade repository
- duply-2.2.2-1.fc32.noarch does not belong to a distupgrade repository
- nothing provides python3-google-api-core >= 1.18.0 needed by python3-google-api-client-1:1.10.0-2.fc33.noarch
Problem 5: package deja-dup-42.2-1.fc33.x86_64 requires duplicity >= 0.6.23, but none of the providers can be installed
- package duplicity-0.8.15-2.fc32.x86_64 requires python3-PyDrive, but none of the providers can be installed
- package duplicity-0.8.15-2.fc33.x86_64 requires python3-PyDrive, but none of the providers can be installed
- package python3-PyDrive-1.3.1-12.fc32.noarch requires python3.8dist(pyyaml) >= 3, but none of the providers can be installed
- problem with installed package deja-dup-42.2-1.fc32.x86_64
- package python3-PyDrive-1.3.1-13.fc33.noarch requires python3.9dist(google-api-python-client) >= 1.2, but none of the providers can be installed
- python3-pyyaml-5.3.1-1.fc32.x86_64 does not belong to a distupgrade repository
- deja-dup-42.2-1.fc32.x86_64 does not belong to a distupgrade repository
- nothing provides python3-google-api-core >= 1.18.0 needed by python3-google-api-client-1:1.10.0-2.fc33.noarch
(try to add '--skip-broken' to skip uninstallable packages)
[root@puchatek ~]#
3 years, 7 months