Re: Donate 1 minute of your time to test upgrades from F31 to F32

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



What is supposed to happen with any packages that depend on python2 that are currently installed on the system? I know that the actual packages have been retired since python2 is retired now, but currently DNF is blocking the upgrade of the system (not just marking them for removal).

Here are the three errors I get:

Problem 2: package exaile-4.0.0-3.fc31.noarch requires python2-dbus, but none of the providers can be installed
  - python2-dbus-1.2.8-6.fc31.x86_64 does not belong to a distupgrade repository
  - problem with installed package exaile-4.0.0-3.fc31.noarch
 Problem 3: package system-config-keyboard-1.4.0-18.fc31.noarch requires python2-newt, but none of the providers can be installed
  - python2-newt-0.52.21-2.fc31.x86_64 does not belong to a distupgrade repository
  - problem with installed package system-config-keyboard-1.4.0-18.fc31.noarch
Problem 5: package wxPython-devel-3.0.2.0-26.fc31.noarch requires python2-wxpython = 3.0.2.0-26.fc31, but none of the providers can be installed
  - python2-wxpython-3.0.2.0-26.fc31.x86_64 does not belong to a distupgrade repository
  - problem with installed package wxPython-devel-3.0.2.0-26.fc31.noarch

-Ian

On Wed, Mar 4, 2020 at 3:26 PM Miroslav Suchý <msuchy@xxxxxxxxxx> wrote:
Do you want to make Fedora 32 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 '*'

  sudo dnf --releasever=32 --setopt=module_platform_id=platform:f32 \
    --enablerepo=updates-testing --enablerepo=updates-testing-modular \
    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.


If you get this prompt:

  ...
  Total download size: XXX M
  Is this ok [y/N]:

you can answer N and nothing happens, no need to test the actual upgrade.

But very likely you get some dependency problem now. In that case, please report it against the appropriate package. Or
against fedora-obsolete-packages if that package should be removed in Fedora 32. Please check existing reports first:
https://red.ht/2kuBDPu

Thank you

--
Miroslav Suchy, RHCA
Red Hat, Associate Manager ABRT/Copr, #brno, #fedora-buildsys
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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/devel@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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/devel@xxxxxxxxxxxxxxxxxxxxxxx

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux