Search results

* F34 Virtualization Test Day;https://fedoraproject.org/wiki/Test_Day:2021-04-13_

| {{result|pass|f34 Beta 1.3 openqa}} | {{result|pass|f34 Beta 1.3 openqa}}

| {{result|pass|f34 Beta 1.3 openqa}} | {{result|fail|f34 Beta 1.3 openqa|1937785}}

* F34 Gnome 40 test day;https://fedoraproject.org/wiki/Test_Day:2021-03-17_Fedora

* test upgrades of F34 Haskell packages to F35 ** Change owner will drop the new builds and revert back to the versions in F34.

* [[Fedora_Linux_34_Release_Party_Schedule|Release Party F34 (virtual)]]

| F34 KDE on KVM (UEFI) | F34 workstation KVM + Core-i5

* On an upgrade from F34, if the user opts-out, the enablement status of third-party repositories sh * Contingency mechanism: revert all changes back to the F34 state. (This will also require reverting the filtered-view-of-Flathub chang

Other F34 guests (like cinnamon or workstation): works fine.</ref> Got the same output on the F34 hypervisor so assume all is good.</ref>

** Request a "f34-boost" [https://docs.pagure.org/releng/sop_adding_side_build_targets.html b ...cy mechanism: Worst case scenario is to abandon the update and simply ship F34 with Boost 1.73, which is already in rawhide. It would also be possible to

...ng of <code>rust-*</code> packages from their mass branching script before f34 is branched off of rawhide. * Contingency mechanism: untag and block <code>rust-*</code> packages in the f34 tag in koji (help from releng / a koji admin required), revert mass branchi

Package 'amarok' successfuly rebuilt on top of the MariaDB 10.5 during the F34 mass rebuild. ...e forced to revert the change, bump MariaDB 10.4 package epoch and release F34 with MariaDB 10.4 instead.

** Merge side-tag into rawhide prior to the f34 branch date. ** Continue packaging newer release candidates into rawhide and f34 until the final release is complete (~March 2021)

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

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

{{admon/warning |f33/f34 docker images need docker V20.10:|

...re metal fresh install of F33, standard dnf upgrade to F34, dnf upgrade in F34</ref> ...<ref>Everything works well (even did a dnf upgrade after system-upgrade to F34), except running hostnamectl status makes all the terminal text become a li

...|jpbn}}<ref>after install this one Fedora does not start. dnf upgrade from F34 did work. </ref>

Screenshot-f34-add-ibus-unikey-input-method.png|Adding the ibus-unikey input method in the Screenshot-f34-using-ibus-unikey-input-method.png|How to use the ibus-unikey input method.

[[Category:F34]]