Comments

202 Comments

@hxunbanned It is not appropriate to place negative karma on every update. It is also not appropriate to place negative karma on updates that have minor regressions. Please adhere to the feedback guidelines when submitting karma. https://fedoraproject.org/wiki/QA:Update_feedback_guidelines

Yes, it is an optional feature, and it has been added as a weak dependency. Remove or block it if you don't want it.

Compiles and runs Jellyfin as expected.

karma

Thanks for fixing bz 1892006.

BZ#1892006 Not accepting v1.0 config format in F33+
karma

No regressions seen on Vega 11 / Ryzen 3400G.

Upgraded from 19.0.5. No regressions seen.

@itrymybest80, that is an interesting use-case that may not be widely known. I would suggest you raise this on the Wine forum - https://forum.winehq.org/ - or if it is reproducible create an upstream wine-staging bug. https://bugs.winehq.org/enter_bug.cgi?product=Wine-staging

There is no upgrade path for radicale 2 to 3. This breaks F32 to F33 upgrades as there is no radicale 2 in F33.

BZ#1895614 SELinux restorecon in %post fails

There's a dep problem introduced in this update. Problem: cannot install the best candidate for the job - nothing provides pkgconfig(libudfread) >= 1.1.0 needed by libbluray-devel-1.2.1-1.fc33.x86_64

Works fine. Thanks.

BZ#1889199 RFE: Update to 20200907

Starcraft 2 still works.

Thanks for quickly fixing this.

BZ#1885139 nothing provides python3.6dist(pyasn1) >= 0.4.6 needed by python3-ldap3-2.8.1-1.el8.noarch

Perhaps I misread the comment and the linked commit is not to the fix. Sorry.

The flash plugin is still broken in this release. Upstream says they backported it to v80... I guess it was too late for 80.0.1?

https://bugzilla.mozilla.org/show_bug.cgi?id=1661715

FYI - The Flash plugin is broken in v80. Upstream has fixed it.

https://bugzilla.mozilla.org/show_bug.cgi?id=1661715

I can't update wine beyond 5.10 yet. 5.11 requires an updated wine-mono and that update packages a binary form of MinGW clang as a compiler instead of using traditional MinGW gcc.

@atim this update includes the patch from the bug you linked.

Yes, they have been fixed for some time. I added them here so they will get closed. Sorry for the misdirection.