Provisioning Fedora 35 is still broken with updates-testing repo enabled and systemd-249.12-3.fc35.x86_64 installed from it.

This update seems to have caused installation regression https://bugzilla.redhat.com/show_bug.cgi?id=2074083.

Tested with podman run --rm -ti registry.fedoraproject.org/fedora:32 bash -c 'dnf upgrade -y --enablerepo=updates-testing dnf ; dnf install -y zsh'.

I'm experiencing regression https://bugzilla.redhat.com/show_bug.cgi?id=1928643.

Also, for some reason dnf did not show those dependencies in the weak dependency listing ... but that's probably something to report against dnf.

Thanks. I confirm that dnf upgrade --setopt=install_weak_deps=False --enablerepo=updates-testing cura does not pull those in. I'm however worried that subsequent updates will pull them again. Couldn't we use Suggests instead?

In general though, the 4.8.0 cura works well.

I'm not fond of the fact that the update pulls in while texlive stack, compared to 4.7.1, and also compared to my test builds in https://copr.fedorainfracloud.org/coprs/adelton/cura-4.8.0/builds/. Would we be able to get rid of those dependencies?

The build fixed the issue for me on Fedora 32.

The build fixed the GSSAPI issue. Thank you.

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

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

As mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1788084#c15, this update together with https://kojipkgs.fedoraproject.org//packages/python-astroid/2.3.3/4.gitace7b29.fc31/noarch/python3-astroid-2.3.3-4.gitace7b29.fc31.noarch.rpm makes things work, so reverting the karma to +1.

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.

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