Fedora minimum hardware requirements
by Chris Murphy
Hi,
Workstation working group was tracking this:
#241 Re-revisit Fedora Workstation minimums
https://pagure.io/fedora-workstation/issue/241
But to answer the questions, I think we need to broaden the
conversation, hence this email.
Only Fedora Workstation edition explicitly states minimum hardware
requirements: "Fedora requires a minimum of 20GB disk, 2GB RAM, to
install and run successfully. Double those amounts is recommended."
https://getfedora.org/en/workstation/download/
Minimum hardware requirements is intended to setup some kind of
expectation of performance. The goal isn't the hardware requirement,
that's just the means of getting to the goal. So what's the goal? For
sure folks need to be able to install it plus some breathing room to
install additional software and user data. That gets to the minimum
storage space angle.
But the CPU, memory, and IO angle are more complex. A completely
objective metric would account for the local workload, which we don't
know. So we're going to have to come up with a subjective
recommendation, i.e. take an educated guess. (I enjoy underscoring
that subjective != arbitrary.)
How does the minimum hardware requirement achieve the intended goal?
And is it testable? We could ask folks to run some workloads on
low-CPU, low-memory hardware, and report 'grep -r . /proc/pressure'
whenever they think the system is performing worse than expected? Or
what?
Anyway, this is just to kick off a conversation. Let's see where it goes.
--
Chris Murphy
2 years, 8 months
Qt package licenses
by Jerry James
I'm doing a review of a MinGW build of a Qt 6 package:
https://bugzilla.redhat.com/show_bug.cgi?id=2009214
During the license check portion of the review, I have become
increasingly convinced that our qt5-* and qt6-* packages have
incorrect License fields. Currently they have "LGPLv2 with exceptions
or GPLv3 with exceptions". I believe that most or all of them should
have one of these two instead:
- LGPLv3 or GPLv2+
- LGPLv3 or GPLv2+ with exceptions
Could one or two of you license-minded people read through the
comments on that bug and indicate whether you think the analysis is
correct or not, please?
--
Jerry James
http://www.jamezone.org/
2 years, 8 months
bodhi updates skipping updates-testing entirely
by Fabio Valentini
Hi everybody,
There seems to be some inconsistency with how our update workflow
currently works. When an update gets enough positive karma "pre-push"
(still in "pending → testing" state) so that it can be pushed to
stable, bodhi changes its state to ("pending → stable"), making it
skip the "updates-testing" repository entirely.
That isn't that big of a problem most of the time, since "fedora" /
"updates" and "updates-testing" repositories are composed daily, but
during freezes, this leads to the weird problem that possibly
important updates get stuck in a state where they are available from
*no repository at all*.
For example, this now happened to the flatpak 1.12.1 update:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-256d5ee9fe
It got +5 karma before the update was even available from the
updates-testing repository (presumably users tested the builds from
koji directly - I hope?), so it got pushed to "stable" by bodhi. But
now it's been sitting in "pending → stable" state for two days because
of the final freeze, making the update available from *no repository*,
while it's a pretty big update (1.11 → 1.12) and also contains
security fixes and bug fixes for Steam - maybe it should get a freeze
exception now, otherwise it will only become available as a 0day
update.
So, I wonder, should updates always be allowed to skip being in the
"updates-testing" repository entirely? There's probably good reasons
for it sometimes (for example, time-critical security updates, i.e.
firefox, kernel, etc.), but in the general case, not giving regular
"non-koji" update testers any time to test updates before they're
pushed to stable seems suboptimal.
Maybe updates should only be able to be pushed to stable by karma if
they are in the "testing" state, and need a manual "submit to stable"
button push if they're still "pending"? That should be both fairly
straightforward to implement in bodhi, and should allow for both the
"pending → stable fast-track, this is urgent" and the "lets wait and
let it sit in updates-testing for at least one day" scenarios.
What do you think?
Fabio
2 years, 8 months
Fedora 35 compose report: 20211022.n.0 changes
by Fedora Rawhide Report
OLD: Fedora-35-20211021.n.0
NEW: Fedora-35-20211022.n.0
===== SUMMARY =====
Added images: 2
Dropped images: 0
Added packages: 0
Dropped packages: 1
Upgraded packages: 4
Downgraded packages: 0
Size of added packages: 0 B
Size of dropped packages: 70.55 KiB
Size of upgraded packages: 63.62 MiB
Size of downgraded packages: 0 B
Size change of upgraded packages: 25.29 KiB
Size change of downgraded packages: 0 B
===== ADDED IMAGES =====
Image: Server raw-xz aarch64
Path: Server/aarch64/images/Fedora-Server-35-20211022.n.0.aarch64.raw.xz
Image: KDE raw-xz aarch64
Path: Spins/aarch64/images/Fedora-KDE-35-20211022.n.0.aarch64.raw.xz
===== DROPPED IMAGES =====
===== ADDED PACKAGES =====
===== DROPPED PACKAGES =====
Package: python-rpi-gpio-0.7.0-6.fc35
Summary: Class to control the GPIO on a Raspberry Pi
RPMs: python3-RPi.GPIO
Size: 70.55 KiB
===== UPGRADED PACKAGES =====
Package: dracut-055-5.fc35
Old package: dracut-055-4.fc35
Summary: Initramfs generator using udev
RPMs: dracut dracut-caps dracut-config-generic dracut-config-rescue dracut-live dracut-network dracut-squash dracut-tools
Size: 2.40 MiB
Size change: 4.95 KiB
Changelog:
* Mon Oct 18 2021 Adam Williamson <awilliam(a)redhat.com> - 055-5
- Backport PR #1584 to fix missing block drivers, boot in EC2 (#2010058)
Package: fedora-third-party-0.8-1.fc35
Old package: fedora-third-party-0.7-1.fc35
Summary: Tool for handling third-party RPM and Flatpak repositories in Fedora
RPMs: fedora-third-party
Size: 31.18 KiB
Size change: 76 B
Changelog:
* Fri Oct 15 2021 Owen W. Taylor <otaylor(a)fishsoup.net> - 0.8-1
- Drop a chcon call that was making problems for selinux confinement
* Fri Oct 15 2021 Owen W. Taylor <otaylor(a)fishsoup.net> - 0.8-1
- Version 0.8 (Owen W. Taylor)
- Stop calling chcon to propagate selinux context to editor config files (Owen W. Taylor)
Package: plasma-discover-5.23.0-3.fc35
Old package: plasma-discover-5.23.0-2.fc35
Summary: KDE and Plasma resources management GUI
RPMs: plasma-discover plasma-discover-flatpak plasma-discover-libs plasma-discover-notifier plasma-discover-offline-updates plasma-discover-packagekit plasma-discover-rpm-ostree plasma-discover-snap
Size: 41.20 MiB
Size change: 7.72 KiB
Changelog:
* Tue Oct 19 2021 Adam Williamson <awilliam(a)redhat.com> - 5.23.0-3
- Don't use system appstream cache (#2011322)
- Force minimum width for install/remove button (#2015491)
Package: selinux-policy-35.3-1.20211019git94970fc.fc35
Old package: selinux-policy-35.1-1.fc35
Summary: SELinux policy configuration
RPMs: selinux-policy selinux-policy-devel selinux-policy-doc selinux-policy-minimum selinux-policy-mls selinux-policy-sandbox selinux-policy-targeted
Size: 19.99 MiB
Size change: 12.55 KiB
Changelog:
* Mon Oct 18 2021 Zdenek Pytela <zpytela(a)redhat.com> - 35.2-1
- Allow fedora-third-party execute "flatpak remote-add"
- Add files_manage_var_lib_files() interface
- Add write permisson to userfaultfd_anon_inode_perms
- Allow proper function sosreport via iotop
- Allow proper function sosreport in sysadmin role
- Allow fedora-third-party to connect to the system log service
- Allow fedora-third-party dbus chat with policykit
- Allow chrony-wait service start with DynamicUser=yes
- Allow management of lnk_files if similar access to regular files
- Allow unconfined_t transition to mozilla_plugin_t with NoNewPrivileges
- Allow systemd-resolved watch /run/systemd
- Allow fedora-third-party create and use unix_dgram_socket
- Removing pkcs_tmpfs_filetrans interface and edit pkcs policy files
- Allow login_userdomain named filetrans to pkcs_slotd_tmpfs_t domain
* Tue Oct 19 2021 Adam Williamson <awilliam(a)redhat.com> - 35.3-1.20211019git94970fc
- Allow fedora-third-party map generic cache files
- Add gnome_map_generic_cache_files() interface
- Add files_manage_var_lib_dirs() interface
- Allow fedora-third party manage gpg keys
- Allow fedora-third-party run "flatpak remote-add --from flathub"
- Allow fedora-third-party run flatpak post-install actions
===== DOWNGRADED PACKAGES =====
2 years, 8 months