Search results

| {{result|pass|f32 RC-1.6 openqa}} | {{result|pass|f32 RC-1.6 openqa}}

| {{result|pass|f32 RC-1.6 menantea}} | {{result|pass|f32 RC-1.6 menantea}}

* F32 Gnome 3.36 test day;https://fedoraproject.org/wiki/Test_Day:2020-02-20_Gnom

...32 release schedule, so the new compiler version could be introduced into F32 once it's released. ...kages depending on `fpc` should be rebuilt with the new `fpc` once it hits F32, or, if there is not enough time for that, just all packages built after th

| {{result|pass}}<ref>f31 to f32 successful upgrade with dnf-current | {{result|pass}}<ref>f31 to f32 upgrade successful</ref>

* test upgrades of F32 packages to F33 ** Change owner will drop the new builds and revert back to the versions in F32.

** Request a "f32-boost" [https://docs.pagure.org/releng/sop_adding_side_build_targets.html b ...gineering: create an issue similar to [https://pagure.io/releng/issue/8943 f32-boost side tag] (a check of an impact with Release Engineering is needed)

...mage for users working in Computational Neuroscience. || || Approved for F32, Recurring || Yes || 4GB || || [[Category:F32]]

** Haskell packages to be built in a `f32-build-side` tag in Koji. [done]

2019-08-20 Branch Fedora 31 from Rawhide (Rawhide becomes future F32) | fedora-docs-install-guide || 258459 || 5807904 || No || N/A || ||

2019-08-20 Branch Fedora 31 from Rawhide (Rawhide becomes future F32) | fedora-docs-install-guide || 258459 || 5807904 || Requires migration ? || Not started || ||

...issues with packaging and for issues that need tracking (blocker bugs for F32): [https://bugzilla.redhat.com Red Hat Bugzilla] under "IoT".

** Request a f32-llvm side-tag from Release Engineering. ** Merge side-tag into rawhide prior to the f32 branch date.

[[F32_Artwork | Full suite of F32 artwork]]

...ult stream. The `nodejs:14` stream will likely become available during the F32 lifetime. # https://pagure.io/releng/issue/8879 - Create pungi config for Rawhide/F32 ursa prime buildroot

As [[Changes/EnableEarlyoom|Fedora Workstation did in F32]], install earlyoom package, and enable it by default. If RAM goes below 4%

...mpfr-3.1.6 and its dependencies stays intact. The tag would be merged into F32 after everything is rebuilt.

==== Alternative proposal: Do this together with the Python 2 retirement in F32 ====

...mage for users working in Computational Neuroscience. || || Approved for F32, Recurring || Yes || 4GB || ||

...mage for users working in Computational Neuroscience. || || Approved for F32, Recurring || Yes || 4GB || ||

...mage for users working in Computational Neuroscience. || || Approved for F32, Recurring || Yes || 4GB || ||

...issues with packaging and for issues that need tracking (blocker bugs for F32): [https://bugzilla.redhat.com Red Hat Bugzilla] under "IoT".

...ch would be to do the equivalent of dnf module reset all during upgrade to F32, similarly to the proposed solution for https://bugzilla.redhat.com/show_bu ...0-12.fc31 build into the tag, build koo, merge the built package back into f32-build and f31-updates-candidate.

A user installs it during F32 lifetime.

...egular F32 and grub stopped showing the btrfs F33 after install of regular F32.

{{Common bugs issue|f32-iot-aarch64-upgrade|Failed upgrade from Fedora 32 IoT Edition on AArch64|18

* Proposal owners: Rebase golang package in f32, help with resolving possible issues found during package rebuilds.

# Once f32 is out, push EPEL and older stable releases as well (due to compatibility i

...release announcement] and the [https://docs.fedoraproject.org/en-US/fedora/f32/release-notes/ Fedora 32 release notes] for specific information about chan {{Common bugs issue|f32-workstation-ppc64le-grub-boot|Fedora 32 Workstation (ppc64le) Live image fa

...is recommended for secure boot users). This kernel should install fine on F32 systems. | Dell XPS 13 9360, Intel i7-7500U, F32 Workstation

When users are upgraded to firewalld with nftables enabled (f32) all their firewall rules will exist in nftables instead of iptables. All o

...h packaging and for issues that need tracking downstream (blocker bugs for F32): [https://bugzilla.redhat.com Red Hat Bugzilla].

| Thinkpad T440s Core i5 vpro bare metal from F32 to F33 whith /home preservation | qemu on f32

*# Retire {{package|python38}} from F32+

* Make sure to use the latest version of dnf for F32 is installed | F32 Workstation KVM/qemu BIOS

...f Ruby 2.6 and its dependencies stays intact. The tag would be merged into F32 after everything is rebuild.<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->

...extreme case has started to thrash. We have started to ship EarlyOOM with F32, however, while it is a good solution to this date, it is shipped with the

| F32 beta (nightly build) in Gnome Boxes on Thinkpad T440s | F32, Lenovo T480s (i7-8650U)

...is recommended for secure boot users). This kernel should install fine on F32 systems. | F32 with kernel 5.7.6 from koji in VM

* Support for F32 has been removed as EOL.

...is recommended for secure boot users). This kernel should install fine on F32 systems. | F32 Workstation, bare metal, FUJITSU LIFEBOOK E752, BIOS Version 1.13 08/21/201

...can cause corruption of user data must be fixed or documented at [[Common F32 bugs]].

...s released on 2020-04-28. The [https://docs.fedoraproject.org/en-US/fedora/f32/release-notes/ release notes] are on docs.fedoraproject.org. [[Category:F32]]

As Fedora Workstation did in F32, install earlyoom package, and enable it by default. If RAM goes below 4% f

...is recommended for secure boot users). This kernel should install fine on F32 systems. | Lenovo ThinkPad T450 (i5-5300U, 16GB RAM) F32

...is recommended for secure boot users). This kernel should install fine on F32 systems. | F32 on Thinkpad T480s