We will try again for a 29 October release. Action summary ==================== Accepted blockers ----------------- 1. distribution — Cannot upgrade to Fedora 31: package exa-0.9.0-2.module_f31+5365+04413d87.x86_64 requires libgit2.so.28()(64bit), but none of the providers can be installed — MODIFIED ACTION: QA to verify updates FEDORA-2019-e8db3bef68 (F30) and FEDORA-2019-7656a4dd09 (F29) ACTION: FESCo to vote accepting this as sufficient: https://pagure.io/fesco/issue/2230#comment-605570 2. sddm — Cannot start Fedora-KDE-Live (F31) in basic graphics mode on BIOS machine — POST ACTION: systemd maintainers to create an update incorporating upstream PR 13792. 3. dnf — dnf.exceptions.Error: Incorrect or unknown "arch": armv7hcnl — ON_QA ACTION: QA to verify update FEDORA-2019-801cba6c72 ACTION: dnf team to make necessary libdnf & dnf changes Proposed blockers ----------------- 1. gnome-software — gnome-software: gs_flatpak_get_installation(): gnome-software killed by SIGSEGV — ON_QA ACTION: QA to verify update FEDORA-2019-6575577db7 2. PackageKit — Gnome-software should provide workaround for libgit2 for F29/F30->F31 upgrade — NEW ACTION: PackageKit maintainers to add workaround similar to BZ 1747408. Bug-by-bug detail ============= Accepted blockers ----------------- 1. distribution — https://bugzilla.redhat.com/show_bug.cgi?id=1747408 — MODIFIED Cannot upgrade to Fedora 31: package exa-0.9.0-2.module_f31+5365+04413d87.x86_64 requires libgit2.so.28()(64bit), but none of the providers can be installed Accepted as a blocker by FESCo, even though it does not affect default package sets. As a short-term fix, `dnf system-upgrade` will reset the libgit2 module when upgrading from Fedora 29 and Fedora 30. FESCo still needs to accept this proposal as sufficient. 2. sddm — https://bugzilla.redhat.com/show_bug.cgi?id=1728240 — POST Cannot start Fedora-KDE-Live (F31) in basic graphics mode on BIOS machine This issue only seems to affect BIOS machines when using basic graphics mode. There is a systemd component to this issue, which will be fixed in a new build. That may be enough to resolve the blocker independent of the broader fix in sddm. Upstream issue: https://github.com/sddm/sddm/issues/1204 systemd pull request: https://github.com/systemd/systemd/pull/13792 3. dnf — https://bugzilla.redhat.com/show_bug.cgi?id=1691430 — ON_QA dnf.exceptions.Error: Incorrect or unknown "arch": armv7hcnl A virt-install of a armv7 guest on a aarch64 host fails to install. Or if you install f29 with no updates (before the changes that caused this bug) and then tried to update, it would work the first time (using the old dnf) then be broken forever. RPM update FEDORA-2019-801cba6c72 addresses the RPM part of the issue. Changes are also needed in dnf and libdnf to fix detection. Proposed blockers ----------------- 1. gnome-software — https://bugzilla.redhat.com/show_bug.cgi?id=1762689 — ON_QA gnome-software: gs_flatpak_get_installation(): gnome-software killed by SIGSEGV gnome-software crashes very often while running in background, often immediately after boot when at least one Flatpak and at least one non-Flatpak GsApp has an available update and the last app in the list happens to not be a Flatpak. Update FEDORA-2019-6575577db7 contains a backported potential fix. 2. PackageKit — https://bugzilla.redhat.com/show_bug.cgi?id=1762751 — NEW Gnome-software should provide workaround for libgit2 for F29/F30->F31 upgrade The graphical companion to BZ 1747408. If a FESCo majority votes for https://pagure.io/fesco/issue/2230#comment-605570 , it will become an accepted previous release blocker. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx
