Donate 1 minute of your time to test upgrades from F38 to F39

[Miroslav Suchý]

Do you want to make Fedora 39 better? Please spend 1 minute of your time and try to run:

# Run this only if you use default Fedora modules
# next time you run any DNF command default modules will be enabled again
sudo dnf module reset '*'

dnf --releasever=39 --setopt=module_platform_id=platform:f39 \
--enablerepo=updates-testing \
$(rpm -q fedora-repos-modular >/dev/null && echo --enablerepo=updates-testing-modular) \
--assumeno distro-sync

This command does not replace `dnf system-upgrade`, but it will reveal potential problems.

You may also run `dnf upgrade` before running this command.

The `--assumeno` will just test the transaction, but does not make the actual upgrade.

In case you hit dependency issues, please report it against the appropriate package.

Or against fedora-obsolete-packages if that package should be removed in Fedora 39. Please check existing reports 
against fedora-obsolete-packages first:

https://red.ht/2kuBDPu

and also there is already bunch of "Fails to install" (F39FailsToInstall) reports:

https://bugzilla.redhat.com/buglist.cgi?bug_id=2168845&bug_id_type=andde...

Two notes:

* you may want to run the same command with dnf5 to help test new dnf.

* this command found zero issues on my personal system - great work all everybody!

Thank you

Miroslav

[Steven A. Falco]

On 8/23/23 02:22 PM, Miroslav Suchý wrote:
> dnf --releasever=39 --setopt=module_platform_id=platform:f39 \
> --enablerepo=updates-testing \
> $(rpm -q fedora-repos-modular >/dev/null && echo --enablerepo=updates-testing-modular) \
> --assumeno distro-sync

Problem 1: problem with installed package freecad-1:0.20.2-3.fc38.x86_64
   - freecad-1:0.20.2-3.fc38.x86_64 from @System  does not belong to a distupgrade repository
   - nothing provides libboost_python311.so.1.81.0()(64bit) needed by freecad-1:0.20.2-4.fc39.x86_64 from fedora
   - nothing provides libboost_python311.so.1.81.0()(64bit) needed by freecad-1:0.20.2-4.fc39.x86_64 from fedora-modular
   - nothing provides libboost_python311.so.1.81.0()(64bit) needed by freecad-1:0.20.2-4.fc39.x86_64 from updates-modular
   - nothing provides libboost_python311.so.1.81.0()(64bit) needed by freecad-1:0.20.2-4.fc39.x86_64 from updates-testing-modular
  Problem 2: problem with installed package freecad-data-1:0.20.2-3.fc38.noarch
   - package freecad-data-1:0.20.2-4.fc39.noarch from fedora requires freecad = 1:0.20.2-4.fc39, but none of the providers can be installed
   - package freecad-data-1:0.20.2-4.fc39.noarch from fedora-modular requires freecad = 1:0.20.2-4.fc39, but none of the providers can be installed
   - package freecad-data-1:0.20.2-4.fc39.noarch from updates-modular requires freecad = 1:0.20.2-4.fc39, but none of the providers can be installed
   - package freecad-data-1:0.20.2-4.fc39.noarch from updates-testing-modular requires freecad = 1:0.20.2-4.fc39, but none of the providers can be installed
   - freecad-data-1:0.20.2-3.fc38.noarch from @System  does not belong to a distupgrade repository
   - nothing provides libboost_python311.so.1.81.0()(64bit) needed by freecad-1:0.20.2-4.fc39.x86_64 from fedora
   - nothing provides libboost_python311.so.1.81.0()(64bit) needed by freecad-1:0.20.2-4.fc39.x86_64 from fedora-modular
   - nothing provides libboost_python311.so.1.81.0()(64bit) needed by freecad-1:0.20.2-4.fc39.x86_64 from updates-modular
   - nothing provides libboost_python311.so.1.81.0()(64bit) needed by freecad-1:0.20.2-4.fc39.x86_64 from updates-testing-modular
  Problem 3: problem with installed package python3-shiboken2-1:5.15.7-2.fc38.x86_64
   - package python3-shiboken2-1:5.15.7-2.fc38.x86_64 from @System requires python(abi) = 3.11, but none of the providers can be installed
   - package python3-shiboken2-1:5.15.7-2.fc38.x86_64 from fedora requires python(abi) = 3.11, but none of the providers can be installed
   - package python3-shiboken2-1:5.15.7-2.fc38.x86_64 from fedora-modular requires python(abi) = 3.11, but none of the providers can be installed
   - package python3-shiboken2-1:5.15.7-2.fc38.x86_64 from updates-modular requires python(abi) = 3.11, but none of the providers can be installed
   - package python3-shiboken2-1:5.15.7-2.fc38.x86_64 from updates-testing-modular requires python(abi) = 3.11, but none of the providers can be installed
   - python3-3.11.4-1.fc38.x86_64 from @System  does not belong to a distupgrade repository
  Problem 4: problem with installed package python3-pyside2-1:5.15.7-2.fc38.x86_64
   - package python3-pyside2-1:5.15.7-2.fc38.x86_64 from @System requires python(abi) = 3.11, but none of the providers can be installed
   - package python3-pyside2-1:5.15.7-2.fc38.x86_64 from fedora requires python(abi) = 3.11, but none of the providers can be installed
   - package python3-pyside2-1:5.15.7-2.fc38.x86_64 from fedora-modular requires python(abi) = 3.11, but none of the providers can be installed
   - package python3-pyside2-1:5.15.7-2.fc38.x86_64 from updates-modular requires python(abi) = 3.11, but none of the providers can be installed
   - package python3-pyside2-1:5.15.7-2.fc38.x86_64 from updates-testing-modular requires python(abi) = 3.11, but none of the providers can be installed
   - package python3-3.11.4-1.fc38.x86_64 from @System requires python3-libs(x86-64) = 3.11.4-1.fc38, but none of the providers can be installed
   - python3-libs-3.11.4-1.fc38.x86_64 from @System  does not belong to a distupgrade repository

[Richard Shaw]

On Wed, Aug 23, 2023 at 1:41 PM Steven A. Falco 
wrote:
> On 8/23/23 02:22 PM, Miroslav Suchý wrote:
> > dnf --releasever=39 --setopt=module_platform_id=platform:f39 \
> > --enablerepo=updates-testing \
> > $(rpm -q fedora-repos-modular >/dev/null && echo
>
> --enablerepo=updates-testing-modular) \
> > --assumeno distro-sync
>
> Problem 1: problem with installed package freecad-1:0.20.2-3.fc38.x86_64
> freecad-1:0.20.2-3.fc38.x86_64 from @System  does not belong to a
>
> distupgrade repository
> nothing provides libboost_python311.so.1.81.0()(64bit) needed by
>
> freecad-1:0.20.2-4.fc39.x86_64 from fedora
> nothing provides libboost_python311.so.1.81.0()(64bit) needed by
>
> freecad-1:0.20.2-4.fc39.x86_64 from fedora-modular
> nothing provides libboost_python311.so.1.81.0()(64bit) needed by
>
> freecad-1:0.20.2-4.fc39.x86_64 from updates-modular
> nothing provides libboost_python311.so.1.81.0()(64bit) needed by
>
> freecad-1:0.20.2-4.fc39.x86_64 from updates-testing-modular
>   Problem 2: problem with installed package
> freecad-data-1:0.20.2-3.fc38.noarch
> package freecad-data-1:0.20.2-4.fc39.noarch from fedora requires
>
> freecad = 1:0.20.2-4.fc39, but none of the providers can be installed
> package freecad-data-1:0.20.2-4.fc39.noarch from fedora-modular
>
> requires freecad = 1:0.20.2-4.fc39, but none of the providers can be
> installed
> package freecad-data-1:0.20.2-4.fc39.noarch from updates-modular
>
> requires freecad = 1:0.20.2-4.fc39, but none of the providers can be
> installed
> package freecad-data-1:0.20.2-4.fc39.noarch from
>
> updates-testing-modular requires freecad = 1:0.20.2-4.fc39, but none of the
> providers can be installed
> freecad-data-1:0.20.2-3.fc38.noarch from @System  does not belong to
>
> a distupgrade repository
> nothing provides libboost_python311.so.1.81.0()(64bit) needed by
>
> freecad-1:0.20.2-4.fc39.x86_64 from fedora
> nothing provides libboost_python311.so.1.81.0()(64bit) needed by
>
> freecad-1:0.20.2-4.fc39.x86_64 from fedora-modular
> nothing provides libboost_python311.so.1.81.0()(64bit) needed by
>
> freecad-1:0.20.2-4.fc39.x86_64 from updates-modular
> nothing provides libboost_python311.so.1.81.0()(64bit) needed by
>
> freecad-1:0.20.2-4.fc39.x86_64 from updates-testing-modular
>   Problem 3: problem with installed package
> python3-shiboken2-1:5.15.7-2.fc38.x86_64
> package python3-shiboken2-1:5.15.7-2.fc38.x86_64 from @System
>
> requires python(abi) = 3.11, but none of the providers can be installed
> package python3-shiboken2-1:5.15.7-2.fc38.x86_64 from fedora requires
>
> python(abi) = 3.11, but none of the providers can be installed
> package python3-shiboken2-1:5.15.7-2.fc38.x86_64 from fedora-modular
>
> requires python(abi) = 3.11, but none of the providers can be installed
> package python3-shiboken2-1:5.15.7-2.fc38.x86_64 from updates-modular
>
> requires python(abi) = 3.11, but none of the providers can be installed
> package python3-shiboken2-1:5.15.7-2.fc38.x86_64 from
>
> updates-testing-modular requires python(abi) = 3.11, but none of the
> providers can be installed
> python3-3.11.4-1.fc38.x86_64 from @System  does not belong to a
>
> distupgrade repository
>   Problem 4: problem with installed package
> python3-pyside2-1:5.15.7-2.fc38.x86_64
> package python3-pyside2-1:5.15.7-2.fc38.x86_64 from @System requires
>
> python(abi) = 3.11, but none of the providers can be installed
> package python3-pyside2-1:5.15.7-2.fc38.x86_64 from fedora requires
>
> python(abi) = 3.11, but none of the providers can be installed
> package python3-pyside2-1:5.15.7-2.fc38.x86_64 from fedora-modular
>
> requires python(abi) = 3.11, but none of the providers can be installed
> package python3-pyside2-1:5.15.7-2.fc38.x86_64 from updates-modular
>
> requires python(abi) = 3.11, but none of the providers can be installed
> package python3-pyside2-1:5.15.7-2.fc38.x86_64 from
>
> updates-testing-modular requires python(abi) = 3.11, but none of the
> providers can be installed
> package python3-3.11.4-1.fc38.x86_64 from @System requires
>
> python3-libs(x86-64) = 3.11.4-1.fc38, but none of the providers can be
> installed
> python3-libs-3.11.4-1.fc38.x86_64 from @System  does not belong to a
>
> distupgrade repository

FreeCAD is a known issue since the upgrade to Python 3.12. PySide2 is not
compatible with Python 3.12 and upstream has no intention of making it
compatible as they are only supporting PySide6 for Qt6 now. There's also a
TBB dependency issue.

For now it would be better to use the appimage.

Thanks,
Richard

[Ankur Sinha]

Hello,

I got quite a few issues, some of these are from third party repos, but
others do seem to be Fedora packages that are still FTBFS/FTI (a
majority are neuro-sig packages that we're aware of and working on):

Problem 1: package python3-cypy-0.2.0-12.fc38.noarch from @System requires python(abi) = 3.11, but none of the providers can be installed
  - python3-3.11.4-1.fc38.x86_64 from @System  does not belong to a distupgrade repository
  - problem with installed package python3-cypy-0.2.0-12.fc38.noarch
 Problem 2: package python3-pygments-git-1.6.0-2.fc38.noarch from @System requires python3.11dist(pygments), but none of the providers can be installed
  - python3-pygments-2.14.0-1.fc38.noarch from @System  does not belong to a distupgrade repository
  - problem with installed package python3-pygments-git-1.6.0-2.fc38.noarch
 Problem 3: package python3-pygpu-0.7.6-19.fc38.x86_64 from @System requires python3.11dist(mako) >= 0.7, but none of the providers can be installed
  - python3-mako-1.2.3-2.fc38.noarch from @System  does not belong to a distupgrade repository
  - problem with installed package python3-pygpu-0.7.6-19.fc38.x86_64
 Problem 4: package python3-theano-1.1.2-6.fc38.noarch from @System requires python3.11dist(filelock), but none of the providers can be installed
  - python3-filelock-3.8.2-2.fc38.noarch from @System  does not belong to a distupgrade repository
  - problem with installed package python3-theano-1.1.2-6.fc38.noarch
 Problem 5: package python3-3.11.4-1.fc38.x86_64 from @System requires python3-libs(x86-64) = 3.11.4-1.fc38, but none of the providers can be installed
  - package python3-slip-0.6.4-29.fc38.noarch from @System requires python(abi) = 3.11, but none of the providers can be installed
  - python3-libs-3.11.4-1.fc38.x86_64 from @System  does not belong to a distupgrade repository
  - problem with installed package python3-slip-0.6.4-29.fc38.noarch
 Problem 6: problem with installed package igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64
  - package igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64 from @System requires libprocps.so.8()(64bit), but none of the providers can be installed
  - package igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64 from @System requires libprocps.so.8(LIBPROCPS_0)(64bit), but none of the providers can be installed
  - package igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64 from fedora requires libprocps.so.8()(64bit), but none of the providers can be installed
  - package igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64 from fedora requires libprocps.so.8(LIBPROCPS_0)(64bit), but none of the providers can be installed
  - package igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64 from fedora-modular requires libprocps.so.8()(64bit), but none of the providers can be installed
  - package igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64 from fedora-modular requires libprocps.so.8(LIBPROCPS_0)(64bit), but none of the providers can be installed
  - package igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64 from updates-modular requires libprocps.so.8()(64bit), but none of the providers can be installed
  - package igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64 from updates-modular requires libprocps.so.8(LIBPROCPS_0)(64bit), but none of the providers can be installed
  - package igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64 from updates-testing-modular requires libprocps.so.8()(64bit), but none of the providers can be installed
  - package igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64 from updates-testing-modular requires libprocps.so.8(LIBPROCPS_0)(64bit), but none of the providers can be installed
  - procps-ng-3.3.17-11.fc38.x86_64 from @System  does not belong to a distupgrade repository
 Problem 7: problem with installed package python3-sciunit-0.2.7-6.fc38.noarch
  - package python3-sciunit-0.2.7-6.fc38.noarch from @System requires python3.11dist(gitpython), but none of the providers can be installed
  - package python3-sciunit-0.2.7-6.fc38.noarch from fedora requires python3.11dist(gitpython), but none of the providers can be installed
  - package python3-sciunit-0.2.7-6.fc38.noarch from fedora-modular requires python3.11dist(gitpython), but none of the providers can be installed
  - package python3-sciunit-0.2.7-6.fc38.noarch from updates-modular requires python3.11dist(gitpython), but none of the providers can be installed
  - package python3-sciunit-0.2.7-6.fc38.noarch from updates-testing-modular requires python3.11dist(gitpython), but none of the providers can be installed
  - python3-GitPython-3.1.30-2.fc38.noarch from @System  does not belong to a distupgrade repository
 Problem 8: problem with installed package python3-pyneuroml-0.7.3-1.fc38.noarch
  - package python3-pyneuroml-0.7.3-1.fc38.noarch from @System requires python3.11dist(pylems) >= 0.5.7, but none of the providers can be installed
  - package python3-pyneuroml-0.7.3-1.fc38.noarch from copr:copr.fedorainfracloud.org:group_neurofedora:neurofedora-extra requires python3.11dist(pylems) >= 0.5.7, but none of the providers can be installed
  - python3-PyLEMS-0.6.2-1.fc38.noarch from @System  does not belong to a distupgrade repository
 Problem 9: problem with installed package python3-modelspec-0.2.6-1.fc38.noarch
  - package python3-modelspec-0.2.6-1.fc38.noarch from @System requires python3.11dist(attrs), but none of the providers can be installed
  - package python3-modelspec-0.2.6-1.fc38.noarch from copr:copr.fedorainfracloud.org:group_neurofedora:neurofedora-extra requires python3.11dist(attrs), but none of the providers can be installed
  - python3-attrs-22.2.0-2.fc38.noarch from @System  does not belong to a distupgrade repository
 Problem 10: problem with installed package python3-pyneuroml+brian-0.7.3-1.fc38.noarch
  - package python3-pyneuroml+brian-0.7.3-1.fc38.noarch from @System requires python3.11dist(brian2), but none of the providers can be installed
  - package python3-pyneuroml+brian-0.7.3-1.fc38.noarch from copr:copr.fedorainfracloud.org:group_neurofedora:neurofedora-extra requires python3.11dist(brian2), but none of the providers can be installed
  - python3-brian2-2.5.1-2.fc38.x86_64 from @System  does not belong to a distupgrade repository
 Problem 11: problem with installed package python3-neuromllite-0.5.3-2.fc38.noarch
  - package python3-neuromllite-0.5.3-2.fc38.noarch from @System requires python3.11dist(h5py), but none of the providers can be installed
  - package python3-neuromllite-0.5.3-2.fc38.noarch from copr:copr.fedorainfracloud.org:group_neurofedora:neurofedora-extra requires python3.11dist(h5py), but none of the providers can be installed
  - python3-h5py-3.7.0-4.fc38.x86_64 from @System  does not belong to a distupgrade repository
 Problem 12: problem with installed package python3-pyneuroml+tune-0.7.3-1.fc38.noarch
  - package python3-pyneuroml+tune-0.7.3-1.fc38.noarch from @System requires python3.11dist(inspyred), but none of the providers can be installed
  - package python3-pyneuroml+tune-0.7.3-1.fc38.noarch from copr:copr.fedorainfracloud.org:group_neurofedora:neurofedora-extra requires python3.11dist(inspyred), but none of the providers can be installed
  - python3-inspyred-1.0.1-11.20211124git5fa8224.fc38.noarch from @System  does not belong to a distupgrade repository
 Problem 13: problem with installed package python3-pyneuroml+netpyne-0.7.3-1.fc38.noarch
  - package python3-pyneuroml+netpyne-0.7.3-1.fc38.noarch from @System requires python3.11dist(netpyne), but none of the providers can be installed
  - package python3-pyneuroml+netpyne-0.7.3-1.fc38.noarch from copr:copr.fedorainfracloud.org:group_neurofedora:neurofedora-extra requires python3.11dist(netpyne), but none of the providers can be installed
  - python3-netpyne-1.0.4.1-1.fc38.noarch from @System  does not belong to a distupgrade repository
 Problem 14: problem with installed package python3-pyneuroml+neuron-0.7.3-1.fc38.noarch
  - package python3-pyneuroml+neuron-0.7.3-1.fc38.noarch from @System requires python3.11dist(neuron), but none of the providers can be installed
  - package python3-pyneuroml+neuron-0.7.3-1.fc38.noarch from copr:copr.fedorainfracloud.org:group_neurofedora:neurofedora-extra requires python3.11dist(neuron), but none of the providers can be installed
  - python3-neuron-8.2.2-3.fc38.x86_64 from @System  does not belong to a distupgrade repository
 Problem 15: problem with installed package python3-pyneuroml+analysis-0.7.3-1.fc38.noarch
  - package python3-pyneuroml+analysis-0.7.3-1.fc38.noarch from @System requires python3.11dist(pyelectro), but none of the providers can be installed
  - package python3-pyneuroml+analysis-0.7.3-1.fc38.noarch from copr:copr.fedorainfracloud.org:group_neurofedora:neurofedora-extra requires python3.11dist(pyelectro), but none of the providers can be installed
  - python3-pyelectro-0.2.5-1.fc38.noarch from @System  does not belong to a distupgrade repository
 Problem 16: problem with installed package python3-pyneuroml+hdf5-0.7.3-1.fc38.noarch
  - package python3-pyneuroml+hdf5-0.7.3-1.fc38.noarch from @System requires python3.11dist(tables), but none of the providers can be installed
  - package python3-pyneuroml+hdf5-0.7.3-1.fc38.noarch from copr:copr.fedorainfracloud.org:group_neurofedora:neurofedora-extra requires python3.11dist(tables), but none of the providers can be installed
  - python3-tables-3.7.0-7.fc38.x86_64 from @System  does not belong to a distupgrade repository
 Problem 17: problem with installed package python3.12-devel-3.12.0~rc1-1.fc38.x86_64
  - package python3-devel-3.12.0~rc1-1.fc39.x86_64 from fedora conflicts with python3 < 3.12.0~rc1-1.fc39 provided by python3-3.11.4-1.fc38.x86_64 from @System
  - package python3-devel-3.12.0~rc1-1.fc39.x86_64 from fedora-modular conflicts with python3 < 3.12.0~rc1-1.fc39 provided by python3-3.11.4-1.fc38.x86_64 from @System
  - package python3-devel-3.12.0~rc1-1.fc39.x86_64 from updates-modular conflicts with python3 < 3.12.0~rc1-1.fc39 provided by python3-3.11.4-1.fc38.x86_64 from @System
  - package python3-devel-3.12.0~rc1-1.fc39.x86_64 from updates-testing-modular conflicts with python3 < 3.12.0~rc1-1.fc39 provided by python3-3.11.4-1.fc38.x86_64 from @System
  - package python3-slip-dbus-0.6.4-29.fc38.noarch from @System requires python(abi) = 3.11, but none of the providers can be installed
  - python3.12-devel-3.12.0~rc1-1.fc38.x86_64 from @System  does not belong to a distupgrade repository
  - problem with installed package python3-slip-dbus-0.6.4-29.fc38.noarch
 Problem 18: problem with installed package python3-pyneuroml+povray-0.7.3-1.fc38.noarch
  - package python3-pyneuroml+povray-0.7.3-1.fc38.noarch from @System requires python3-pyneuroml = 0.7.3-1.fc38, but none of the providers can be installed
  - package python3-pyneuroml+povray-0.7.3-1.fc38.noarch from copr:copr.fedorainfracloud.org:group_neurofedora:neurofedora-extra requires python3-pyneuroml = 0.7.3-1.fc38, but none of the providers can be installed
  - package python3-pyneuroml-0.7.3-1.fc38.noarch from @System requires python3.11dist(airspeed) >= 0.5.5, but none of the providers can be installed
  - package python3-pyneuroml-0.7.3-1.fc38.noarch from copr:copr.fedorainfracloud.org:group_neurofedora:neurofedora-extra requires python3.11dist(airspeed) >= 0.5.5, but none of the providers can be installed
  - python3-airspeed-0.5.20-2.fc38.noarch from @System  does not belong to a distupgrade repository
 Problem 19: problem with installed package python3-igor-0.3-26.fc38.noarch
  - package python3-igor-0.3-25.fc39.noarch from fedora requires python(abi) = 3.11, but none of the providers can be installed
  - package python3-igor-0.3-25.fc39.noarch from fedora-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package python3-igor-0.3-25.fc39.noarch from updates-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package python3-igor-0.3-25.fc39.noarch from updates-testing-modular requires python(abi) = 3.11, but none of the providers can be installed
  - problem with installed package python3-devel-3.11.4-1.fc38.x86_64
  - package python3-devel-3.12.0~rc1-1.fc39.x86_64 from fedora conflicts with python3 < 3.12.0~rc1-1.fc39 provided by python3-3.11.4-1.fc38.x86_64 from @System
  - package python3-devel-3.12.0~rc1-1.fc39.x86_64 from fedora-modular conflicts with python3 < 3.12.0~rc1-1.fc39 provided by python3-3.11.4-1.fc38.x86_64 from @System
  - package python3-devel-3.12.0~rc1-1.fc39.x86_64 from updates-modular conflicts with python3 < 3.12.0~rc1-1.fc39 provided by python3-3.11.4-1.fc38.x86_64 from @System
  - package python3-devel-3.12.0~rc1-1.fc39.x86_64 from updates-testing-modular conflicts with python3 < 3.12.0~rc1-1.fc39 provided by python3-3.11.4-1.fc38.x86_64 from @System
  - python3-devel-3.11.4-1.fc38.x86_64 from @System  does not belong to a distupgrade repository
  - python3-igor-0.3-26.fc38.noarch from @System  does not belong to a distupgrade repository
 Problem 20: problem with installed package offlineimap-8.0.0-9.fc38.noarch
  - package offlineimap-8.0.0-7.fc38.noarch from fedora requires python(abi) = 3.11, but none of the providers can be installed
  - package offlineimap-8.0.0-7.fc38.noarch from fedora-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package offlineimap-8.0.0-7.fc38.noarch from updates-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package offlineimap-8.0.0-7.fc38.noarch from updates-testing-modular requires python(abi) = 3.11, but none of the providers can be installed
  - problem with installed package python3.12-3.12.0~rc1-1.fc38.x86_64
  - cannot install both python3-3.12.0~rc1-1.fc39.x86_64 from fedora and python3-3.11.4-1.fc38.x86_64 from @System
  - cannot install both python3-3.12.0~rc1-1.fc39.x86_64 from fedora-modular and python3-3.11.4-1.fc38.x86_64 from @System
  - cannot install both python3-3.12.0~rc1-1.fc39.x86_64 from updates-modular and python3-3.11.4-1.fc38.x86_64 from @System
  - cannot install both python3-3.12.0~rc1-1.fc39.x86_64 from updates-testing-modular and python3-3.11.4-1.fc38.x86_64 from @System
  - python3.12-3.12.0~rc1-1.fc38.x86_64 from @System  does not belong to a distupgrade repository
  - offlineimap-8.0.0-9.fc38.noarch from @System  does not belong to a distupgrade repository
 Problem 21: problem with installed package python3-async-generator-1.10-16.fc38.noarch
  - package python3-async-generator-1.10-16.fc38.noarch from @System requires python(abi) = 3.11, but none of the providers can be installed
  - package python3-async-generator-1.10-16.fc38.noarch from fedora requires python(abi) = 3.11, but none of the providers can be installed
  - package python3-async-generator-1.10-16.fc38.noarch from fedora-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package python3-async-generator-1.10-16.fc38.noarch from updates-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package python3-async-generator-1.10-16.fc38.noarch from updates-testing-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package rfpkgdb-cli-2.15.0-0.14rc2.fc39.noarch from rpmfusion-free requires python(abi) = 3.12, but none of the providers can be installed
  - python3-3.12.0~rc1-1.fc39.i686 from updates-testing-modular  does not belong to a distupgrade repository
  - python3-3.12.0~rc1-1.fc39.i686 from updates-modular  does not belong to a distupgrade repository
  - python3-3.12.0~rc1-1.fc39.i686 from fedora-modular  does not belong to a distupgrade repository
  - python3-3.12.0~rc1-1.fc39.i686 from fedora  does not belong to a distupgrade repository
  - cannot install both python3-3.12.0~rc1-1.fc39.x86_64 from fedora and python3-3.11.4-1.fc38.x86_64 from @System
  - cannot install both python3-3.12.0~rc1-1.fc39.x86_64 from fedora-modular and python3-3.11.4-1.fc38.x86_64 from @System
  - cannot install both python3-3.12.0~rc1-1.fc39.x86_64 from updates-modular and python3-3.11.4-1.fc38.x86_64 from @System
  - cannot install both python3-3.12.0~rc1-1.fc39.x86_64 from updates-testing-modular and python3-3.11.4-1.fc38.x86_64 from @System
  - problem with installed package rfpkgdb-cli-2.15.0-0.12rc2.fc37.noarch
  - rfpkgdb-cli-2.15.0-0.12rc2.fc37.noarch from @System  does not belong to a distupgrade repository

[Steven A. Falco]

On 8/23/23 04:12 PM, Richard Shaw wrote:
> On Wed, Aug 23, 2023 at 1:41 PM Steven A. Falco <[e-mail] > wrote:
> On 8/23/23 02:22 PM, Miroslav Suchý wrote:
>  > dnf --releasever=39 --setopt=module_platform_id=platform:f39 \
>  > --enablerepo=updates-testing \
>  > $(rpm -q fedora-repos-modular >/dev/null && echo --enablerepo=updates-testing-modular) \
>  > --assumeno distro-sync
>    Problem 1: problem with installed package freecad-1:0.20.2-3.fc38.x86_64
>     - freecad-1:0.20.2-3.fc38.x86_64 from @System  does not belong to a distupgrade repository
>     - nothing provides libboost_python311.so.1.81.0()(64bit) needed by freecad-1:0.20.2-4.fc39.x86_64 from fedora
>     - nothing provides libboost_python311.so.1.81.0()(64bit) needed by freecad-1:0.20.2-4.fc39.x86_64 from fedora-modular
>     - nothing provides libboost_python311.so.1.81.0()(64bit) needed by freecad-1:0.20.2-4.fc39.x86_64 from updates-modular
>     - nothing provides libboost_python311.so.1.81.0()(64bit) needed by freecad-1:0.20.2-4.fc39.x86_64 from updates-testing-modular
>    Problem 2: problem with installed package freecad-data-1:0.20.2-3.fc38.noarch
>     - package freecad-data-1:0.20.2-4.fc39.noarch from fedora requires freecad = 1:0.20.2-4.fc39, but none of the providers can be installed
>     - package freecad-data-1:0.20.2-4.fc39.noarch from fedora-modular requires freecad = 1:0.20.2-4.fc39, but none of the providers can be installed
>     - package freecad-data-1:0.20.2-4.fc39.noarch from updates-modular requires freecad = 1:0.20.2-4.fc39, but none of the providers can be installed
>     - package freecad-data-1:0.20.2-4.fc39.noarch from updates-testing-modular requires freecad = 1:0.20.2-4.fc39, but none of the providers can be installed
>     - freecad-data-1:0.20.2-3.fc38.noarch from @System  does not belong to a distupgrade repository
>     - nothing provides libboost_python311.so.1.81.0()(64bit) needed by freecad-1:0.20.2-4.fc39.x86_64 from fedora
>     - nothing provides libboost_python311.so.1.81.0()(64bit) needed by freecad-1:0.20.2-4.fc39.x86_64 from fedora-modular
>     - nothing provides libboost_python311.so.1.81.0()(64bit) needed by freecad-1:0.20.2-4.fc39.x86_64 from updates-modular
>     - nothing provides libboost_python311.so.1.81.0()(64bit) needed by freecad-1:0.20.2-4.fc39.x86_64 from updates-testing-modular
>    Problem 3: problem with installed package python3-shiboken2-1:5.15.7-2.fc38.x86_64
>     - package python3-shiboken2-1:5.15.7-2.fc38.x86_64 from @System requires python(abi) = 3.11, but none of the providers can be installed
>     - package python3-shiboken2-1:5.15.7-2.fc38.x86_64 from fedora requires python(abi) = 3.11, but none of the providers can be installed
>     - package python3-shiboken2-1:5.15.7-2.fc38.x86_64 from fedora-modular requires python(abi) = 3.11, but none of the providers can be installed
>     - package python3-shiboken2-1:5.15.7-2.fc38.x86_64 from updates-modular requires python(abi) = 3.11, but none of the providers can be installed
>     - package python3-shiboken2-1:5.15.7-2.fc38.x86_64 from updates-testing-modular requires python(abi) = 3.11, but none of the providers can be installed
>     - python3-3.11.4-1.fc38.x86_64 from @System  does not belong to a distupgrade repository
>    Problem 4: problem with installed package python3-pyside2-1:5.15.7-2.fc38.x86_64
>     - package python3-pyside2-1:5.15.7-2.fc38.x86_64 from @System requires python(abi) = 3.11, but none of the providers can be installed
>     - package python3-pyside2-1:5.15.7-2.fc38.x86_64 from fedora requires python(abi) = 3.11, but none of the providers can be installed
>     - package python3-pyside2-1:5.15.7-2.fc38.x86_64 from fedora-modular requires python(abi) = 3.11, but none of the providers can be installed
>     - package python3-pyside2-1:5.15.7-2.fc38.x86_64 from updates-modular requires python(abi) = 3.11, but none of the providers can be installed
>     - package python3-pyside2-1:5.15.7-2.fc38.x86_64 from updates-testing-modular requires python(abi) = 3.11, but none of the providers can be installed
>     - package python3-3.11.4-1.fc38.x86_64 from @System requires python3-libs(x86-64) = 3.11.4-1.fc38, but none of the providers can be installed
>     - python3-libs-3.11.4-1.fc38.x86_64 from @System  does not belong to a distupgrade repository
>
>
> FreeCAD is a known issue since the upgrade to Python 3.12. PySide2 is not compatible with Python 3.12 and upstream has no intention of making it compatible as they are only supporting PySide6 for Qt6 now. There's also a TBB dependency issue.
>
> For now it would be better to use the appimage.

Thanks, Richard - I had missed that thread.

Steve

[Artur Frenszek-Iwicki]

> Problem 1: package libblockdev-vdo-2.24-2.fc32.x86_64 from @System requires libbd_utils.so.2()(64bit), but none of the providers can be installed
> libblockdev-utils-2.28-5.fc38.x86_64 from @System  does not belong to a distupgrade repository
> problem with installed package libblockdev-vdo-2.24-2.fc32.x86_64

This one had "fc32" on it, and we allow Obsoletes to be removed after 2 releases, so dunno if we want do anything about it.

Either way, after manually removing said package, there were no other problems.

A.FI.

[hhlp]

just a note rpmfusion free and nofree not ready....

however all was succesfull with adding the parameters --best -- allowerasing

Installing weak dependencies:

avif-pixbuf-loader                                   x86_64 
0.11.1-11.fc39 fedora                                           16 k
  google-noto-sans-mono-cjk-vf-fonts                   noarch 
1:2.004-4.fc39 fedora                                           14 M
  qadwaitadecorations-qt5                              x86_64 
0.1.0-1.fc39 fedora                                           51 k
  qadwaitadecorations-qt6                              x86_64 
0.1.0-1.fc39 fedora                                           59 k
Removing:
  kernel                                               x86_64 
6.4.7-200.fc38 @updates                                          0
  kernel-core                                          x86_64 
6.4.7-200.fc38 @updates                                         65 M
  kernel-devel                                         x86_64 
6.4.7-200.fc38 @updates                                         68 M
  kernel-modules                                       x86_64 
6.4.7-200.fc38 @updates                                         54 M
  kernel-modules-core                                  x86_64 
6.4.7-200.fc38 @updates                                         30 M
  kernel-modules-extra                                 x86_64 
6.4.7-200.fc38 @updates                                        2.4 M

Removing dependent packages:

kmod-nvidia-6.4.7-200.fc38.x86_64                    x86_64 
3:535.86.05-1.fc38 @@commandline                                    43 M
  kmod-v4l2loopback-6.4.7-200.fc38.x86_64              x86_64 
0.12.7^20230503g2c9b670-1.fc38 
@@commandline                                    24 k
  libgweather                                          x86_64 
40.0-5.fc38 @fedora                                          22 M
  protonvpn                                            noarch 1.0.0-3 
@protonvpn-fedora-stable                          0
  protonvpn-gui                                        noarch 1.12.0-1 
@protonvpn-fedora-stable                        7.0 M
  python3-PyDrive                                      noarch 
1.3.1-21.fc37 @fedora                                         223 k
  python3-async-generator                              noarch 
1.10-16.fc38 @fedora                                         232 k
  python3-autopep8                                     noarch 
1.6.0-6.fc38 @fedora                                         570 k
  python3-fastcache                                    x86_64 
1.1.0-14.fc37 @fedora                                          58 k
  python3-flake8-docstrings                            noarch 
1.6.0-4.fc38 @fedora                                          21 k
  python3-googletrans                                  noarch 
4.0.0~rc1-9.fc37 @fedora                                         102 k
  python3-jsonrpc-server                               noarch 
0.4.0-8.fc38 @fedora                                          57 k
  python3-lsp-black                                    noarch 
1.2.0-4.fc38 @fedora                                          25 k
  python3-lsp-server                                   noarch 
1.4.1-3.fc37 @fedora                                         350 k
  python3-protego                                      noarch 
0.2.1-4.fc38 @fedora                                         187 k
  python3-proton-client                                noarch 0.7.1-3 
@protonvpn-fedora-stable                         64 k
  python3-protonvpn-nm-lib                             noarch 
3.16.0-1.fc38 @protonvpn-fedora-stable                        431 k
  python3-pydocstyle                                   noarch 
6.0.0-7.fc38 @fedora                                         351 k
  python3-pygpu                                        x86_64 
0.7.6-19.fc38 @fedora                                         1.1 M
  python3-pyls-spyder                                  noarch 
0.4.0-6.fc38 @fedora                                          27 k
  python3-pyside2                                      x86_64 
1:5.15.7-2.fc38 @fedora                                          48 M
  python3-pytest-flake8                                noarch 
1.1.1-4.fc38 @updates                                         33 k
  python3-qdarkstyle                                   noarch 
3.0.2-7.fc38 @fedora                                         2.0 M
  python3-scrapy                                       noarch 
2.6.1-4.fc38 @fedora                                         1.9 M
  python3-shiboken2                                    x86_64 
1:5.15.7-2.fc38 @fedora                                         600 k
  python3-spyder                                       noarch 
5.3.1-6.fc38 @fedora                                          22 M
  python3-theano                                       noarch 
1.1.2-6.fc38 @fedora                                          17 M
Downgrading:
  blivet-gui                                           noarch 
2.4.1-3.fc39 fedora                                           20 k
  blivet-gui-runtime                                   noarch 
2.4.1-3.fc39 fedora                                          412 k
  buildah                                              x86_64 
1.31.0-2.fc39 fedora                                          8.4 M
  fwupd                                                x86_64 
1.9.3-1.fc39 fedora                                          1.9 M
  fwupd-plugin-flashrom                                x86_64 
1.9.3-1.fc39 fedora                                           24 k
  fwupd-plugin-modem-manager                           x86_64 
1.9.3-1.fc39 fedora                                           56 k
  fwupd-plugin-uefi-capsule-data                       x86_64 
1.9.3-1.fc39 fedora                                          1.9 M
  httpie                                               noarch 
3.2.2-1.fc39 fedora                                          314 k
  lazydocker                                           x86_64 
0.20.0-1.fc38 copr:copr.fedorainfracloud.org:atim:lazydocker  3.4 M
  libspatialite                                        x86_64 
5.0.1-1.fc39 fedora                                          3.1 M
  libytnef                                             x86_64 
1:2.1.1-2.fc39 fedora                                           39 k
  mawk                                                 x86_64 
1:1.3.4-2.20230730.fc39 fedora                                          
146 k
  protonvpn-cli                                        noarch 
2.2.11-9.fc39 fedora                                           87 k
  python3-google-api-core                              noarch 
1:2.11.1-5.fc39 fedora                                          201 k
  python3-googleapis-common-protos                     noarch 
1.60.0-1.fc39 fedora                                          232 k
  rubberband

Transaction Summary
================================================================================================================
Install      83 Packages
Upgrade    4626 Packages
Remove       33 Packages
Downgrade    16 Packages

Total download size: 6.9 G
Operation aborted.

great work

Regards.,

El 23/8/23 a las 20:22, Miroslav Suchý escribió:
> Do you want to make Fedora 39 better? Please spend 1 minute of your 
> time and try to run:
>
> # Run this only if you use default Fedora modules
> # next time you run any DNF command default modules will be enabled again
> sudo dnf module reset '*'
>
> dnf --releasever=39 --setopt=module_platform_id=platform:f39 \
> --enablerepo=updates-testing \
> $(rpm -q fedora-repos-modular >/dev/null && echo 
> --enablerepo=updates-testing-modular) \
> --assumeno distro-sync
>
> This command does not replace `dnf system-upgrade`, but it will reveal 
> potential problems.
>
> You may also run `dnf upgrade` before running this command.
>
> The `--assumeno` will just test the transaction, but does not make the 
> actual upgrade.
>
> In case you hit dependency issues, please report it against the 
> appropriate package.
>
> Or against fedora-obsolete-packages if that package should be removed 
> in Fedora 39. Please check existing reports against 
> fedora-obsolete-packages first:
>
> https://red.ht/2kuBDPu
>
> and also there is already bunch of "Fails to install" 
> (F39FailsToInstall) reports:
>
> https://bugzilla.redhat.com/buglist.cgi?bug_id=2168845&bug_id_type=andde...
>
> Two notes:
>
> you may want to run the same command with dnf5 to help test new dnf.
>
> this command found zero issues on my personal system - great work
>
> all everybody!
>
> Thank you
>
> Miroslav
>
> devel mailing list [e-mail]
> To unsubscribe send an email [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it:https://pagure.io/fedora-infrastructure/new_issue

[Leigh Scott]

> just a note rpmfusion free and nofree not ready....

What is the issue?
I branched rpmfusion repo two weeks ago

$ sudo repoclosure  --check rpmfusion-free --check rpmfusion-nonfree
Last metadata expiration check: 1:27:59 ago on Thu 24 Aug 2023 17:14:49 BST.
package: mesa-va-drivers-freeworld-23.1.5-1.fc39.i686 from rpmfusion-free
  unresolved deps (1):
    mesa-filesystem(x86-32) = 23.1.5
package: mesa-va-drivers-freeworld-23.1.5-1.fc39.x86_64 from rpmfusion-free
  unresolved deps (1):
    mesa-filesystem(x86-64) = 23.1.5
package: mesa-vdpau-drivers-freeworld-23.1.5-1.fc39.i686 from rpmfusion-free
  unresolved deps (1):
    mesa-filesystem(x86-32) = 23.1.5
package: mesa-vdpau-drivers-freeworld-23.1.5-1.fc39.x86_64 from rpmfusion-free
  unresolved deps (1):
    mesa-filesystem(x86-64) = 23.1.5
package: telegram-desktop-4.8.4-2.fc39.x86_64 from rpmfusion-free
  unresolved deps (1):
    qt6-qtbase(x86-64) = 6.5.1
Error: Repoclosure ended with unresolved dependencies (5) across 5 packages.

telegram-desktop is fixed and awaiting to be pushed to the repo.

[Yaakov Selkowitz]

On Wed, 2023-08-23 at 20:22 +0200, Miroslav Suchý wrote:
> Do you want to make Fedora 39 better? Please spend 1 minute of your
> time and try to run:
>
> dnf --releasever=39 --setopt=module_platform_id=platform:f39 \
> --enablerepo=updates-testing \
> $(rpm -q fedora-repos-modular >/dev/null && echo --
> enablerepo=updates-testing-modular) \
> --assumeno distro-sync

No problems on my host system.  Only problems in my toolbox were due to
third-party repositories not yet being ready for F39, and --best --
allowerasing worked around those (which would have removed those
packages).

Let's keep being vigilant as we get closer to GA, but well done so far!

[Michael J Gruber]

Miroslav Suchý venit, vidit, dixit 2023-08-23 20:22:42:
> Do you want to make Fedora 39 better? Please spend 1 minute of your time and try to run:
>
> # Run this only if you use default Fedora modules
> # next time you run any DNF command default modules will be enabled again
> sudo dnf module reset '*'
>
> dnf --releasever=39 --setopt=module_platform_id=platform:f39 \
> --enablerepo=updates-testing \
> $(rpm -q fedora-repos-modular >/dev/null && echo --enablerepo=updates-testing-modular) \
> --assumeno distro-sync
>
> This command does not replace `dnf system-upgrade`, but it will reveal potential problems.
>
> You may also run `dnf upgrade` before running this command.
>
> The `--assumeno` will just test the transaction, but does not make the actual upgrade.
>
> In case you hit dependency issues, please report it against the appropriate package.
>
> Or against fedora-obsolete-packages if that package should be removed in Fedora 39. Please check existing reports 
> against fedora-obsolete-packages first:
>
> https://red.ht/2kuBDPu
>
> and also there is already bunch of "Fails to install" (F39FailsToInstall) reports:
>
> https://bugzilla.redhat.com/buglist.cgi?bug_id=2168845&bug_id_type=andde...
>
> Two notes:
>
> you may want to run the same command with dnf5 to help test new dnf.
>
> this command found zero issues on my personal system - great work all everybody!

Yep, fantastic work! No problems here, except: I want to upgrade to F39
now :)

dnf4 and dnf5 report the exact same number of packages - and dnf5 does
so blazingly fast. I want it now!

The order of information is different. In particular, dnf5 reports:
- Removing
- Downgrading
- Upgrading
- Installing dependencies
- Installing weak dependencies

At first I thought it missed remove/downgrade, because they came before
the gazillion of upgrades. I understand why that order makes sense
logically, but the consequence is that you don't see the first two at
all for a distro-sync, unless you pipe to less or have infinite scroll
back.

The dnf4 order makes sense, too, (expected upgrades, then exceptions)
and does not lead to the scroll back buffer problem for large upgrades.

Michael

[Philip Rhoades]

On 2023-08-24 04:22, Miroslav Suchý wrote:
> Do you want to make Fedora 39 better? Please spend 1 minute of your
> time and try to run:
>
> # Run this only if you use default Fedora modules
> # next time you run any DNF command default modules will be enabled
> again
> sudo dnf module reset '*'
>
> dnf --releasever=39 --setopt=module_platform_id=platform:f39 \
> --enablerepo=updates-testing \
> $(rpm -q fedora-repos-modular >/dev/null && echo
> --enablerepo=updates-testing-modular) \
> --assumeno distro-sync

After a few attempts I used this:

#!/bin/bash

echo "Doing: dnf -y --skip-broken upgrade"
dnf -y --skip-broken upgrade
echo " "

echo "Doing: dnf -y --skip-broken module reset '*'"
dnf -y --skip-broken module reset '*'
echo " "

echo "Doing: dnf --skip-broken --releasever=39 
--setopt=module_platform_id=platform:f39 . . "
dnf --skip-broken --releasever=39 
--setopt=module_platform_id=platform:f39 \
         --enablerepo=updates-testing \
         $(rpm -q fedora-repos-modular >/dev/null && echo 
--enablerepo=updates-testing-modular) \
         --assumeno distro-sync

echo "Done"

and got this output:

Doing: dnf -y --skip-broken upgrade
Last metadata expiration check: 0:20:39 ago on Thu 24 Aug 2023 05:33:10.
Dependencies resolved.
Nothing to do.
Complete!

Doing: dnf -y --skip-broken module reset '*'
Last metadata expiration check: 0:20:45 ago on Thu 24 Aug 2023 05:33:10.
Dependencies resolved.
Nothing to do.
Complete!

Doing: dnf --skip-broken --releasever=39 
--setopt=module_platform_id=platform:f39 . .
RPM Fusion for Fedora 39 - Nonfree - Updates    7.7 kB/s | 113 kB     
00:14
Last metadata expiration check: 0:21:48 ago on Thu 24 Aug 2023 05:33:10.
Done

and this error output:

Errors during downloading metadata for repository 
'rpmfusion-nonfree-updates':
   - Status code: 404 for 
https://mirrors.rpmfusion.org/metalink?repo=nonfree-fedora-updates-released-... 
(IP: 158.69.60.128)
   - Status code: 404 for 
https://mirrors.rpmfusion.org/metalink?repo=nonfree-fedora-updates-released-... 
(IP: 78.47.223.143)
Error: Failed to download metadata for repo 'rpmfusion-nonfree-updates': 
Cannot prepare internal mirrorlist: Status code: 404 for 
https://mirrors.rpmfusion.org/metalink?repo=
nonfree-fedora-updates-released-39&arch=x86_64 (IP: 78.47.223.143)
Ignoring repositories: rpmfusion-nonfree-updates
Error:
  Problem: problem with installed package 
python3-leveldb-0.201-11.fc38.x86_64
   - package python3-leveldb-0.201-11.fc38.x86_64 from @System requires 
python(abi) = 3.11, but none of the providers can be installed
   - package python3-leveldb-0.201-11.fc38.x86_64 from fedora requires 
python(abi) = 3.11, but none of the providers can be installed
   - package python3-leveldb-0.201-11.fc38.x86_64 from fedora-modular 
requires python(abi) = 3.11, but none of the providers can be installed
   - package python3-leveldb-0.201-11.fc38.x86_64 from updates-modular 
requires python(abi) = 3.11, but none of the providers can be installed
   - package python3-leveldb-0.201-11.fc38.x86_64 from 
updates-testing-modular requires python(abi) = 3.11, but none of the 
providers can be installed
   - python3-3.11.4-1.fc38.x86_64 from @System  does not belong to a 
distupgrade repository

P.
> This command does not replace `dnf system-upgrade`, but it will reveal
> potential problems.
>
> You may also run `dnf upgrade` before running this command.
> The `--assumeno` will just test the transaction, but does not make the
> actual upgrade.
>
> In case you hit dependency issues, please report it against the
> appropriate package.
>
> Or against fedora-obsolete-packages if that package should be removed
> in Fedora 39. Please check existing reports against
> fedora-obsolete-packages first:
>
> https://red.ht/2kuBDPu
>
> and also there is already bunch of "Fails to install"
> (F39FailsToInstall) reports:
>
> https://bugzilla.redhat.com/buglist.cgi?bug_id=2168845&bug_id_type=andde...
>
> Two notes:
>
> you may want to run the same command with dnf5 to help test new dnf.
>
> this command found zero issues on my personal system - great work
>
> all everybody!
>
> Thank you
>  Miroslav
> _______________________________________________
> devel mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue

[Nicola Sella]

Thanks Mirek,

dnf --releasever=39 --setopt=module_platform_id=platform:f39 \
> --enablerepo=updates-testing \
> $(rpm -q fedora-repos-modular >/dev/null && echo
> --enablerepo=updates-testing-modular) \
> --assumeno distro-sync

Allow me to steal some testing. :)
I would like to point out that running the same command, replacing dnf with
dnf5, should work and produce the same transaction.
I suggest running both commands and report eventual errors. This would be
of great help for the dnf team to implement/debug distro-upgrade commands.

I am getting no errors in the transaction and have the same package list
with both package managers.

Thanks,

On Wed, Aug 23, 2023 at 8:23 PM Miroslav Suchý  wrote:
> Do you want to make Fedora 39 better? Please spend 1 minute of your time
> and try to run:
>
> # Run this only if you use default Fedora modules
> # next time you run any DNF command default modules will be enabled again
> sudo dnf module reset '*'
>
> dnf --releasever=39 --setopt=module_platform_id=platform:f39 \
> --enablerepo=updates-testing \
> $(rpm -q fedora-repos-modular >/dev/null && echo
> --enablerepo=updates-testing-modular) \
> --assumeno distro-sync
>
> This command does not replace `dnf system-upgrade`, but it will reveal
> potential problems.
>
> You may also run `dnf upgrade` before running this command.
>
> The `--assumeno` will just test the transaction, but does not make the
> actual upgrade.
>
> In case you hit dependency issues, please report it against the
> appropriate package.
>
> Or against fedora-obsolete-packages if that package should be removed in
> Fedora 39. Please check existing reports against fedora-obsolete-packages
> first:
>
> https://red.ht/2kuBDPu
>
> and also there is already bunch of "Fails to install" (F39FailsToInstall)
> reports:
>
> https://bugzilla.redhat.com/buglist.cgi?bug_id=
> 2168845&bug_id_type=anddependson&format=tvp&list_id=12486533
>
> Two notes:
>
> you may want to run the same command with dnf5 to help test new dnf.
>
> this command found zero issues on my personal system - great work all
>
> everybody!
>
> Thank you
> Miroslav
> _______________________________________________
> devel mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue

[Tom London]

On Thu, Aug 24, 2023 at 3:39 AM Nicola Sella  wrote:
> Thanks Mirek,
>
> dnf --releasever=39 --setopt=module_platform_id=platform:f39 \
> > --enablerepo=updates-testing \
> > $(rpm -q fedora-repos-modular >/dev/null && echo
> > --enablerepo=updates-testing-modular) \
> > --assumeno distro-sync
>
> Allow me to steal some testing. :)
> I would like to point out that running the same command, replacing dnf
> with dnf5, should work and produce the same transaction.
> I suggest running both commands and report eventual errors. This would be
> of great help for the dnf team to implement/debug distro-upgrade commands.
>
> I am getting no errors in the transaction and have the same package list
> with both package managers.
>
> Thanks,
>
> I get this with dnf5:

Problem 1: package python3-slip-0.6.4-29.fc38.noarch requires python(abi) =
3.11, but none of the providers can be installed
  - cannot install both python3-3.11.4-1.fc38.x86_64 and
python3-3.12.0~rc1-1.fc39.x86_64
  - cannot install the best update candidate for package
python3-slip-0.6.4-29.fc38.noarch
  - cannot install the best update candidate for package
python3-3.11.4-1.fc38.x86_64
 Problem 2: package python3-3.11.4-1.fc38.x86_64 requires
python3-libs(x86-64) = 3.11.4-1.fc38, but none of the providers can be
installed
  - package python3-slip-dbus-0.6.4-29.fc38.noarch requires python(abi) =
3.11, but none of the providers can be installed
  - cannot install both python3-libs-3.11.4-1.fc38.x86_64 and
python3-libs-3.12.0~rc1-1.fc39.x86_64
  - cannot install the best update candidate for package
python3-slip-dbus-0.6.4-29.fc38.noarch
  - cannot install the best update candidate for package
python3-libs-3.11.4-1.fc38.x86_64
 Problem 3: package ibus-1.5.29~rc1-2.fc39.x86_64 requires python(abi) =
3.12, but none of the providers can be installed
  - python3-3.12.0~rc1-1.fc39.i686 has inferior architecture
  - cannot install both python3-3.11.4-1.fc38.x86_64 and
python3-3.12.0~rc1-1.fc39.x86_64
  - problem with installed package
  - package python3-slip-dbus-0.6.4-29.fc38.noarch requires python(abi) =
3.11, but none of the providers can be installed
  - cannot install the best update candidate for package
ibus-1.5.28-6.fc38.x86_64
 Problem 4: package vtk-9.2.6-6.fc39.x86_64 requires
libpython3.12.so.1.0()(64bit), but none of the providers can be installed
  - cannot install both python3-libs-3.11.4-1.fc38.x86_64 and
python3-libs-3.12.0~rc1-1.fc39.x86_64
  - package python3-3.11.4-1.fc38.x86_64 requires python3-libs(x86-64) =
3.11.4-1.fc38, but none of the providers can be installed
  - problem with installed package
  - package python3-slip-0.6.4-29.fc38.noarch requires python(abi) = 3.11,
but none of the providers can be installed
  - cannot install the best update candidate for package
vtk-9.2.5-2.fc38.x86_64

and this with dnf:

Problem 1: package python3-slip-0.6.4-29.fc38.noarch requires python(abi) =
3.11, but none of the providers can be installed
  - cannot install both python3-3.11.4-1.fc38.x86_64 and
python3-3.12.0~rc1-1.fc39.x86_64
  - cannot install the best update candidate for package
python3-slip-0.6.4-29.fc38.noarch
  - cannot install the best update candidate for package
python3-3.11.4-1.fc38.x86_64
 Problem 2: package python3-3.11.4-1.fc38.x86_64 requires
python3-libs(x86-64) = 3.11.4-1.fc38, but none of the providers can be
installed
  - package python3-slip-dbus-0.6.4-29.fc38.noarch requires python(abi) =
3.11, but none of the providers can be installed
  - cannot install both python3-libs-3.11.4-1.fc38.x86_64 and
python3-libs-3.12.0~rc1-1.fc39.x86_64
  - cannot install the best update candidate for package
python3-slip-dbus-0.6.4-29.fc38.noarch
  - cannot install the best update candidate for package
python3-libs-3.11.4-1.fc38.x86_64
 Problem 3: package torbrowser-launcher-0.3.6-6.fc39.noarch requires
python(abi) = 3.12, but none of the providers can be installed
  - python3-3.12.0~rc1-1.fc39.i686 has inferior architecture
  - cannot install both python3-3.11.4-1.fc38.x86_64 and
python3-3.12.0~rc1-1.fc39.x86_64
  - problem with installed package
  - package python3-slip-dbus-0.6.4-29.fc38.noarch requires python(abi) =
3.11, but none of the providers can be installed
  - cannot install the best update candidate for package
torbrowser-launcher-0.3.6-3.fc38.noarch
 Problem 4: package vtk-9.2.6-6.fc39.x86_64 requires
libpython3.12.so.1.0()(64bit), but none of the providers can be installed
  - cannot install both python3-libs-3.11.4-1.fc38.x86_64 and
python3-libs-3.12.0~rc1-1.fc39.x86_64
  - package python3-3.11.4-1.fc38.x86_64 requires python3-libs(x86-64) =
3.11.4-1.fc38, but none of the providers can be installed
  - problem with installed package
  - package python3-slip-0.6.4-29.fc38.noarch requires python(abi) = 3.11,
but none of the providers can be installed
  - cannot install the best update candidate for package
vtk-9.2.5-2.fc38.x86_64

Notice that Problem 3 is different.

tom

[Tom London]

BTW, after removing python3-slip, python3-slip-dbus and python3-decorator,
both dnf5 and dnf produce no errors

On Thu, Aug 24, 2023 at 6:35 AM Tom London  wrote:
> On Thu, Aug 24, 2023 at 3:39 AM Nicola Sella  wrote:
> > Thanks Mirek,
> >
> > dnf --releasever=39 --setopt=module_platform_id=platform:f39 \
> > > --enablerepo=updates-testing \
> > > $(rpm -q fedora-repos-modular >/dev/null && echo
> > > --enablerepo=updates-testing-modular) \
> > > --assumeno distro-sync
> >
> > Allow me to steal some testing. :)
> > I would like to point out that running the same command, replacing dnf
> > with dnf5, should work and produce the same transaction.
> > I suggest running both commands and report eventual errors. This would be
> > of great help for the dnf team to implement/debug distro-upgrade commands.
> >
> > I am getting no errors in the transaction and have the same package list
> > with both package managers.
> >
> > Thanks,
> >
> > I get this with dnf5:
>
> Problem 1: package python3-slip-0.6.4-29.fc38.noarch requires python(abi)
> = 3.11, but none of the providers can be installed
> cannot install both python3-3.11.4-1.fc38.x86_64 and
>
> python3-3.12.0~rc1-1.fc39.x86_64
> cannot install the best update candidate for package
>
> python3-slip-0.6.4-29.fc38.noarch
> cannot install the best update candidate for package
>
> python3-3.11.4-1.fc38.x86_64
>  Problem 2: package python3-3.11.4-1.fc38.x86_64 requires
> python3-libs(x86-64) = 3.11.4-1.fc38, but none of the providers can be
> installed
> package python3-slip-dbus-0.6.4-29.fc38.noarch requires python(abi) =
>
> 3.11, but none of the providers can be installed
> cannot install both python3-libs-3.11.4-1.fc38.x86_64 and
>
> python3-libs-3.12.0~rc1-1.fc39.x86_64
> cannot install the best update candidate for package
>
> python3-slip-dbus-0.6.4-29.fc38.noarch
> cannot install the best update candidate for package
>
> python3-libs-3.11.4-1.fc38.x86_64
>  Problem 3: package ibus-1.5.29~rc1-2.fc39.x86_64 requires python(abi) =
> 3.12, but none of the providers can be installed
> python3-3.12.0~rc1-1.fc39.i686 has inferior architecture
> cannot install both python3-3.11.4-1.fc38.x86_64 and
>
> python3-3.12.0~rc1-1.fc39.x86_64
> problem with installed package
> package python3-slip-dbus-0.6.4-29.fc38.noarch requires python(abi) =
>
> 3.11, but none of the providers can be installed
> cannot install the best update candidate for package
>
> ibus-1.5.28-6.fc38.x86_64
>  Problem 4: package vtk-9.2.6-6.fc39.x86_64 requires
> libpython3.12.so.1.0()(64bit), but none of the providers can be installed
> cannot install both python3-libs-3.11.4-1.fc38.x86_64 and
>
> python3-libs-3.12.0~rc1-1.fc39.x86_64
> package python3-3.11.4-1.fc38.x86_64 requires python3-libs(x86-64) =
>
> 3.11.4-1.fc38, but none of the providers can be installed
> problem with installed package
> package python3-slip-0.6.4-29.fc38.noarch requires python(abi) = 3.11,
>
> but none of the providers can be installed
> cannot install the best update candidate for package
>
> vtk-9.2.5-2.fc38.x86_64
>
> and this with dnf:
>
> Problem 1: package python3-slip-0.6.4-29.fc38.noarch requires python(abi)
> = 3.11, but none of the providers can be installed
> cannot install both python3-3.11.4-1.fc38.x86_64 and
>
> python3-3.12.0~rc1-1.fc39.x86_64
> cannot install the best update candidate for package
>
> python3-slip-0.6.4-29.fc38.noarch
> cannot install the best update candidate for package
>
> python3-3.11.4-1.fc38.x86_64
>  Problem 2: package python3-3.11.4-1.fc38.x86_64 requires
> python3-libs(x86-64) = 3.11.4-1.fc38, but none of the providers can be
> installed
> package python3-slip-dbus-0.6.4-29.fc38.noarch requires python(abi) =
>
> 3.11, but none of the providers can be installed
> cannot install both python3-libs-3.11.4-1.fc38.x86_64 and
>
> python3-libs-3.12.0~rc1-1.fc39.x86_64
> cannot install the best update candidate for package
>
> python3-slip-dbus-0.6.4-29.fc38.noarch
> cannot install the best update candidate for package
>
> python3-libs-3.11.4-1.fc38.x86_64
>  Problem 3: package torbrowser-launcher-0.3.6-6.fc39.noarch requires
> python(abi) = 3.12, but none of the providers can be installed
> python3-3.12.0~rc1-1.fc39.i686 has inferior architecture
> cannot install both python3-3.11.4-1.fc38.x86_64 and
>
> python3-3.12.0~rc1-1.fc39.x86_64
> problem with installed package
> package python3-slip-dbus-0.6.4-29.fc38.noarch requires python(abi) =
>
> 3.11, but none of the providers can be installed
> cannot install the best update candidate for package
>
> torbrowser-launcher-0.3.6-3.fc38.noarch
>  Problem 4: package vtk-9.2.6-6.fc39.x86_64 requires
> libpython3.12.so.1.0()(64bit), but none of the providers can be installed
> cannot install both python3-libs-3.11.4-1.fc38.x86_64 and
>
> python3-libs-3.12.0~rc1-1.fc39.x86_64
> package python3-3.11.4-1.fc38.x86_64 requires python3-libs(x86-64) =
>
> 3.11.4-1.fc38, but none of the providers can be installed
> problem with installed package
> package python3-slip-0.6.4-29.fc38.noarch requires python(abi) = 3.11,
>
> but none of the providers can be installed
> cannot install the best update candidate for package
>
> vtk-9.2.5-2.fc38.x86_64
>
> Notice that Problem 3 is different.
>
> tom
>
> --
> Tom London

[Robert-André Mauchin]

On 8/23/23 20:22, Miroslav Suchý wrote:
> Do you want to make Fedora 39 better? Please spend 1 minute of your time and try to run:
>
> # Run this only if you use default Fedora modules
> # next time you run any DNF command default modules will be enabled again
> sudo dnf module reset '*'
>
> dnf --releasever=39 --setopt=module_platform_id=platform:f39 \
> --enablerepo=updates-testing \
> $(rpm -q fedora-repos-modular >/dev/null && echo --enablerepo=updates-testing-modular) \
> --assumeno distro-sync
>
> This command does not replace `dnf system-upgrade`, but it will reveal potential problems.
>
> You may also run `dnf upgrade` before running this command.
>
> The `--assumeno` will just test the transaction, but does not make the actual upgrade.
>
> In case you hit dependency issues, please report it against the appropriate package.
>
> Or against fedora-obsolete-packages if that package should be removed in Fedora 39. Please 
> check existing reports against fedora-obsolete-packages first:
>
> https://red.ht/2kuBDPu
>
> and also there is already bunch of "Fails to install" (F39FailsToInstall) reports:
>
> https://bugzilla.redhat.com/buglist.cgi?bug_id=2168845&bug_id_type=andde...
>
> Two notes:
>
> you may want to run the same command with dnf5 to help test new dnf.
>
> this command found zero issues on my personal system - great work all everybody!
>
> Thank you
>
> Miroslav

sudo dnf --releasever=39 --setopt=module_platform_id=platform:f39 \
          --enablerepo=updates-testing \
          $(rpm -q fedora-repos-modular >/dev/null && echo 
--enablerepo=updates-testing-modular) \
          --assumeno distro-sync

Problem 1: problem with installed package mangohud-0.6.9.1-1.fc38.i686
   - package mangohud-0.6.9-1.fc39.i686 from fedora requires libfmt.so.9, but none of the 
providers can be installed
   - package mangohud-0.6.9-1.fc39.i686 from updates-testing-modular requires libfmt.so.9, 
but none of the providers can be installed
   - mangohud-0.6.9.1-1.fc38.i686 from @System  does not belong to a distupgrade repository
   - fmt-9.1.0-2.fc38.i686 from @System  does not belong to a distupgrade repository

Problem 2: problem with installed package mesa-va-drivers-freeworld-23.1.5-1.fc38.x86_64
   - package mesa-va-drivers-freeworld-23.1.5-1.fc39.x86_64 from rpmfusion-free requires 
mesa-filesystem(x86-64) = 23.1.5, but none of the providers can be installed
   - mesa-va-drivers-freeworld-23.1.5-1.fc38.x86_64 from @System  does not belong to a 
distupgrade repository
   - mesa-filesystem-23.1.5-1.fc38.x86_64 from @System  does not belong to a distupgrade 
repository

-> RPMFusion issue probably

Problem 3: problem with installed package mangohud-0.6.9.1-1.fc38.x86_64
   - package mangohud-0.6.9.1-1.fc38.x86_64 from @System requires 
libspdlog.so.1.11()(64bit), but none of the providers can be installed
   - package mangohud-0.6.9-1.fc39.x86_64 from fedora requires libspdlog.so.1.11()(64bit), 
but none of the providers can be installed
   - package mangohud-0.6.9-1.fc39.x86_64 from updates-testing-modular requires 
libspdlog.so.1.11()(64bit), but none of the providers can be installed
   - spdlog-1.11.0-5.fc38.x86_64 from @System  does not belong to a distupgrade repository

Problem 4: problem with installed package mesa-dri-drivers-23.1.5-1.fc38.x86_64
   - package mesa-dri-drivers-23.2.0~rc2-3.fc39.x86_64 from fedora requires 
mesa-filesystem(x86-64) = 23.2.0~rc2-3.fc39, but none of the providers can be installed
   - package mesa-dri-drivers-23.2.0~rc2-3.fc39.x86_64 from updates-testing-modular requires 
mesa-filesystem(x86-64) = 23.2.0~rc2-3.fc39, but none of the providers can be installed
   - cannot install both mesa-filesystem-23.2.0~rc2-3.fc39.x86_64 from fedora and 
mesa-filesystem-23.1.5-1.fc38.x86_64 from @System
   - cannot install both mesa-filesystem-23.2.0~rc2-3.fc39.x86_64 from 
updates-testing-modular and mesa-filesystem-23.1.5-1.fc38.x86_64 from @System
   - package mesa-vdpau-drivers-freeworld-23.1.5-1.fc39.x86_64 from rpmfusion-free requires 
mesa-filesystem(x86-64) = 23.1.5, but none of the providers can be installed
   - problem with installed package mesa-vdpau-drivers-freeworld-23.1.5-1.fc38.x86_64
   - mesa-vdpau-drivers-freeworld-23.1.5-1.fc38.x86_64 from @System  does not belong to a 
distupgrade repository
   - mesa-dri-drivers-23.1.5-1.fc38.x86_64 from @System  does not belong to a distupgrade 
repository

Problem 5: package steam-1.0.0.78-2.fc39.i686 from rpmfusion-nonfree requires 
mesa-dri-drivers(x86-32), but none of the providers can be installed
   - mesa-dri-drivers-23.2.0~rc2-3.fc39.i686 from updates-testing-modular  does not belong 
to a distupgrade repository
   - mesa-dri-drivers-23.2.0~rc2-3.fc39.i686 from fedora  does not belong to a distupgrade 
repository
   - package mesa-dri-drivers-23.2.0~rc2-3.fc39.x86_64 from fedora requires 
mesa-filesystem(x86-64) = 23.2.0~rc2-3.fc39, but none of the providers can be installed
   - package mesa-dri-drivers-23.2.0~rc2-3.fc39.x86_64 from updates-testing-modular requires 
mesa-filesystem(x86-64) = 23.2.0~rc2-3.fc39, but none of the providers can be installed
   - cannot install both mesa-filesystem-23.2.0~rc2-3.fc39.x86_64 from fedora and 
mesa-filesystem-23.1.5-1.fc38.x86_64 from @System
   - cannot install both mesa-filesystem-23.2.0~rc2-3.fc39.x86_64 from 
updates-testing-modular and mesa-filesystem-23.1.5-1.fc38.x86_64 from @System
   - problem with installed package mesa-va-drivers-freeworld-23.1.5-1.fc38.i686
   - mesa-va-drivers-freeworld-23.1.5-1.fc38.i686 from @System  does not belong to a 
distupgrade repository
   - mesa-va-drivers-freeworld-23.1.5-1.fc39.i686 from rpmfusion-free  does not belong to a 
distupgrade repository
   - package mesa-va-drivers-freeworld-23.1.5-1.fc38.x86_64 from @System requires 
mesa-filesystem(x86-64) = 23.1.5, but none of the providers can be installed
   - package mesa-va-drivers-freeworld-23.1.5-1.fc39.x86_64 from rpmfusion-free requires 
mesa-filesystem(x86-64) = 23.1.5, but none of the providers can be installed
   - problem with installed package steam-1.0.0.78-1.fc38.i686
   - package mesa-dri-drivers-23.1.5-1.fc38.i686 from @System requires mesa-libglapi(x86-32) 
= 23.1.5-1.fc38, but none of the providers can be installed
   - steam-1.0.0.78-1.fc38.i686 from @System  does not belong to a distupgrade repository
   - mesa-libglapi-23.1.5-1.fc38.i686 from @System  does not belong to a distupgrade repository
(try to add '--allowerasing' to command line to replace conflicting packages or 
'--skip-broken' to skip uninstallable packages

-> RPMFusion issue.

Not sure about mangohud? it says package mangohud-0.6.9-1.fc39.x86_64 from 
updates-testing-modular, yet it is installed from the updates repo:

Name         : mangohud
Version      : 0.6.9.1
Release      : 1.fc38
Architecture : i686
Size         : 1.6 M
Source       : mangohud-0.6.9.1-1.fc38.src.rpm
Repository   : @System
 From repo    : updates
Summary      : Vulkan overlay layer for monitoring FPS, temperatures, CPU/GPU load and more
URL          : https://github.com/flightlessmango/MangoHud
License      : MIT
Description  : A modification of the Mesa Vulkan overlay. Including GUI improvements,
              : temperature reporting, and logging capabilities.
              :
              : To install GUI front-end:

[Solomon Peachy]

On Wed, Aug 23, 2023 at 08:22:42PM +0200, Miroslav Suchý wrote:
> Do you want to make Fedora 39 better? Please spend 1 minute of your time and try to run:

I ran this on a bunch of my fleet, lots of problems, and they all seem 
to be related to the Python 3.12 bump.

F38 Workstation #1:

Problem 1: problem with installed package openocd-0.12.0-2.fc38.x86_64
  - openocd-0.12.0-2.fc38.x86_64 from @System  does not belong to a distupgrade repository
  - nothing provides libjim.so.0.81()(64bit) needed by openocd-0.12.0-0.rc1.fc38.2.x86_64 from fedora
  - nothing provides libjim.so.0.81()(64bit) needed by openocd-0.12.0-0.rc1.fc38.2.x86_64 from fedora-modular
  - nothing provides libjim.so.0.81()(64bit) needed by openocd-0.12.0-0.rc1.fc38.2.x86_64 from updates-modular
  - nothing provides libjim.so.0.81()(64bit) needed by openocd-0.12.0-0.rc1.fc38.2.x86_64 from updates-testing-modular
 Problem 2: package python3-PyDrive-1.3.1-21.fc37.noarch from @System requires python(abi) = 3.11, but none of the providers can be installed
  - python3-3.11.4-1.fc38.x86_64 from @System  does not belong to a distupgrade repository
  - problem with installed package python3-PyDrive-1.3.1-21.fc37.noarch
 Problem 3: problem with installed package python3-pathtools-0.1.2-30.fc38.noarch
  - package python3-pathtools-0.1.2-30.fc38.noarch from @System requires python(abi) = 3.11, but none of the providers can be installed
  - package python3-pathtools-0.1.2-30.fc38.noarch from fedora requires python(abi) = 3.11, but none of the providers can be installed
  - package python3-pathtools-0.1.2-30.fc38.noarch from fedora-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package python3-pathtools-0.1.2-30.fc38.noarch from updates-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package python3-pathtools-0.1.2-30.fc38.noarch from updates-testing-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package python3-3.11.4-1.fc38.x86_64 from @System requires python3-libs(x86-64) = 3.11.4-1.fc38, but none of the providers can be installed
  - python3-libs-3.11.4-1.fc38.x86_64 from @System  does not belong to a distupgrade repository
Problem 4: problem with installed package python3-devel-3.11.4-1.fc38.x86_64
  - package python3-devel-3.12.0~rc1-1.fc39.x86_64 from fedora conflicts with python3 < 3.12.0~rc1-1.fc39 provided by python3-3.11.4-1.fc38.x86_64 from @System
  - package python3-devel-3.12.0~rc1-1.fc39.x86_64 from fedora-modular conflicts with python3 < 3.12.0~rc1-1.fc39 provided by python3-3.11.4-1.fc38.x86_64 from @System
  - package python3-devel-3.12.0~rc1-1.fc39.x86_64 from updates-modular conflicts with python3 < 3.12.0~rc1-1.fc39 provided by python3-3.11.4-1.fc38.x86_64 from @System
  - package python3-devel-3.12.0~rc1-1.fc39.x86_64 from updates-testing-modular conflicts with python3 < 3.12.0~rc1-1.fc39 provided by python3-3.11.4-1.fc38.x86_64 from @System
  - problem with installed package python3-async-generator-1.10-16.fc38.noarch
  - package python3-async-generator-1.10-16.fc38.noarch from @System requires python(abi) = 3.11, but none of the providers can be installed
  - package python3-async-generator-1.10-16.fc38.noarch from fedora requires python(abi) = 3.11, but none of the providers can be installed
  - package python3-async-generator-1.10-16.fc38.noarch from fedora-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package python3-async-generator-1.10-16.fc38.noarch from updates-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package python3-async-generator-1.10-16.fc38.noarch from updates-testing-modular requires python(abi) = 3.11, but none of the providers can be installed
  - python3-devel-3.11.4-1.fc38.x86_64 from @System  does not belong to a distupgrade repository

F38 Workstation #2:

Problem 1: problem with installed package python3-pathtools-0.1.2-30.fc38.noarch
  - package python3-pathtools-0.1.2-30.fc38.noarch from @System requires python(abi) = 3.11, but none of the providers can be installed
  - package python3-pathtools-0.1.2-30.fc38.noarch from fedora requires python(abi) = 3.11, but none of the providers can be installed
  - package python3-pathtools-0.1.2-30.fc38.noarch from fedora-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package python3-pathtools-0.1.2-30.fc38.noarch from updates-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package python3-pathtools-0.1.2-30.fc38.noarch from updates-testing-modular requires python(abi) = 3.11, but none of the providers can be installed
  - python3-3.11.4-1.fc38.x86_64 from @System  does not belong to a distupgrade repository
 Problem 3: problem with installed package python3-async-generator-1.10-16.fc38.noarch
  - package python3-async-generator-1.10-16.fc38.noarch from @System requires python(abi) = 3.11, but none of the providers can be installed
  - package python3-async-generator-1.10-16.fc38.noarch from fedora requires python(abi) = 3.11, but none of the providers can be installed
  - package python3-async-generator-1.10-16.fc38.noarch from fedora-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package python3-async-generator-1.10-16.fc38.noarch from updates-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package python3-async-generator-1.10-16.fc38.noarch from updates-testing-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package python3-3.11.4-1.fc38.x86_64 from @System requires python3-libs(x86-64) = 3.11.4-1.fc38, but none of the providers can be installed
  - python3-libs-3.11.4-1.fc38.x86_64 from @System  does not belong to a distupgrade repository

F37 snowflake server #1:

Problem 1: problem with installed package matrix-synapse-1.63.1-3.fc37.noarch
  - matrix-synapse-1.63.1-3.fc37.noarch from @System  does not belong to a distupgrade repository
  - nothing provides (python3.11dist(canonicaljson) < 3~~ with python3.11dist(canonicaljson) >= 2) needed by matrix-synapse-1.86.0-1.fc39.x86_64 from fedora
  - nothing provides (python3.11dist(matrix-common) < 2~~ with python3.11dist(matrix-common) >= 1.3) needed by matrix-synapse-1.86.0-1.fc39.x86_64 from fedora
  - nothing provides python3.11dist(immutabledict) >= 2 needed by matrix-synapse-1.86.0-1.fc39.x86_64 from fedora
  - nothing provides python3.11dist(setuptools-rust) >= 1.3 needed by matrix-synapse-1.86.0-1.fc39.x86_64 from fedora
  - nothing provides (python3.11dist(canonicaljson) < 3~~ with python3.11dist(canonicaljson) >= 2) needed by matrix-synapse-1.86.0-1.fc39.x86_64 from fedora-modular
  - nothing provides (python3.11dist(matrix-common) < 2~~ with python3.11dist(matrix-common) >= 1.3) needed by matrix-synapse-1.86.0-1.fc39.x86_64 from fedora-modular
  - nothing provides python3.11dist(immutabledict) >= 2 needed by matrix-synapse-1.86.0-1.fc39.x86_64 from fedora-modular
  - nothing provides python3.11dist(setuptools-rust) >= 1.3 needed by matrix-synapse-1.86.0-1.fc39.x86_64 from fedora-modular
  - nothing provides (python3.11dist(canonicaljson) < 3~~ with python3.11dist(canonicaljson) >= 2) needed by matrix-synapse-1.86.0-1.fc39.x86_64 from updates-modular
  - nothing provides (python3.11dist(matrix-common) < 2~~ with python3.11dist(matrix-common) >= 1.3) needed by matrix-synapse-1.86.0-1.fc39.x86_64 from updates-modular
  - nothing provides python3.11dist(immutabledict) >= 2 needed by matrix-synapse-1.86.0-1.fc39.x86_64 from updates-modular
  - nothing provides python3.11dist(setuptools-rust) >= 1.3 needed by matrix-synapse-1.86.0-1.fc39.x86_64 from updates-modular
  - nothing provides (python3.11dist(canonicaljson) < 3~~ with python3.11dist(canonicaljson) >= 2) needed by matrix-synapse-1.86.0-1.fc39.x86_64 from updates-testing-modular
  - nothing provides (python3.11dist(matrix-common) < 2~~ with python3.11dist(matrix-common) >= 1.3) needed by matrix-synapse-1.86.0-1.fc39.x86_64 from updates-testing-modular
  - nothing provides python3.11dist(immutabledict) >= 2 needed by matrix-synapse-1.86.0-1.fc39.x86_64 from updates-testing-modular
  - nothing provides python3.11dist(setuptools-rust) >= 1.3 needed by matrix-synapse-1.86.0-1.fc39.x86_64 from updates-testing-modular
 Problem 2: package python3-PyDrive-1.3.1-21.fc37.noarch from @System requires python(abi) = 3.11, but none of the providers can be installed
  - python3-3.11.4-1.fc37.x86_64 from @System  does not belong to a distupgrade repository
  - problem with installed package python3-PyDrive-1.3.1-21.fc37.noarch
 Problem 3: problem with installed package matrix-synapse+postgres-1.63.1-3.fc37.noarch
  - package matrix-synapse+postgres-1.86.0-1.fc39.x86_64 from fedora requires matrix-synapse = 1.86.0-1.fc39, but none of the providers can be installed
  - package matrix-synapse+postgres-1.86.0-1.fc39.x86_64 from fedora-modular requires matrix-synapse = 1.86.0-1.fc39, but none of the providers can be installed
  - package matrix-synapse+postgres-1.86.0-1.fc39.x86_64 from updates-modular requires matrix-synapse = 1.86.0-1.fc39, but none of the providers can be installed
  - package matrix-synapse+postgres-1.86.0-1.fc39.x86_64 from updates-testing-modular requires matrix-synapse = 1.86.0-1.fc39, but none of the providers can be installed
  - matrix-synapse+postgres-1.63.1-3.fc37.noarch from @System  does not belong to a distupgrade repository
  - nothing provides (python3.11dist(canonicaljson) < 3~~ with python3.11dist(canonicaljson) >= 2) needed by matrix-synapse-1.86.0-1.fc39.x86_64 from fedora
  - nothing provides (python3.11dist(matrix-common) < 2~~ with python3.11dist(matrix-common) >= 1.3) needed by matrix-synapse-1.86.0-1.fc39.x86_64 from fedora
  - nothing provides python3.11dist(immutabledict) >= 2 needed by matrix-synapse-1.86.0-1.fc39.x86_64 from fedora
  - nothing provides python3.11dist(setuptools-rust) >= 1.3 needed by matrix-synapse-1.86.0-1.fc39.x86_64 from fedora
  - nothing provides (python3.11dist(canonicaljson) < 3~~ with python3.11dist(canonicaljson) >= 2) needed by matrix-synapse-1.86.0-1.fc39.x86_64 from fedora-modular
  - nothing provides (python3.11dist(matrix-common) < 2~~ with python3.11dist(matrix-common) >= 1.3) needed by matrix-synapse-1.86.0-1.fc39.x86_64 from fedora-modular
  - nothing provides python3.11dist(immutabledict) >= 2 needed by matrix-synapse-1.86.0-1.fc39.x86_64 from fedora-modular
  - nothing provides python3.11dist(setuptools-rust) >= 1.3 needed by matrix-synapse-1.86.0-1.fc39.x86_64 from fedora-modular
  - nothing provides (python3.11dist(canonicaljson) < 3~~ with python3.11dist(canonicaljson) >= 2) needed by matrix-synapse-1.86.0-1.fc39.x86_64 from updates-modular
  - nothing provides (python3.11dist(matrix-common) < 2~~ with python3.11dist(matrix-common) >= 1.3) needed by matrix-synapse-1.86.0-1.fc39.x86_64 from updates-modular
  - nothing provides python3.11dist(immutabledict) >= 2 needed by matrix-synapse-1.86.0-1.fc39.x86_64 from updates-modular
  - nothing provides python3.11dist(setuptools-rust) >= 1.3 needed by matrix-synapse-1.86.0-1.fc39.x86_64 from updates-modular
  - nothing provides (python3.11dist(canonicaljson) < 3~~ with python3.11dist(canonicaljson) >= 2) needed by matrix-synapse-1.86.0-1.fc39.x86_64 from updates-testing-modular
  - nothing provides (python3.11dist(matrix-common) < 2~~ with python3.11dist(matrix-common) >= 1.3) needed by matrix-synapse-1.86.0-1.fc39.x86_64 from updates-testing-modular
  - nothing provides python3.11dist(immutabledict) >= 2 needed by matrix-synapse-1.86.0-1.fc39.x86_64 from updates-testing-modular
  - nothing provides python3.11dist(setuptools-rust) >= 1.3 needed by matrix-synapse-1.86.0-1.fc39.x86_64 from updates-testing-modular
 Problem 4: problem with installed package matrix-synapse+systemd-1.63.1-3.fc37.noarch
  - package matrix-synapse+systemd-1.86.0-1.fc39.x86_64 from fedora requires matrix-synapse = 1.86.0-1.fc39, but none of the providers can be installed
  - package matrix-synapse+systemd-1.86.0-1.fc39.x86_64 from fedora-modular requires matrix-synapse = 1.86.0-1.fc39, but none of the providers can be installed
  - package matrix-synapse+systemd-1.86.0-1.fc39.x86_64 from updates-modular requires matrix-synapse = 1.86.0-1.fc39, but none of the providers can be installed
  - package matrix-synapse+systemd-1.86.0-1.fc39.x86_64 from updates-testing-modular requires matrix-synapse = 1.86.0-1.fc39, but none of the providers can be installed
  - matrix-synapse+systemd-1.63.1-3.fc37.noarch from @System  does not belong to a distupgrade repository
  - nothing provides (python3.11dist(canonicaljson) < 3~~ with python3.11dist(canonicaljson) >= 2) needed by matrix-synapse-1.86.0-1.fc39.x86_64 from fedora
  - nothing provides (python3.11dist(matrix-common) < 2~~ with python3.11dist(matrix-common) >= 1.3) needed by matrix-synapse-1.86.0-1.fc39.x86_64 from fedora
  - nothing provides python3.11dist(immutabledict) >= 2 needed by matrix-synapse-1.86.0-1.fc39.x86_64 from fedora
  - nothing provides python3.11dist(setuptools-rust) >= 1.3 needed by matrix-synapse-1.86.0-1.fc39.x86_64 from fedora
  - nothing provides (python3.11dist(canonicaljson) < 3~~ with python3.11dist(canonicaljson) >= 2) needed by matrix-synapse-1.86.0-1.fc39.x86_64 from fedora-modular
  - nothing provides (python3.11dist(matrix-common) < 2~~ with python3.11dist(matrix-common) >= 1.3) needed by matrix-synapse-1.86.0-1.fc39.x86_64 from fedora-modular
  - nothing provides python3.11dist(immutabledict) >= 2 needed by matrix-synapse-1.86.0-1.fc39.x86_64 from fedora-modular
  - nothing provides python3.11dist(setuptools-rust) >= 1.3 needed by matrix-synapse-1.86.0-1.fc39.x86_64 from fedora-modular
  - nothing provides (python3.11dist(canonicaljson) < 3~~ with python3.11dist(canonicaljson) >= 2) needed by matrix-synapse-1.86.0-1.fc39.x86_64 from updates-modular
  - nothing provides (python3.11dist(matrix-common) < 2~~ with python3.11dist(matrix-common) >= 1.3) needed by matrix-synapse-1.86.0-1.fc39.x86_64 from updates-modular
  - nothing provides python3.11dist(immutabledict) >= 2 needed by matrix-synapse-1.86.0-1.fc39.x86_64 from updates-modular
  - nothing provides python3.11dist(setuptools-rust) >= 1.3 needed by matrix-synapse-1.86.0-1.fc39.x86_64 from updates-modular
  - nothing provides (python3.11dist(canonicaljson) < 3~~ with python3.11dist(canonicaljson) >= 2) needed by matrix-synapse-1.86.0-1.fc39.x86_64 from updates-testing-modular
  - nothing provides (python3.11dist(matrix-common) < 2~~ with python3.11dist(matrix-common) >= 1.3) needed by matrix-synapse-1.86.0-1.fc39.x86_64 from updates-testing-modular
  - nothing provides python3.11dist(immutabledict) >= 2 needed by matrix-synapse-1.86.0-1.fc39.x86_64 from updates-testing-modular
  - nothing provides python3.11dist(setuptools-rust) >= 1.3 needed by matrix-synapse-1.86.0-1.fc39.x86_64 from updates-testing-modular
 Problem 5: problem with installed package fail2ban-server-1.0.2-3.fc37.noarch
  - package fail2ban-server-1.0.2-5.fc39.noarch from fedora requires python(abi) = 3.11, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from fedora-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from updates-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from updates-testing-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package python3-3.11.4-1.fc37.x86_64 from @System requires python3-libs(x86-64) = 3.11.4-1.fc37, but none of the providers can be installed
  - python3-libs-3.11.4-1.fc37.x86_64 from @System  does not belong to a distupgrade repository
  - fail2ban-server-1.0.2-3.fc37.noarch from @System  does not belong to a distupgrade repository
 Problem 6: problem with installed package fail2ban-systemd-1.0.2-3.fc37.noarch
  - package fail2ban-systemd-1.0.2-5.fc39.noarch from fedora requires fail2ban-server = 1.0.2-5.fc39, but none of the providers can be installed
  - package fail2ban-systemd-1.0.2-5.fc39.noarch from fedora-modular requires fail2ban-server = 1.0.2-5.fc39, but none of the providers can be installed
  - package fail2ban-systemd-1.0.2-5.fc39.noarch from updates-modular requires fail2ban-server = 1.0.2-5.fc39, but none of the providers can be installed
  - package fail2ban-systemd-1.0.2-5.fc39.noarch from updates-testing-modular requires fail2ban-server = 1.0.2-5.fc39, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from fedora requires python(abi) = 3.11, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from fedora-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from updates-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from updates-testing-modular requires python(abi) = 3.11, but none of the providers can be installed
  - problem with installed package python3-devel-3.11.4-1.fc37.x86_64
  - package python3-devel-3.12.0~rc1-1.fc39.x86_64 from fedora conflicts with python3 < 3.12.0~rc1-1.fc39 provided by python3-3.11.4-1.fc37.x86_64 from @System
  - package python3-devel-3.12.0~rc1-1.fc39.x86_64 from fedora-modular conflicts with python3 < 3.12.0~rc1-1.fc39 provided by python3-3.11.4-1.fc37.x86_64 from @System
  - package python3-devel-3.12.0~rc1-1.fc39.x86_64 from updates-modular conflicts with python3 < 3.12.0~rc1-1.fc39 provided by python3-3.11.4-1.fc37.x86_64 from @System
  - package python3-devel-3.12.0~rc1-1.fc39.x86_64 from updates-testing-modular conflicts with python3 < 3.12.0~rc1-1.fc39 provided by python3-3.11.4-1.fc37.x86_64 from @System
  - python3-devel-3.11.4-1.fc37.x86_64 from @System  does not belong to a distupgrade repository
  - fail2ban-systemd-1.0.2-3.fc37.noarch from @System  does not belong to a distupgrade repository
 Problem 7: problem with installed package fail2ban-sendmail-1.0.2-3.fc37.noarch
  - package fail2ban-sendmail-1.0.2-5.fc39.noarch from fedora requires fail2ban-server = 1.0.2-5.fc39, but none of the providers can be installed
  - package fail2ban-sendmail-1.0.2-5.fc39.noarch from fedora-modular requires fail2ban-server = 1.0.2-5.fc39, but none of the providers can be installed
  - package fail2ban-sendmail-1.0.2-5.fc39.noarch from updates-modular requires fail2ban-server = 1.0.2-5.fc39, but none of the providers can be installed
  - package fail2ban-sendmail-1.0.2-5.fc39.noarch from updates-testing-modular requires fail2ban-server = 1.0.2-5.fc39, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from fedora requires python(abi) = 3.11, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from fedora-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from updates-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from updates-testing-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package python3-3.11.4-1.fc37.x86_64 from @System requires python3-libs(x86-64) = 3.11.4-1.fc37, but none of the providers can be installed
  - package weechat-4.0.4-3.fc39.x86_64 from updates-testing requires libpython3.12.so.1.0()(64bit), but none of the providers can be installed
  - cannot install both python3-libs-3.12.0~rc1-1.fc39.x86_64 from fedora and python3-libs-3.11.4-1.fc37.x86_64 from @System
  - cannot install both python3-libs-3.12.0~rc1-1.fc39.x86_64 from fedora-modular and python3-libs-3.11.4-1.fc37.x86_64 from @System
  - cannot install both python3-libs-3.12.0~rc1-1.fc39.x86_64 from updates-modular and python3-libs-3.11.4-1.fc37.x86_64 from @System
  - cannot install both python3-libs-3.12.0~rc1-1.fc39.x86_64 from updates-testing-modular and python3-libs-3.11.4-1.fc37.x86_64 from @System
  - problem with installed package weechat-3.6-1.fc37.x86_64
  - package weechat-3.6-6.fc39.x86_64 from fedora requires libperl.so.5.36()(64bit), but none of the providers can be installed
  - package weechat-3.6-6.fc39.x86_64 from fedora-modular requires libperl.so.5.36()(64bit), but none of the providers can be installed
  - package weechat-3.6-6.fc39.x86_64 from updates-modular requires libperl.so.5.36()(64bit), but none of the providers can be installed
  - package weechat-3.6-6.fc39.x86_64 from updates-testing-modular requires libperl.so.5.36()(64bit), but none of the providers can be installed
  - weechat-3.6-1.fc37.x86_64 from @System  does not belong to a distupgrade repository
  - perl-libs-4:5.36.1-494.fc37.x86_64 from @System  does not belong to a distupgrade repository
  - fail2ban-sendmail-1.0.2-3.fc37.noarch from @System  does not belong to a distupgrade repository
 Problem 8: problem with installed package fail2ban-mail-1.0.2-3.fc37.noarch
  - package fail2ban-mail-1.0.2-5.fc39.noarch from fedora requires fail2ban-server = 1.0.2-5.fc39, but none of the providers can be installed
  - package fail2ban-mail-1.0.2-5.fc39.noarch from fedora-modular requires fail2ban-server = 1.0.2-5.fc39, but none of the providers can be installed
  - package fail2ban-mail-1.0.2-5.fc39.noarch from updates-modular requires fail2ban-server = 1.0.2-5.fc39, but none of the providers can be installed
  - package fail2ban-mail-1.0.2-5.fc39.noarch from updates-testing-modular requires fail2ban-server = 1.0.2-5.fc39, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from fedora requires python(abi) = 3.11, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from fedora-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from updates-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from updates-testing-modular requires python(abi) = 3.11, but none of the providers can be installed
  - problem with installed package gobject-introspection-devel-1.74.0-1.fc37.x86_64
  - package gobject-introspection-devel-1.76.1-5.fc39.x86_64 from updates-testing-modular requires (python(abi) = 3.12 if python3), but none of the providers can be installed
  - package gobject-introspection-devel-1.76.1-5.fc39.x86_64 from updates-modular requires (python(abi) = 3.12 if python3), but none of the providers can be installed
  - package gobject-introspection-devel-1.76.1-5.fc39.x86_64 from fedora-modular requires (python(abi) = 3.12 if python3), but none of the providers can be installed
  - package gobject-introspection-devel-1.76.1-5.fc39.x86_64 from fedora requires (python(abi) = 3.12 if python3), but none of the providers can be installed
  - python3-3.12.0~rc1-1.fc39.i686 from updates-testing-modular  does not belong to a distupgrade repository
  - python3-3.12.0~rc1-1.fc39.i686 from updates-modular  does not belong to a distupgrade repository
  - python3-3.12.0~rc1-1.fc39.i686 from fedora-modular  does not belong to a distupgrade repository
  - python3-3.12.0~rc1-1.fc39.i686 from fedora  does not belong to a distupgrade repository
  - cannot install both python3-3.12.0~rc1-1.fc39.x86_64 from fedora and python3-3.11.4-1.fc37.x86_64 from @System
  - cannot install both python3-3.12.0~rc1-1.fc39.x86_64 from fedora-modular and python3-3.11.4-1.fc37.x86_64 from @System
  - cannot install both python3-3.12.0~rc1-1.fc39.x86_64 from updates-modular and python3-3.11.4-1.fc37.x86_64 from @System
  - cannot install both python3-3.12.0~rc1-1.fc39.x86_64 from updates-testing-modular and python3-3.11.4-1.fc37.x86_64 from @System
  - gobject-introspection-devel-1.74.0-1.fc37.x86_64 from @System  does not belong to a distupgrade repository
  - fail2ban-mail-1.0.2-3.fc37.noarch from @System  does not belong to a distupgrade repository

F37 server #2:

Problem 1: problem with installed package fail2ban-server-1.0.2-3.fc37.noarch
  - package fail2ban-server-1.0.2-5.fc39.noarch from fedora requires python(abi) = 3.11, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from fedora-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from updates-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from updates-testing-modular requires python(abi) = 3.11, but none of the providers can be installed
  - python3-3.11.4-1.fc37.x86_64 from @System  does not belong to a distupgrade repository
  - fail2ban-server-1.0.2-3.fc37.noarch from @System  does not belong to a distupgrade repository
 Problem 2: problem with installed package fail2ban-sendmail-1.0.2-3.fc37.noarch
  - package fail2ban-sendmail-1.0.2-5.fc39.noarch from fedora requires fail2ban-server = 1.0.2-5.fc39, but none of the providers can be installed
  - package fail2ban-sendmail-1.0.2-5.fc39.noarch from fedora-modular requires fail2ban-server = 1.0.2-5.fc39, but none of the providers can be installed
  - package fail2ban-sendmail-1.0.2-5.fc39.noarch from updates-modular requires fail2ban-server = 1.0.2-5.fc39, but none of the providers can be installed
  - package fail2ban-sendmail-1.0.2-5.fc39.noarch from updates-testing-modular requires fail2ban-server = 1.0.2-5.fc39, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from fedora requires python(abi) = 3.11, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from fedora-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from updates-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from updates-testing-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package python3-3.11.4-1.fc37.x86_64 from @System requires python3-libs(x86-64) = 3.11.4-1.fc37, but none of the providers can be installed
  - python3-libs-3.11.4-1.fc37.x86_64 from @System  does not belong to a distupgrade repository
  - fail2ban-sendmail-1.0.2-3.fc37.noarch from @System  does not belong to a distupgrade repository
 Problem 3: problem with installed package fail2ban-firewalld-1.0.2-3.fc37.noarch
  - package fail2ban-firewalld-1.0.2-5.fc39.noarch from fedora requires fail2ban-server = 1.0.2-5.fc39, but none of the providers can be installed
  - package fail2ban-firewalld-1.0.2-5.fc39.noarch from fedora-modular requires fail2ban-server = 1.0.2-5.fc39, but none of the providers can be installed
  - package fail2ban-firewalld-1.0.2-5.fc39.noarch from updates-modular requires fail2ban-server = 1.0.2-5.fc39, but none of the providers can be installed
  - package fail2ban-firewalld-1.0.2-5.fc39.noarch from updates-testing-modular requires fail2ban-server = 1.0.2-5.fc39, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from fedora requires python(abi) = 3.11, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from fedora-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from updates-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from updates-testing-modular requires python(abi) = 3.11, but none of the providers can be installed
  - problem with installed package rdiff-backup-2.2.5-2.fc37.x86_64
  - package rdiff-backup-2.2.5-4.fc39.x86_64 from fedora requires python(abi) = 3.12, but none of the providers can be installed
  - package rdiff-backup-2.2.5-4.fc39.x86_64 from fedora-modular requires python(abi) = 3.12, but none of the providers can be installed
  - package rdiff-backup-2.2.5-4.fc39.x86_64 from updates-modular requires python(abi) = 3.12, but none of the providers can be installed
  - package rdiff-backup-2.2.5-4.fc39.x86_64 from updates-testing-modular requires python(abi) = 3.12, but none of the providers can be installed
  - python3-3.12.0~rc1-1.fc39.i686 from updates-testing-modular  does not belong to a distupgrade repository
  - python3-3.12.0~rc1-1.fc39.i686 from updates-modular  does not belong to a distupgrade repository
  - python3-3.12.0~rc1-1.fc39.i686 from fedora-modular  does not belong to a distupgrade repository
  - python3-3.12.0~rc1-1.fc39.i686 from fedora  does not belong to a distupgrade repository
  - cannot install both python3-3.12.0~rc1-1.fc39.x86_64 from fedora and python3-3.11.4-1.fc37.x86_64 from @System
  - cannot install both python3-3.12.0~rc1-1.fc39.x86_64 from fedora-modular and python3-3.11.4-1.fc37.x86_64 from @System
  - cannot install both python3-3.12.0~rc1-1.fc39.x86_64 from updates-modular and python3-3.11.4-1.fc37.x86_64 from @System
  - cannot install both python3-3.12.0~rc1-1.fc39.x86_64 from updates-testing-modular and python3-3.11.4-1.fc37.x86_64 from @System
  - rdiff-backup-2.2.5-2.fc37.x86_64 from @System  does not belong to a distupgrade repository
  - fail2ban-firewalld-1.0.2-3.fc37.noarch from @System  does not belong to a distupgrade repository
 Problem 4: problem with installed package fail2ban-1.0.2-3.fc37.noarch
  - package fail2ban-1.0.2-5.fc39.noarch from fedora requires fail2ban-server = 1.0.2-5.fc39, but none of the providers can be installed
  - package fail2ban-1.0.2-5.fc39.noarch from fedora-modular requires fail2ban-server = 1.0.2-5.fc39, but none of the providers can be installed
  - package fail2ban-1.0.2-5.fc39.noarch from updates-modular requires fail2ban-server = 1.0.2-5.fc39, but none of the providers can be installed
  - package fail2ban-1.0.2-5.fc39.noarch from updates-testing-modular requires fail2ban-server = 1.0.2-5.fc39, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from fedora requires python(abi) = 3.11, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from fedora-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from updates-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from updates-testing-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package python3-3.11.4-1.fc37.x86_64 from @System requires python3-libs(x86-64) = 3.11.4-1.fc37, but none of the providers can be installed
  - problem with installed package unbound-libs-1.17.1-1.fc37.x86_64
  - package unbound-libs-1.17.1-4.fc39.x86_64 from fedora requires libpython3.12.so.1.0()(64bit), but none of the providers can be installed
  - package unbound-libs-1.17.1-4.fc39.x86_64 from fedora-modular requires libpython3.12.so.1.0()(64bit), but none of the providers can be installed
  - package unbound-libs-1.17.1-4.fc39.x86_64 from updates-modular requires libpython3.12.so.1.0()(64bit), but none of the providers can be installed
  - package unbound-libs-1.17.1-4.fc39.x86_64 from updates-testing-modular requires libpython3.12.so.1.0()(64bit), but none of the providers can be installed
  - cannot install both python3-libs-3.12.0~rc1-1.fc39.x86_64 from fedora and python3-libs-3.11.4-1.fc37.x86_64 from @System
  - cannot install both python3-libs-3.12.0~rc1-1.fc39.x86_64 from fedora-modular and python3-libs-3.11.4-1.fc37.x86_64 from @System
  - cannot install both python3-libs-3.12.0~rc1-1.fc39.x86_64 from updates-modular and python3-libs-3.11.4-1.fc37.x86_64 from @System
  - cannot install both python3-libs-3.12.0~rc1-1.fc39.x86_64 from updates-testing-modular and python3-libs-3.11.4-1.fc37.x86_64 from @System
  - unbound-libs-1.17.1-1.fc37.x86_64 from @System  does not belong to a distupgrade repository
  - fail2ban-1.0.2-3.fc37.noarch from @System  does not belong to a distupgrade repository

F38 server #1:

Problem 1: problem with installed package fail2ban-server-1.0.2-3.fc38.noarch
  - package fail2ban-server-1.0.2-5.fc39.noarch from fedora requires python(abi) = 3.11, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from fedora-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from updates-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from updates-testing-modular requires python(abi) = 3.11, but none of the providers can be installed
  - python3-3.11.4-1.fc38.x86_64 from @System  does not belong to a distupgrade repository
  - fail2ban-server-1.0.2-3.fc38.noarch from @System  does not belong to a distupgrade repository
 Problem 2: problem with installed package fail2ban-systemd-1.0.2-3.fc38.noarch
  - package fail2ban-systemd-1.0.2-5.fc39.noarch from fedora requires fail2ban-server = 1.0.2-5.fc39, but none of the providers can be installed
  - package fail2ban-systemd-1.0.2-5.fc39.noarch from fedora-modular requires fail2ban-server = 1.0.2-5.fc39, but none of the providers can be installed
  - package fail2ban-systemd-1.0.2-5.fc39.noarch from updates-modular requires fail2ban-server = 1.0.2-5.fc39, but none of the providers can be installed
  - package fail2ban-systemd-1.0.2-5.fc39.noarch from updates-testing-modular requires fail2ban-server = 1.0.2-5.fc39, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from fedora requires python(abi) = 3.11, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from fedora-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from updates-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from updates-testing-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package python3-3.11.4-1.fc38.x86_64 from @System requires python3-libs(x86-64) = 3.11.4-1.fc38, but none of the providers can be installed
  - python3-libs-3.11.4-1.fc38.x86_64 from @System  does not belong to a distupgrade repository
  - fail2ban-systemd-1.0.2-3.fc38.noarch from @System  does not belong to a distupgrade repository
 Problem 3: problem with installed package fail2ban-sendmail-1.0.2-3.fc38.noarch
  - package fail2ban-sendmail-1.0.2-5.fc39.noarch from fedora requires fail2ban-server = 1.0.2-5.fc39, but none of the providers can be installed
  - package fail2ban-sendmail-1.0.2-5.fc39.noarch from fedora-modular requires fail2ban-server = 1.0.2-5.fc39, but none of the providers can be installed
  - package fail2ban-sendmail-1.0.2-5.fc39.noarch from updates-modular requires fail2ban-server = 1.0.2-5.fc39, but none of the providers can be installed
  - package fail2ban-sendmail-1.0.2-5.fc39.noarch from updates-testing-modular requires fail2ban-server = 1.0.2-5.fc39, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from fedora requires python(abi) = 3.11, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from fedora-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from updates-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from updates-testing-modular requires python(abi) = 3.11, but none of the providers can be installed
  - problem with installed package python3-devel-3.11.4-1.fc38.x86_64
  - package python3-devel-3.12.0~rc1-1.fc39.x86_64 from fedora conflicts with python3 < 3.12.0~rc1-1.fc39 provided by python3-3.11.4-1.fc38.x86_64 from @System
  - package python3-devel-3.12.0~rc1-1.fc39.x86_64 from fedora-modular conflicts with python3 < 3.12.0~rc1-1.fc39 provided by python3-3.11.4-1.fc38.x86_64 from @System
  - package python3-devel-3.12.0~rc1-1.fc39.x86_64 from updates-modular conflicts with python3 < 3.12.0~rc1-1.fc39 provided by python3-3.11.4-1.fc38.x86_64 from @System
  - package python3-devel-3.12.0~rc1-1.fc39.x86_64 from updates-testing-modular conflicts with python3 < 3.12.0~rc1-1.fc39 provided by python3-3.11.4-1.fc38.x86_64 from @System
  - python3-devel-3.11.4-1.fc38.x86_64 from @System  does not belong to a distupgrade repository
  - fail2ban-sendmail-1.0.2-3.fc38.noarch from @System  does not belong to a distupgrade repository

F38 server #2:

Problem 1: problem with installed package fail2ban-server-1.0.2-3.fc38.noarch  x
  - package fail2ban-server-1.0.2-5.fc39.noarch from fedora requires python(abi) = 3.11, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from fedora-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from updates-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from updates-testing-modular requires python(abi) = 3.11, but none of the providers can be installed
  - python3-3.11.4-1.fc38.x86_64 from @System  does not belong to a distupgrade repository
  - fail2ban-server-1.0.2-3.fc38.noarch from @System  does not belong to a distupgrade repository
Problem 2: problem with installed package fail2ban-systemd-1.0.2-3.fc38.noarch omes with ABSOLUTELY NO WA
  - package fail2ban-systemd-1.0.2-5.fc39.noarch from fedora requires fail2ban-server = 1.0.2-5.fc39, but none of the providers can be installed
  - package fail2ban-systemd-1.0.2-5.fc39.noarch from fedora-modular requires fail2ban-server = 1.0.2-5.fc39, but none of the providers can be installed
  - package fail2ban-systemd-1.0.2-5.fc39.noarch from updates-modular requires fail2ban-server = 1.0.2-5.fc39, but none of the providers can be installed
  - package fail2ban-systemd-1.0.2-5.fc39.noarch from updates-testing-modular requires fail2ban-server = 1.0.2-5.fc39, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from fedora requires python(abi) = 3.11, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from fedora-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from updates-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from updates-testing-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package python3-3.11.4-1.fc38.x86_64 from @System requires python3-libs(x86-64) = 3.11.4-1.fc38, but none of the providers can be installed
  - python3-libs-3.11.4-1.fc38.x86_64 from @System  does not belong to a distupgrade repository
  - fail2ban-systemd-1.0.2-3.fc38.noarch from @System  does not belong to a distupgrade repository
 Problem 3: problem with installed package sos-4.5.1-1.fc38.noarch
  - package sos-4.6.0-1.fc39.noarch from fedora requires python(abi) = 3.12, but none of the providers can be installed
  - package sos-4.6.0-1.fc39.noarch from fedora-modular requires python(abi) = 3.12, but none of the providers can be installed
  - package sos-4.6.0-1.fc39.noarch from updates-modular requires python(abi) = 3.12, but none of the providers can be installed
  - package sos-4.6.0-1.fc39.noarch from updates-testing-modular requires python(abi) = 3.12, but none of the providers can be installed
  - python3-3.12.0~rc1-1.fc39.i686 from updates-testing-modular  does not belong to a distupgrade repository
  - python3-3.12.0~rc1-1.fc39.i686 from updates-modular  does not belong to a distupgrade repository
  - python3-3.12.0~rc1-1.fc39.i686 from fedora-modular  does not belong to a distupgrade repository
  - python3-3.12.0~rc1-1.fc39.i686 from fedora  does not belong to a distupgrade repository
  - cannot install both python3-3.12.0~rc1-1.fc39.x86_64 from fedora and python3-3.11.4-1.fc38.x86_64 from @System
  - cannot install both python3-3.12.0~rc1-1.fc39.x86_64 from fedora-modular and python3-3.11.4-1.fc38.x86_64 from @System
  - cannot install both python3-3.12.0~rc1-1.fc39.x86_64 from updates-modular and python3-3.11.4-1.fc38.x86_64 from @System
  - cannot install both python3-3.12.0~rc1-1.fc39.x86_64 from updates-testing-modular and python3-3.11.4-1
.fc38.x86_64 from @System
  - problem with installed package fail2ban-sendmail-1.0.2-3.fc38.noarch
  - package fail2ban-sendmail-1.0.2-5.fc39.noarch from fedora requires fail2ban-server = 1.0.2-5.fc39, but none of the providers can be installed
  - package fail2ban-sendmail-1.0.2-5.fc39.noarch from fedora-modular requires fail2ban-server = 1.0.2-5.fc39, but none of the providers can be installed
  - package fail2ban-sendmail-1.0.2-5.fc39.noarch from updates-modular requires fail2ban-server = 1.0.2-5.fc39, but none of the providers can be installed
  - package fail2ban-sendmail-1.0.2-5.fc39.noarch from updates-testing-modular requires fail2ban-server = 1.0.2-5.fc39, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from fedora requires python(abi) = 3.11, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from fedora-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from updates-modular requires python(abi) = 3.11, but none of the providers can be installed
  - package fail2ban-server-1.0.2-5.fc39.noarch from updates-testing-modular requires python(abi) = 3.11, but none of the providers can be installed
  - fail2ban-sendmail-1.0.2-3.fc38.noarch from @System  does not belong to a distupgrade repository
  - sos-4.5.1-1.fc38.noarch from @System  does not belong to a distupgrade repository

F38 server #3:   Clean upgrade

F38 snowflake RPi3: Clean upgrade

- Solomon

[Adam Williamson]

On Fri, 2023-08-25 at 20:32 -0400, Solomon Peachy via devel wrote:
> On Wed, Aug 23, 2023 at 08:22:42PM +0200, Miroslav Suchý wrote:
> > Do you want to make Fedora 39 better? Please spend 1 minute of your time and try to run:
>
> I ran this on a bunch of my fleet, lots of problems, and they all seem 
> to be related to the Python 3.12 bump.

It's a lot of output, but not *so* many problems when you boil it down.

A lot of it is fail2ban, which is not working with Python 3.12 because
it uses asynchat , which has been removed in Python 3.12:

https://docs.python.org/3.12/whatsnew/3.12.html#removed

Upstream is aware of this and working on it, but it's not done yet:
https://github.com/fail2ban/fail2ban/issues/3487

so, there's not much we can do about this, unless we want to write the
port for them. (Not me! I don't volunteer!)

I suppose we could just vendor asynchat and asyncore back into
fail2ban, but that feels pretty ugly. Maybe worth doing in extremis if
upstream can't get it ported before F39 Final, since I think fail2ban
is quite popular?

openocd seems to not be building ATM:
https://bugzilla.redhat.com/show_bug.cgi?id=2226064
I think this is likely due to libgpiod getting a major bump (from 1.6
to 2.0). There's an upstream ticket on this:
https://sourceforge.net/p/openocd/tickets/306/
but last update from upstream was in 2021. pbrobinson pinged it in
March with no response. Again not much we can do here unless we want to
do the porting work for upstream.

PyDrive was retired nine months ago:
https://src.fedoraproject.org/rpms/PyDrive/c/17c7af2339900db6584b15b89c0be88...
it probably needs to be obsoleted as part of
https://bugzilla.redhat.com/show_bug.cgi?id=2233409 . I've added a
comment there.

python-pathtools is FTBFS:
https://bugzilla.redhat.com/show_bug.cgi?id=2226277
because it uses the imp module that was removed in Python 3.12. This is
a pretty common case, we've fixed several packages for this, but not
this one yet. It's using it for something pretty stupid, so I've done
an equally stupid patch to fix it:
https://bodhi.fedoraproject.org/updates/FEDORA-2023-9235b56665

There's some discussion about async-generator here:
https://bugzilla.redhat.com/show_bug.cgi?id=2220121
seems it may get retired (which would mean we'd need to obsolete it).

matrix-synapse has a bunch of test suite failures, it looks like:
https://kojipkgs.fedoraproject.org//work/tasks/8799/104998799/build.log
upstream seem to be working on this:
https://github.com/matrix-org/synapse/pull/16099
so I guess the next version or so might succeed, or the maintainer
could bump to 1.91.0rc1 and backport that PR if they're really keen...

I *think* that's everything in your list.

[Solomon Peachy]

On Fri, Aug 25, 2023 at 06:55:17PM -0700, Adam Williamson wrote:
> It's a lot of output, but not *so* many problems when you boil it down.

Yeah, it's ultimately another example (or four) of how Python is utterly 
worthless as a "stable" application platform.
> I suppose we could just vendor asynchat and asyncore back into
> fail2ban, but that feels pretty ugly. Maybe worth doing in extremis if
> upstream can't get it ported before F39 Final, since I think fail2ban
> is quite popular?

Everything is important to someone, but I would think that fail2ban 
would result in some serious teeth-gnashing if it got dropped.

- Solomon

[Samuel Sieb]

On 8/25/23 20:51, Solomon Peachy via devel wrote:
> On Fri, Aug 25, 2023 at 06:55:17PM -0700, Adam Williamson wrote:
> > It's a lot of output, but not *so* many problems when you boil it down.
>
> Yeah, it's ultimately another example (or four) of how Python is utterly
> worthless as a "stable" application platform.

No, it's a demonstration of applications that aren't being properly 
maintained when they're still using functions that have been deprecated 
for 6 releases which is also that many years.  Python core is very stable.

[Solomon Peachy]

On Fri, Aug 25, 2023 at 09:08:23PM -0700, Samuel Sieb wrote:
> No, it's a demonstration of applications that aren't being properly
> maintained when they're still using functions that have been deprecated for
> 6 releases which is also that many years.  Python core is very stable.

So... you're saying that the fact that *every* python release in the 
past decade carries backwards-incompatible core changes is somehow an 
indication of its "stability"?

(If you want "stability" in python you have to pin absolutely everything 
 in a per-applicaiton venv, including every [sub-]dependency and the 
 interpreter version.  And $deity help you if you need some 
 relatively-bleeding-edge modules or have dependencies with conflicting 
 version needs. I spent the majority of my time at $dayjob-1 keeping on 
 top of the constant CI failures caused by the turtles-all-the-way-down 
 dependencies changing out from under us)

If you want a platform that is actually stable, take perl.  They have an 
explicit policy of never breaking existing software even if it means 
carrying bugs forward indefinitely, and scripts/modules have to 
explicitly opt into behavioral changes.

I have twenty-year-old perl scripts that still work just fine, but in my 
experience, even couple-years-old python code most likely won't.

If perl is "write once, read nowhere" python is "write once, fix forever".

/rant

- Solomon

[Przemek Klosowski]

On 8/26/23 00:51, Solomon Peachy via devel wrote:
> I have twenty-year-old perl scripts that still work just fine, but in my
> experience, even couple-years-old python code most likely won't.

I love both perl and python, but have to say that perl stability is 
partly due to the fact that its development stalled at some point so 
that the current perl is 5.34  and Perl 5.0 was released in 1994.

I feel that this stasis is not necessarily so bad---not that perl is 
perfect, but it just works so well for short targeted data manipulation. 
Reminds me of the well know quote(1) : "If you don't want your 
environment/language to develop and improve, you have no heart;  if you 
insist on it constantly changing, you have no brain".

The downside of course is that perl is not getting much in the way of 
new tech like machine learning, AI/LLM, etc, and is not a good match for 
large projects because of too much of duck typing.

(1) "If you're not a liberal when you're 20, you have no heart. If 
you're not a conservative when you're 40, you have no head"---it's 
widely mis-attributed to Winston Churchill but he didn't use it apparently.

[Geraldo Simião Kutz]

Only this errors, none of them look like real problems:

Erro:
Problema 1: problema com o pacote instalado
telegram-desktop-4.8.4-3.fc38.x86_64
 - telegram-desktop-4.8.4-3.fc38.x86_64 from @System  does not belong to a
distupgrade repository
 - nothing provides qt6-qtbase(x86-64) = 6.5.1 needed by
telegram-desktop-4.8.4-2.fc39.x86_64 from rpmfusion-free
Problema 2: problema com o pacote instalado
igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64
 - package igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64 from @System
requires libprocps.so.8()(64bit), but none of the providers can be
installed
 - package igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64 from @System
requires libprocps.so.8(LIBPROCPS_0)(64bit), but none of the providers can
be installed
 - package igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64 from fedora
requires libprocps.so.8()(64bit), but none of the providers can be
installed
 - package igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64 from fedora
requires libprocps.so.8(LIBPROCPS_0)(64bit), but none of the providers can
be installed
 - package igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64 from
fedora-modular requires libprocps.so.8()(64bit), but none of the providers
can be installed
 - package igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64 from
fedora-modular requires libprocps.so.8(LIBPROCPS_0)(64bit), but none of the
providers can be installed
 - package igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64 from
updates-modular requires libprocps.so.8()(64bit), but none of the providers
can be installed
 - package igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64 from
updates-modular requires libprocps.so.8(LIBPROCPS_0)(64bit), but none of
the providers can be installed
 - package igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64 from
updates-testing-modular requires libprocps.so.8()(64bit), but none of the
providers can be installed
 - package igt-gpu-tools-1.26-3.20220508gitcffa5ff.fc38.x86_64 from
updates-testing-modular requires libprocps.so.8(LIBPROCPS_0)(64bit), but
none of the providers can be insta
lled
 - procps-ng-3.3.17-11.fc38.x86_64 from @System  does not belong to a
distupgrade repository
(tente adicionar '--skip-broken' para pular pacotes desinstaláveis)

Em qua., 23 de ago. de 2023 às 15:23, Miroslav Suchý 
escreveu:
> Do you want to make Fedora 39 better? Please spend 1 minute of your time
> and try to run:
>
> # Run this only if you use default Fedora modules
> # next time you run any DNF command default modules will be enabled again
> sudo dnf module reset '*'
>
> dnf --releasever=39 --setopt=module_platform_id=platform:f39 \
> --enablerepo=updates-testing \
> $(rpm -q fedora-repos-modular >/dev/null && echo
> --enablerepo=updates-testing-modular) \
> --assumeno distro-sync
>
> This command does not replace `dnf system-upgrade`, but it will reveal
> potential problems.
>
> You may also run `dnf upgrade` before running this command.
>
> The `--assumeno` will just test the transaction, but does not make the
> actual upgrade.
>
> In case you hit dependency issues, please report it against the
> appropriate package.
>
> Or against fedora-obsolete-packages if that package should be removed in
> Fedora 39. Please check existing reports against fedora-obsolete-packages
> first:
>
> https://red.ht/2kuBDPu
>
> and also there is already bunch of "Fails to install" (F39FailsToInstall)
> reports:
>
> https://bugzilla.redhat.com/buglist.cgi?bug_id=
> 2168845&bug_id_type=anddependson&format=tvp&list_id=12486533
>
> Two notes:
>
> you may want to run the same command with dnf5 to help test new dnf.
>
> this command found zero issues on my personal system - great work all
>
> everybody!
>
> Thank you
> Miroslav
> _______________________________________________
> devel mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue

[Gary Buhrmaster]

On Wed, Aug 23, 2023 at 6:23 PM Miroslav Suchý  wrote:
> this command found zero issues on my personal system - great work all everybody!

On my small handful of systems I found zero issues
(well, one issue on two systems with a 3rd party repo
(which was actually my own local repo, so hoisted on
my own petard since I had not yet rebuilt for F39 and
the various app/lib uplifts)).

Looks good to me.  Thanks.

[Luna Jernberg]

Did this on my Thinkpad Edge a couple of days ago, and it went fine :)

Den ons 23 aug. 2023 kl 20:23 skrev Miroslav Suchý :
> Do you want to make Fedora 39 better? Please spend 1 minute of your time and try to run:
>
> # Run this only if you use default Fedora modules
> # next time you run any DNF command default modules will be enabled again
> sudo dnf module reset '*'
>
> dnf --releasever=39 --setopt=module_platform_id=platform:f39 \
> --enablerepo=updates-testing \
> $(rpm -q fedora-repos-modular >/dev/null && echo --enablerepo=updates-testing-modular) \
> --assumeno distro-sync
>
> This command does not replace `dnf system-upgrade`, but it will reveal potential problems.
>
> You may also run `dnf upgrade` before running this command.
>
> The `--assumeno` will just test the transaction, but does not make the actual upgrade.
>
> In case you hit dependency issues, please report it against the appropriate package.
>
> Or against fedora-obsolete-packages if that package should be removed in Fedora 39. Please check existing reports against fedora-obsolete-packages first:
>
> https://red.ht/2kuBDPu
>
> and also there is already bunch of "Fails to install" (F39FailsToInstall) reports:
>
> https://bugzilla.redhat.com/buglist.cgi?bug_id=2168845&bug_id_type=andde...
>
> Two notes:
>
> you may want to run the same command with dnf5 to help test new dnf.
>
> this command found zero issues on my personal system - great work all everybody!
>
> Thank you
>
> Miroslav
> _______________________________________________
> devel mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Luna Jernberg]

well other then that i have to disable rpmfusion now when i think about it

Den mån 28 aug. 2023 kl 23:35 skrev Luna Jernberg :
> Did this on my Thinkpad Edge a couple of days ago, and it went fine :)
>
> Den ons 23 aug. 2023 kl 20:23 skrev Miroslav Suchý :
> > Do you want to make Fedora 39 better? Please spend 1 minute of your time and try to run:
> >
> > # Run this only if you use default Fedora modules
> > # next time you run any DNF command default modules will be enabled again
> > sudo dnf module reset '*'
> >
> > dnf --releasever=39 --setopt=module_platform_id=platform:f39 \
> > --enablerepo=updates-testing \
> > $(rpm -q fedora-repos-modular >/dev/null && echo --enablerepo=updates-testing-modular) \
> > --assumeno distro-sync
> >
> > This command does not replace `dnf system-upgrade`, but it will reveal potential problems.
> >
> > You may also run `dnf upgrade` before running this command.
> >
> > The `--assumeno` will just test the transaction, but does not make the actual upgrade.
> >
> > In case you hit dependency issues, please report it against the appropriate package.
> >
> > Or against fedora-obsolete-packages if that package should be removed in Fedora 39. Please check existing reports against fedora-obsolete-packages first:
> >
> > https://red.ht/2kuBDPu
> >
> > and also there is already bunch of "Fails to install" (F39FailsToInstall) reports:
> >
> > https://bugzilla.redhat.com/buglist.cgi?bug_id=2168845&bug_id_type=andde...
> >
> > Two notes:
> >
> > you may want to run the same command with dnf5 to help test new dnf.
> >
> > this command found zero issues on my personal system - great work all everybody!
> >
> > Thank you
> >
> > Miroslav
> > _______________________________________________
> > devel mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
> > 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/[e-mail]
> > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Marcin Juszkiewicz]

W dniu 23.08.2023 o 20:22, Miroslav Suchý pisze:
> Do you want to make Fedora 39 better? Please spend 1 minute of your time 
> and try to run:
>
> # Run this only if you use default Fedora modules
> # next time you run any DNF command default modules will be enabled again
> sudo dnf module reset '*'
>
> dnf --releasever=39 --setopt=module_platform_id=platform:f39 \
> --enablerepo=updates-testing \
> $(rpm -q fedora-repos-modular >/dev/null && echo 
> --enablerepo=updates-testing-modular) \
> --assumeno distro-sync

Problem 1: problem with installed package mesa-vdpau-drivers-freeworld-23.0.2-1.fc38.x86_64
   - mesa-vdpau-drivers-freeworld-23.0.2-1.fc38.x86_64 from @System  does not belong to a distupgrade repository
   - nothing provides mesa-filesystem(x86-64) = 23.1.5 needed by mesa-vdpau-drivers-freeworld-23.1.5-1.fc39.x86_64 from rpmfusion-free

That's rpmfusion so will be sorted out.

Problem 2: package ghc-data-array-byte-0.1.0.1-1.fc38.x86_64 from @System requires libHSarray-0.5.4.0-ghc9.2.6.so()(64bit), but none of the providers can be installed
   - ghc-array-0.5.4.0-133.fc38.x86_64 from @System  does not belong to a distupgrade repository
   - problem with installed package ghc-data-array-byte-0.1.0.1-1.fc38.x86_64

Looks like package got dropped in meantime.

Problem 3: package python3-PyDrive-1.3.1-21.fc37.noarch from @System requires python(abi) = 3.11, but none of the providers can be installed
   - python3-3.11.4-1.fc38.x86_64 from @System  does not belong to a distupgrade repository
   - problem with installed package python3-PyDrive-1.3.1-21.fc37.noarch

Already discussed, obsolete package.

Problem 4: problem with installed package python3-async-generator-1.10-16.fc38.noarch
   - package python3-async-generator-1.10-16.fc38.noarch from @System requires python(abi) = 3.11, but none of the providers can be installed
   - package python3-async-generator-1.10-16.fc38.noarch from fedora requires python(abi) = 3.11, but none of the providers can be installed
   - package python3-async-generator-1.10-16.fc38.noarch from updates-testing-modular requires python(abi) = 3.11, but none of the providers can be installed
   - package python3-3.11.4-1.fc38.x86_64 from @System requires python3-libs(x86-64) = 3.11.4-1.fc38, but none of the providers can be installed
   - python3-libs-3.11.4-1.fc38.x86_64 from @System  does not belong to a distupgrade repository

Also already discussed.

DNF5 managed to solve problems on it's own:

Transaction Summary:
  Installing:       47 packages
  Upgrading:      3803 packages
  Replacing:      3841 packages
  Removing:          7 packages
  Downgrading:      28 packages

Total size of inbound packages is 4 GiB. Need to download 4 GiB.
After this operation 669 MiB will be used (install 16 GiB, remove 16 GiB).

[Adam Williamson]

On Tue, 2023-08-29 at 10:33 +0200, Marcin Juszkiewicz wrote:
> Problem 2: package ghc-data-array-byte-0.1.0.1-1.fc38.x86_64 from @System requires libHSarray-0.5.4.0-ghc9.2.6.so()(64bit), but none of the providers can be installed
> ghc-array-0.5.4.0-133.fc38.x86_64 from @System  does not belong to a distupgrade repository
> problem with installed package ghc-data-array-byte-0.1.0.1-1.fc38.x86_64
>
> Looks like package got dropped in meantime.

Such packages ought to be obsoleted by something - if nothing else, by
fedora-obsolete-packages . You can file a bug or PR asking for it to be
added there.
> DNF5 managed to solve problems on it's own:
>
> Transaction Summary:
>   Installing:       47 packages
>   Upgrading:      3803 packages
>   Replacing:      3841 packages
>   Removing:          7 packages
>   Downgrading:      28 packages

This is likely because it defaults to `--allowerasing` behaviour? This
is kinda a controversial topic. GNOME Software also does this, and I
don't *love* it as it can result in people being surprised by packages
having disappeared on upgrade. ('allowerasing' means, basically, if a
package like this is blocking the transaction, just remove it).

[Michael Catanzaro]

On Tue, Aug 29 2023 at 08:26:42 AM -0700, Adam Williamson 
 wrote:
> This is likely because it defaults to `--allowerasing` behaviour? This
> is kinda a controversial topic. GNOME Software also does this, and I
> don't *love* it as it can result in people being surprised by packages
> having disappeared on upgrade. ('allowerasing' means, basically, if a
> package like this is blocking the transaction, just remove it).

GNOME Software warns exactly which packages would be removed by an 
upgrade, so there should be no surprises. (This is afaik the only place 
where packages are exposed in the UI. Normally Software only shows 
applications and plug-ins.)

Michael

[Marcin Juszkiewicz]

W dniu 29.08.2023 o 17:26, Adam Williamson pisze:
> On Tue, 2023-08-29 at 10:33 +0200, Marcin Juszkiewicz wrote:
> > Problem 2: package ghc-data-array-byte-0.1.0.1-1.fc38.x86_64 from @System requires libHSarray-0.5.4.0-ghc9.2.6.so()(64bit), but none of the providers can be installed
> >     - ghc-array-0.5.4.0-133.fc38.x86_64 from @System  does not belong to a distupgrade repository
> >     - problem with installed package ghc-data-array-byte-0.1.0.1-1.fc38.x86_64
> >
> > Looks like package got dropped in meantime.
>
> Such packages ought to be obsoleted by something - if nothing else, by
> fedora-obsolete-packages . You can file a bug or PR asking for it to be
> added there.

https://bugzilla.redhat.com/show_bug.cgi?id=2237365 reported.

[Sérgio Basto]

Error: 
 Problem 1: conflicting requests
  - package default-fonts-cjk-sans-4.0-8.fc39.noarch from fedora
requires google-noto-sans-cjk-vf-fonts, but none of the providers can
be installed
  - package default-fonts-cjk-sans-4.0-9.fc39.noarch from updates-
testing requires google-noto-sans-cjk-vf-fonts, but none of the
providers can be installed
 Problem 2: conflicting requests
  - package default-fonts-core-math-4.0-8.fc39.noarch from fedora
requires google-noto-sans-math-fonts, but none of the providers can be
installed
  - package default-fonts-core-math-4.0-9.fc39.noarch from updates-
testing requires google-noto-sans-math-fonts, but none of the providers
can be installed

On Wed, 2023-08-23 at 20:22 +0200, Miroslav Suchý wrote:
> Do you want to make Fedora 39 better? Please spend 1 minute of your
> time and try to run:
>  
>  # Run this only if you use default Fedora modules
>  # next time you run any DNF command default modules will be enabled
> again
>  sudo dnf module reset '*'
> dnf --releasever=39 --setopt=module_platform_id=platform:f39 \
>  --enablerepo=updates-testing \
>  $(rpm -q fedora-repos-modular >/dev/null && echo --
> enablerepo=updates-testing-modular) \
>  --assumeno distro-sync
>
> This command does not replace `dnf system-upgrade`, but it will
> reveal potential problems. 
> You may also run `dnf upgrade` before running this command.
>  
> The `--assumeno` will just test the transaction, but does not make
> the actual upgrade.
>
> In case you hit dependency issues, please report it against the
> appropriate package. 
> Or against fedora-obsolete-packages if that package should be removed
> in Fedora 39. Please check existing reports against fedora-obsolete-
> packages first:
>  https://red.ht/2kuBDPu
> and also there is already bunch of "Fails to install"
> (F39FailsToInstall) reports:
> https://bugzilla.redhat.com/buglist.cgi?bug_id=2168845&bug_id_type=andde...
>
> Two notes:
> you may want to run the same command with dnf5 to help test new
>
> dnf.
> this command found zero issues on my personal system - great work
>
> all everybody!
>
> Thank you
>  Miroslav 
> _______________________________________________
> devel mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue

[Adam Williamson]

On Sun, 2023-09-03 at 14:47 +0100, Sérgio Basto wrote:
> Error: 
>  Problem 1: conflicting requests
> package default-fonts-cjk-sans-4.0-8.fc39.noarch from fedora
>
> requires google-noto-sans-cjk-vf-fonts, but none of the providers can
> be installed
> package default-fonts-cjk-sans-4.0-9.fc39.noarch from updates-
>
> testing requires google-noto-sans-cjk-vf-fonts, but none of the
> providers can be installed
>  Problem 2: conflicting requests
> package default-fonts-core-math-4.0-8.fc39.noarch from fedora
>
> requires google-noto-sans-math-fonts, but none of the providers can be
> installed
> package default-fonts-core-math-4.0-9.fc39.noarch from updates-
>
> testing requires google-noto-sans-math-fonts, but none of the providers
> can be installed

Is there no more than this? The important question is *why* google-
noto-sans-cjk-vf-fonts and google-noto-sans-math-fonts can't be
installed...I have both installed on F39, so they're not just broken...

[Sérgio Basto]

On Sun, 2023-09-03 at 09:07 -0700, Adam Williamson wrote:
> On Sun, 2023-09-03 at 14:47 +0100, Sérgio Basto wrote:
> > Error: 
> >  Problem 1: conflicting requests
> >   - package default-fonts-cjk-sans-4.0-8.fc39.noarch from fedora
> > requires google-noto-sans-cjk-vf-fonts, but none of the providers
> > can
> > be installed
> >   - package default-fonts-cjk-sans-4.0-9.fc39.noarch from updates-
> > testing requires google-noto-sans-cjk-vf-fonts, but none of the
> > providers can be installed
> >  Problem 2: conflicting requests
> >   - package default-fonts-core-math-4.0-8.fc39.noarch from fedora
> > requires google-noto-sans-math-fonts, but none of the providers can
> > be
> > installed
> >   - package default-fonts-core-math-4.0-9.fc39.noarch from updates-
> > testing requires google-noto-sans-math-fonts, but none of the
> > providers
> > can be installed
>
> Is there no more than this? The important question is *why* google-
> noto-sans-cjk-vf-fonts and google-noto-sans-math-fonts can't be
> installed...I have both installed on F39, so they're not just
> broken...

yes only these 2 problems but I used dnf system-upgrade [1]
I have enabled updates-testing repo.
But upgrade went wrong , it hanged  , librpm is broken dnf is broken ,
my vm is almost unbootable, so I can't do more tests ...

But upgrade went wrong , it hanged  when was updatin rpm-libs  , now
librpm is broken, dnf is broken , my vm boot with many errors and
doesn't have graphics , only console  so I can't do more tests ...
sorry

[1]
dnf system-upgrade download --refresh --releasever=39 --allowerasing -y
> -- 
> Adam Williamson (he/him/his)
> Fedora QA
> Fedora Chat: @adamwill:fedora.im | Mastodon: @[e-mail]
> https://www.happyassassin.net
>
> devel mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue

[Jens-Ulrik Petersen]

On Thu, Aug 24, 2023 at 2:23 AM Miroslav Suchý  wrote:
:
> dnf --releasever=39 --setopt=module_platform_id=platform:f39 \
>
> --enablerepo=updates-testing \
> $(rpm -q fedora-repos-modular >/dev/null && echo
> --enablerepo=updates-testing-modular) \
> --assumeno distro-sync

So are the F39M modular repos empty?? (since I thought they were being
removed)
Maybe they have to stay around for F39 to allow smooth upgrades, is that
the point?

Jens

[Adam Williamson]

On Thu, 2023-09-07 at 13:05 +0800, Jens-Ulrik Petersen wrote:
> On Thu, Aug 24, 2023 at 2:23 AM Miroslav Suchý  wrote:
> :
> > dnf --releasever=39 --setopt=module_platform_id=platform:f39 \
> >
> > --enablerepo=updates-testing \
> > $(rpm -q fedora-repos-modular >/dev/null && echo
> > --enablerepo=updates-testing-modular) \
> > --assumeno distro-sync
>
> So are the F39M modular repos empty?? (since I thought they were being
> removed)
> Maybe they have to stay around for F39 to allow smooth upgrades, is that
> the point?

Yes, and yes. You won't gain anything by explicitly enabling the
updates-testing-modular repo, msuchy could probably drop that from his
test command.

[Zbigniew Jędrzejewski-Szmek]

I'm getting:

Transaction failed: Rpm transaction failed.
  - file /usr/lib64/libnode.so.115 from install of nodejs-libs-1:20.5.1-1.fc39.x86_64 conflicts with file from package nodejs20-libs-1:20.5.1-1.fc38.x86_64
  - file /usr/bin/node-20 from install of nodejs-1:20.5.1-1.fc39.x86_64 conflicts with file from package nodejs20-1:20.5.1-1.fc38.x86_64

I filed https://bugzilla.redhat.com/show_bug.cgi?id=2237882.

Zbyszek