Our purpose in this meeting is to review
proposed blocker and nice-to-have bugs and decide whether to accept
them, and to monitor the progress of fixing existing accepted
blocker and nice-to-have bugs.(adamw,
16:08:41)
We'll be following the process outlined
at:(adamw,
16:08:41)
currently -3 in the ticket, from mcatanzaro,
kparal and adamw:
https://pagure.io/fedora-qa/blocker-review/issue/142(adamw,
16:19:13)
AGREED: 1885479 -
RejectedBlocker (Final) - this is now rejected with the information
that it only happens when user password is changed in a certain way
(that is fairly unlikely to be encountered on first boot or in live
usage)(adamw,
16:26:36)
(1887367) Gnome applications cannot be forwarded via ssh.(adamw, 16:26:56)
we have -2 in the ticket currently, from kparal
and adamw(adamw,
16:28:20)
AGREED: 1887367 -
RejectedBlocker (Final) - we don't think this really meets the
criterion cited or any other, ssh X forwarding does not seem like
basic functionality(adamw,
16:38:47)
we have +2 in the ticket from kparal and
adamw(adamw,
16:42:35)
AGREED: 1863531 -
AcceptedFreezeException (Final) - accepted as we conventionally
accept FTBFS bugs to try and make the frozen final repo as
installable as possible(adamw,
16:48:31)
(1886561) RPM spec file syntax highlighting is not working(adamw, 16:48:37)
AGREED: 1886561 -
AcceptedFreezeException (Final) - we think it makes sense to
maintain continuity here and we disagree with upstream's rationale
for moving these in the first place. it would be good to get
kdudka's clear ack before pushing this, though(adamw,
17:07:26)
(1770599) os-prober very slow - taking up to 20 minutes(adamw, 17:07:36)
we have +2 in the ticket from kparal and
adamw(adamw,
17:08:07)
AGREED: 1770599 -
AcceptedFreezeException (Final) - this is a sensitive thing to
touch, but the bug is pretty bad for affected folks. We think it
makes sense to accept a fix if we're confident about its safety, to
save affected folks from a 10-20 minute delay during install(adamw,
17:13:54)
AGREED: 1886187 -
AcceptedBlocker (Final) - Raspberry Pis up to series 3 are on the
ARM supported hardware list, and we have confirmation of the bug
from coremodule, so accepting as a clear violation of Basic
criterion "All release-blocking images must boot in their supported
configurations"(adamw,
17:17:14)
there's still a lot of confusion about who's
running into what problem here, but it seems we're broadly treating
this bug as being about a scenario where the Secure Boot key that
our initial bootloader (shim) is signed with gets revoked somehow
(due to the BootHole vulnerability)(adamw,
17:57:41)
FESCo has agreed to treat this problem as a
FESCo blocker - https://pagure.io/fesco/issue/2479#comment-694834 -
but stipulates that the resolution "does not necessarily have to be
technical"(adamw,
17:58:19)
so we're broadly waiting on FESCo and pjones to
decide what to do about this(adamw,
17:58:35)