Comments

73 Comments
BZ#1887077 Incorrect password expiry warning
BZ#1889090 After upgrading to kernel-5.8.15-201.fc32.aarch64 Banana Pi M64 does not get IP address from DHCP on eth0
BZ#1889090 After upgrading to kernel-5.8.15-201.fc32.aarch64 Banana Pi M64 does not get IP address from DHCP on eth0

The build fixed the issue for me on Fedora 32.

BZ#1862978 After upgrade to Fedora 32, bip stopped accepting logins

The build fixed the GSSAPI issue. Thank you.

BZ#1830545 After upgrade to Fedora 32, offlineimap GSSAPI authentication no longer works

The CPU Frequency Monitor is working again with this build. Thank you, jan

BZ#1830261 After upgrade to Fedora 32, CPU Frequency Monitor fails to run

Current packages in epel-testing make pylint work for me. Thank you.

BZ#1783311 RFE - build a python-astroid package for EPEL8
BZ#1787911 Missing dependency on `six~=1.12` and `lazy_object_proxy==1.4.*`
BZ#1788084 python3-astroid-2.3.3-2.gitace7b29.fc31 breaks pylint
BZ#1788084 python3-astroid-2.3.3-2.gitace7b29.fc31 breaks pylint
BZ#1788084 python3-astroid-2.3.3-2.gitace7b29.fc31 breaks pylint

Fresh installation of python3-pylint-2.3.1-2.fc31.noarch with https://kojipkgs.fedoraproject.org//packages/python-astroid/2.3.3/3.gitace7b29.fc31/noarch/python3-astroid-2.3.3-3.gitace7b29.fc31.noarch.rpm causes things to fail with pkg_resources.DistributionNotFound: The 'six~=1.12' distribution was not found and is required by astroid.

So that's probably another dependency which is needed.

BZ#1788084 python3-astroid-2.3.3-2.gitace7b29.fc31 breaks pylint

Upgrading python-lazy-object-proxy does not seem to fix the pylint problem.

BZ#1788084 python3-astroid-2.3.3-2.gitace7b29.fc31 breaks pylint

With terminus-fonts-4.48-2.fc31.noarch, Terminus Medium 8 fonts works fine with xfce4-terminal-0.8.8-2.fc31.x86_64 and pango-1.44.7-1.fc31.x86_64. Thank you.

BZ#1748495 The terminus font is no longer found by gvim, so text files come up with glyphs instead of characters.

Upgrading from cri-o-1.16.0-0.1.rc1.git6a4b481.module_f31+6837+7e34758d.x86_64 to ccri-o-1.16.0-0.4.rc2.module_f31+7054+4022d60f.x86_64 does not fix the problem:

Nov 25 03:39:32 machine.example.test systemd[1]: Starting Container Runtime Interface for OCI (CRI-O)... Nov 25 03:39:32 machine.example.test crio[10053]: time="2019-11-25 03:39:32.135457557-05:00" level=fatal msg="Invalid character(s) found in build meta data \"7054+4022d60f-rc2\"" Nov 25 03:39:32 machine.example.test systemd[1]: crio.service: Main process exited, code=exited, status=1/FAILURE Nov 25 03:39:32 machine.example.test systemd[1]: crio.service: Failed with result 'exit-code'. Nov 25 03:39:32 machine.example.test systemd[1]: Failed to start Container Runtime Interface for OCI (CRI-O).

BZ#1740730 cri-o 2:1.14.9-1.module_f30+5132+c35a5687 does not start
BZ#1754170 The crio command fails with: 'Invalid character(s) found in prerelease "module_f30"'
karma

The build addresses the segfault reported in https://bugzilla.redhat.com/show_bug.cgi?id=1665490

BZ#1665490 Importing xmlsec causes segfault when exception message should be displayed [wait for Python 3.7.5]
karma
BZ#1755643 Upgrade to sssd 2.2.2-1.fc30 breaks setting up FreeIPA replica in containers
karma
BZ#1755643 Upgrade to sssd 2.2.2-1.fc30 breaks setting up FreeIPA replica in containers
karma

I experience https://bugzilla.redhat.com/show_bug.cgi?id=1755643 with the 2.2.2-1 SSSD version.