Do you want to make Fedora 41 better? Please spend 1 minute of your time and try to run:
dnf --releasever=41 --enablerepo=updates-testing --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 40. Please check existing reports against fedora-obsolete-packages first:
and also there is already lots of "Fails to install" (F40FailsToInstall) reports:
One note:
* you may want to run the same command with dnf5 to help test new dnf. Do not forget to add --best otherwise DNF5 hides all problems.
For convenience here is the relevant part of Fedora Guidelines on renaming and replacing packages:
https://docs.fedoraproject.org/en-US/packaging-guidelines/#renaming-or-repla...
Thank you
Miroslav
I have three machines running F40; here are the results:
==== #1 ==== Error: Problem 1: package module-build-service-3.9.2-9.fc41.noarch from fedora requires python(abi) = 3.12, but none of the providers can be installed - problem with installed package module-build-service-3.9.2-9.fc40.noarch - python3-3.12.5-1.fc40.x86_64 from @System does not belong to a distupgrade repository - module-build-service-3.9.2-9.fc40.noarch from @System does not belong to a distupgrade repository Problem 2: problem with installed package python3-fedmsg-1.1.7-6.fc40.noarch - package python3-fedmsg-1.1.7-6.fc40.noarch from @System requires python3.12dist(arrow), but none of the providers can be installed - package python3-fedmsg-1.1.7-6.fc40.noarch from fedora requires python3.12dist(arrow), but none of the providers can be installed - python3-arrow-1.2.3-7.fc40.noarch from @System does not belong to a distupgrade repository
==== #2 ==== Error: Problem: package ghc-foldable1-classes-compat-0.1-4.fc40.x86_64 from @System requires libHSarray-0.5.4.0-ghc9.4.5.so()(64bit), but none of the providers can be installed - ghc-array-0.5.4.0-140.fc40.x86_64 from @System does not belong to a distupgrade repository - problem with installed package ghc-foldable1-classes-compat-0.1-4.fc40.x86_64
I also had issues with some wxGTK3 packages leftover from F37, but I guess if there was a time these should have been obsoleted, it was back in F38 days.
==== #3 ==== Two package downgrades: - postgresql: 16.3-7.fc40 -> 16.3-3.fc41 - postgresql-private-libs: 16.3-7.fc40 -> 16.3-3.fc41
On Mon, Sep 02, 2024 at 11:08:58AM -0000, Artur Frenszek-Iwicki wrote:
I have three machines running F40; here are the results:
==== #1 ==== Error: Problem 1: package module-build-service-3.9.2-9.fc41.noarch from fedora requires python(abi) = 3.12, but none of the providers can be installed
Will add to fedora-obsolete-packages.
==== #2 ==== Error: Problem: package ghc-foldable1-classes-compat-0.1-4.fc40.x86_64 from @System requires libHSarray-0.5.4.0-ghc9.4.5.so()(64bit), but none of the providers can be installed
That's already handled in https://bugzilla.redhat.com/show_bug.cgi?id=2315865.
I also had issues with some wxGTK3 packages leftover from F37, but I guess if there was a time these should have been obsoleted, it was back in F38 days.
It's possible that they didn't cause problems until now. Please report them so we can add them to f-o-p.
Zbyszek
On Mon, Sep 2, 2024 at 12:21 PM Miroslav Suchý msuchy@redhat.com wrote:
Do you want to make Fedora 41 better? Please spend 1 minute of your time and try to run:
dnf --releasever=41 --enablerepo=updates-testing --assumeno distro-syncThis 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 40. Please check existing reports against fedora-obsolete-packages first:
and also there is already lots of "Fails to install" (F40FailsToInstall) reports:
One note:
- you may want to run the same command with dnf5 to help test new dnf. Do not forget to add --best otherwise DNF5 hides all problems.
For convenience here is the relevant part of Fedora Guidelines on renaming and replacing packages:
https://docs.fedoraproject.org/en-US/packaging-guidelines/#renaming-or-repla...
The only issues I see on my system are these:
``` Downgrading: httpd x86_64 2.4.61-3.fc41 fedora 47 k httpd-core x86_64 2.4.61-3.fc41 fedora 1.4 M httpd-filesystem noarch 2.4.61-3.fc41 fedora 12 k httpd-tools x86_64 2.4.61-3.fc41 fedora 80 k mod_lua x86_64 2.4.61-3.fc41 fedora 58 k perl-Regexp-Pattern-License noarch 3.11.1-5.fc41 fedora 112 k wpa_supplicant x86_64 1:2.11-2.fc41 fedora 1.7 M ```
The http downgrade is weird - the 2.4.62-2 update corresponding to what I currently have on f40 should already be in the f41-updates-testing repos since a month ago, but apparently it's not?
The perl-Regexp-Pattern-License and wpa_supplicant downgrades appear to be just NVR downgrades with Release number not having been synced / bumped correctly between branches.
Fabio
On my system I get an exiv2/krita issue and a re2 issue:
``` Error: Problem 1: problem with installed package krita-5.2.2-7.fc40.x86_64 - package krita-5.2.2-11.fc41.x86_64 from fedora requires libexiv2.so.27()(64bit), but none of the providers can be installed - krita-5.2.2-7.fc40.x86_64 from @System does not belong to a distupgrade repository - exiv2-libs-0.27.6-7.fc40.x86_64 from @System does not belong to a distupgrade repository Problem 2: package python3-fb-re2-1.0.7-18.fc41.x86_64 from fedora requires libre2.so.9()(64bit), but none of the providers can be installed - problem with installed package python3-fb-re2-1.0.7-15.fc40.x86_64 - re2-1:20220601-19.fc40.x86_64 from @System does not belong to a distupgrade repository - python3-fb-re2-1.0.7-15.fc40.x86_64 from @System does not belong to a distupgrade repository Problem 3: cannot install both exiv2-libs-0.28.2-5.fc41.x86_64 from fedora and exiv2-libs-0.27.6-7.fc40.x86_64 from @System - package krita-libs-5.2.2-11.fc41.x86_64 from fedora requires libexiv2.so.27()(64bit), but none of the providers can be installed - package exiv2-0.28.2-5.fc41.x86_64 from fedora requires libexiv2.so.28()(64bit), but none of the providers can be installed - package exiv2-0.28.2-5.fc41.x86_64 from fedora requires exiv2-libs(x86-64) = 0.28.2-5.fc41, but none of the providers can be installed - problem with installed package krita-libs-5.2.2-7.fc40.x86_64 - problem with installed package exiv2-0.27.6-7.fc40.x86_64 - krita-libs-5.2.2-7.fc40.x86_64 from @System does not belong to a distupgrade repository - exiv2-0.27.6-7.fc40.x86_64 from @System does not belong to a distupgrade repository ```
On Mon, Sep 02, 2024 at 01:25:35PM +0200, Cristian Le via devel wrote:
On my system I get an exiv2/krita issue and a re2 issue:
Error: Problem 1: problem with installed package krita-5.2.2-7.fc40.x86_64 - package krita-5.2.2-11.fc41.x86_64 from fedora requires
I have krita-5.2.3-1.fc41.x86_64 here, so this seems to have been resolved.
Problem 3: cannot install both exiv2-libs-0.28.2-5.fc41.x86_64 from fedora and exiv2-libs-0.27.6-7.fc40.x86_64 from @System
This is caused by krita, seems resolved now.
Problem 2: package python3-fb-re2-1.0.7-18.fc41.x86_64 from fedora requires libre2.so.9()(64bit), but none of the providers can be installed - problem with installed package python3-fb-re2-1.0.7-15.fc40.x86_64 - re2-1:20220601-19.fc40.x86_64 from @System does not belong to a distupgrade repository - python3-fb-re2-1.0.7-15.fc40.x86_64 from @System does not belong to a distupgrade repository
I have re2-20240702-19.fc41.x86_64 here, so that seems to have been resolved too.
Zbyszek
I encountered the following problem:
``` Error: Problem 1: package cdn-utils-1.162-1.fc40eng.noarch from @System requires python(abi) = 3.12, but none of the providers can be installed - python3-3.12.3-2.fc40.x86_64 from @System does not belong to a distupgrade repository - problem with installed package cdn-utils-1.162-1.fc40eng.noarch Problem 2: package engproduct-cli-1.36-1.fc40eng.noarch from @System requires python3.12dist(requests), but none of the providers can be installed - python3-requests-2.31.0-3.fc40.noarch from @System does not belong to a distupgrade repository - problem with installed package engproduct-cli-1.36-1.fc40eng.noarch Problem 3: package pub-client-0.104.0-1.fc40eng.noarch from @System requires python3.12dist(decorator), but none of the providers can be installed - python3-decorator-5.1.1-9.fc40.noarch from @System does not belong to a distupgrade repository - problem with installed package pub-client-0.104.0-1.fc40eng.noarch Problem 4: package pulp-utils-1.27-1.fc40eng.noarch from @System requires python3.12dist(python-dateutil) >= 1.4.1, but none of the providers can be installed - python3-dateutil-1:2.8.2-13.fc40.noarch from @System does not belong to a distupgrade repository - problem with installed package pulp-utils-1.27-1.fc40eng.noarch Problem 5: package python-cdn_definitions-3.1.0-1.fc40eng.noarch from @System requires python3.12dist(frozendict), but none of the providers can be installed - python3-frozendict-2.3.10-3.fc40.noarch from @System does not belong to a distupgrade repository - problem with installed package python-cdn_definitions-3.1.0-1.fc40eng.noarch Problem 6: package python-pubtools-1.3.0-1.fc40eng.noarch from @System requires python3.12dist(pluggy), but none of the providers can be installed - python3-pluggy-1.3.0-3.fc40.noarch from @System does not belong to a distupgrade repository - problem with installed package python-pubtools-1.3.0-1.fc40eng.noarch Problem 7: package python-pubtools-pulplib-2.38.1-2.fc40eng.noarch from @System requires python3.12dist(attrs), but none of the providers can be installed - python3-attrs-23.2.0-4.fc40.noarch from @System does not belong to a distupgrade repository - problem with installed package python-pubtools-pulplib-2.38.1-2.fc40eng.noarch Problem 8: package python-pushcollector-1.3.0-1.fc40eng.noarch from @System requires python3.12dist(jsonschema), but none of the providers can be installed - python3-jsonschema-4.19.1-3.fc40.noarch from @System does not belong to a distupgrade repository - problem with installed package python-pushcollector-1.3.0-1.fc40eng.noarch Problem 9: package python-pushsource-2.41.0-1.fc40eng.noarch from @System requires python3.12dist(kobo), but none of the providers can be installed - python3-kobo-0.36.2-1.fc40.noarch from @System does not belong to a distupgrade repository - problem with installed package python-pushsource-2.41.0-1.fc40eng.noarch Problem 10: package python-ubiconfig-3.1.1-1.fc40eng.noarch from @System requires python3.12dist(pyyaml), but none of the providers can be installed - python3-pyyaml-6.0.1-14.fc40.x86_64 from @System does not belong to a distupgrade repository - problem with installed package python-ubiconfig-3.1.1-1.fc40eng.noarch Problem 11: package rcm-pa-tool-0.0.42-2.fc40eng.noarch from @System requires python3.12dist(iniparse), but none of the providers can be installed - python3-iniparse-0.5-8.fc40.noarch from @System does not belong to a distupgrade repository - problem with installed package rcm-pa-tool-0.0.42-2.fc40eng.noarch Problem 12: package rcm-repoquery-1.10-1.fc40eng.noarch from @System requires python3.12dist(six), but none of the providers can be installed - python3-six-1.16.0-14.fc40.noarch from @System does not belong to a distupgrade repository - problem with installed package rcm-repoquery-1.10-1.fc40eng.noarch Problem 13: package rhsm-tools-1.119-1.fc40eng.noarch from @System requires python3.12dist(defusedxml), but none of the providers can be installed - python3-defusedxml-0.7.1-12.fc40.noarch from @System does not belong to a distupgrade repository - problem with installed package rhsm-tools-1.119-1.fc40eng.noarch Problem 14: package python3-3.12.3-2.fc40.x86_64 from @System requires python3-libs(x86-64) = 3.12.3-2.fc40, but none of the providers can be installed - package python-exodus_config-1.1.3-1.fc40eng.noarch from @System requires python(abi) = 3.12, but none of the providers can be installed - python3-libs-3.12.3-2.fc40.x86_64 from @System does not belong to a distupgrade repository - problem with installed package python-exodus_config-1.1.3-1.fc40eng.noarch Problem 15: package python3-cairo-devel-1.25.1-5.fc41.x86_64 from fedora requires python3-devel, but none of the providers can be installed - package python3-devel-3.13.0~rc1-2.fc41.i686 from fedora conflicts with python3 < 3.13.0~rc1-2.fc41 provided by python3-3.12.3-2.fc40.x86_64 from @System - package python3-devel-3.13.0~rc1-2.fc41.x86_64 from fedora conflicts with python3 < 3.13.0~rc1-2.fc41 provided by python3-3.12.3-2.fc40.x86_64 from @System - package python3-devel-3.13.0~rc1-3.fc41.i686 from updates-testing conflicts with python3 < 3.13.0~rc1-3.fc41 provided by python3-3.12.3-2.fc40.x86_64 from @System - package python3-devel-3.13.0~rc1-3.fc41.x86_64 from updates-testing conflicts with python3 < 3.13.0~rc1-3.fc41 provided by python3-3.12.3-2.fc40.x86_64 from @System - problem with installed package python3-cairo-devel-1.25.1-3.fc40.x86_64 - package python-frozenlist2-1.0.0-1.fc40eng.noarch from @System requires python(abi) = 3.12, but none of the providers can be installed - python3-devel-3.12.3-2.fc40.x86_64 from @System does not belong to a distupgrade repository - python3-cairo-devel-1.25.1-3.fc40.x86_64 from @System does not belong to a distupgrade repository - problem with installed package python-frozenlist2-1.0.0-1.fc40eng.noarch
```
Somewhat messy for me:
Last metadata expiration check: 0:46:11 ago on Mon 02 Sep 2024 16:37:50 CEST. Error: Problem 1: package poco-pagecompiler-1.12.4-6.fc40.x86_64 from @System requires libPocoFoundation.so.94()(64bit), but none of the providers can be installed - poco-foundation-1.12.4-6.fc40.x86_64 from @System does not belong to a distupgrade repository - problem with installed package poco-pagecompiler-1.12.4-6.fc40.x86_64 Problem 2: problem with installed package docker-compose-1.29.2-12.fc40.noarch - package docker-compose-2.29.2-1.fc41.x86_64 from fedora conflicts with docker-compose-plugin provided by docker-compose-plugin-2.29.2-1.fc40.x86_64 from @System - docker-compose-1.29.2-12.fc40.noarch from @System does not belong to a distupgrade repository - problem with installed package docker-compose-plugin-2.29.2-1.fc40.x86_64 Problem 3: package qt5-qtwebengine-freeworld-5.15.17-1.fc41.x86_64 from rpmfusion-free requires libre2.so.9()(64bit), but none of the providers can be installed - problem with installed package qt5-qtwebengine-freeworld-5.15.17-1.fc40.x86_64 - re2-1:20220601-19.fc40.x86_64 from @System does not belong to a distupgrade repository - qt5-qtwebengine-freeworld-5.15.17-1.fc40.x86_64 from @System does not belong to a distupgrade repository Problem 4: cannot install both re2-1:20240702-18.fc41.x86_64 from fedora and re2-1:20220601-19.fc40.x86_64 from @System - package python3-fb-re2-1.0.7-18.fc41.x86_64 from fedora requires libre2.so.9()(64bit), but none of the providers can be installed - package libarrow-16.1.0-8.fc41.x86_64 from fedora requires libre2.so.11()(64bit), but none of the providers can be installed - problem with installed package python3-fb-re2-1.0.7-15.fc40.x86_64 - problem with installed package libarrow-15.0.2-5.fc40.x86_64 - python3-fb-re2-1.0.7-15.fc40.x86_64 from @System does not belong to a distupgrade repository - libarrow-15.0.2-5.fc40.x86_64 from @System does not belong to a distupgrade repository
--alec
To me, this looks a bit messy:
rror: Problem 1: package poco-pagecompiler-1.12.4-6.fc40.x86_64 from @System requires libPocoFoundation.so.94()(64bit), but none of the providers can be installed - poco-foundation-1.12.4-6.fc40.x86_64 from @System does not belong to a distupgrade repository - problem with installed package poco-pagecompiler-1.12.4-6.fc40.x86_64 Problem 2: problem with installed package docker-compose-1.29.2-12.fc40.noarch - package docker-compose-2.29.2-1.fc41.x86_64 from fedora conflicts with docker-compose-plugin provided by docker-compose-plugin-2.29.1-1.fc40.x86_64 from @System - docker-compose-1.29.2-12.fc40.noarch from @System does not belong to a distupgrade repository - problem with installed package docker-compose-plugin-2.29.1-1.fc40.x86_64 Problem 3: package qt5-qtwebengine-freeworld-5.15.17-1.fc41.x86_64 from rpmfusion-free requires libre2.so.9()(64bit), but none of the providers can be installed - problem with installed package qt5-qtwebengine-freeworld-5.15.17-1.fc40.x86_64 - re2-1:20220601-19.fc40.x86_64 from @System does not belong to a distupgrade repository - qt5-qtwebengine-freeworld-5.15.17-1.fc40.x86_64 from @System does not belong to a distupgrade repository Problem 4: cannot install both re2-1:20240702-18.fc41.x86_64 from fedora and re2-1:20220601-19.fc40.x86_64 from @System - package python3-fb-re2-1.0.7-18.fc41.x86_64 from fedora requires libre2.so.9()(64bit), but none of the providers can be installed - package libarrow-16.1.0-8.fc41.x86_64 from fedora requires libre2.so.11()(64bit), but none of the providers can be installed - problem with installed package python3-fb-re2-1.0.7-15.fc40.x86_64 - problem with installed package libarrow-15.0.2-5.fc40.x86_64 - python3-fb-re2-1.0.7-15.fc40.x86_64 from @System does not belong to a distupgrade repository - libarrow-15.0.2-5.fc40.x86_64 from @System does not belong to a distupgrade repository
--alec
On Mon, Sep 02, 2024 at 11:37:04AM -0000, Kanitha Chim wrote:
Error: Problem 1: package cdn-utils-1.162-1.fc40eng.noarch from @System requires python(abi) = 3.12, but none of the providers can be installed Problem 2: package engproduct-cli-1.36-1.fc40eng.noarch from @System requires python3.12dist(requests), but none of the providers can be installed Problem 3: package pub-client-0.104.0-1.fc40eng.noarch from @System requires python3.12dist(decorator), but none of the providers can be installed Problem 4: package pulp-utils-1.27-1.fc40eng.noarch from @System requires python3.12dist(python-dateutil) >= 1.4.1, but none of the providers can be installed Problem 5: package python-cdn_definitions-3.1.0-1.fc40eng.noarch from @System requires python3.12dist(frozendict), but none of the providers can be installed Problem 6: package python-pubtools-1.3.0-1.fc40eng.noarch from @System requires python3.12dist(pluggy), but none of the providers can be installed Problem 7: package python-pubtools-pulplib-2.38.1-2.fc40eng.noarch from @System requires python3.12dist(attrs), but none of the providers can be installed Problem 8: package python-pushcollector-1.3.0-1.fc40eng.noarch from @System requires python3.12dist(jsonschema), but none of the providers can be installed Problem 9: package python-pushsource-2.41.0-1.fc40eng.noarch from @System requires python3.12dist(kobo), but none of the providers can be installed Problem 10: package python-ubiconfig-3.1.1-1.fc40eng.noarch from @System requires python3.12dist(pyyaml), but none of the providers can be installed Problem 11: package rcm-pa-tool-0.0.42-2.fc40eng.noarch from @System requires python3.12dist(iniparse), but none of the providers can be installed Problem 12: package rcm-repoquery-1.10-1.fc40eng.noarch from @System requires python3.12dist(six), but none of the providers can be installed Problem 13: package rhsm-tools-1.119-1.fc40eng.noarch from @System requires python3.12dist(defusedxml), but none of the providers can be installed
'fc40eng' is not a fedora dist tag. Those packages are from somewhere else.
Problem 14: package python3-3.12.3-2.fc40.x86_64 from @System requires python3-libs(x86-64) = 3.12.3-2.fc40, but none of the providers can be installed
- package python-exodus_config-1.1.3-1.fc40eng.noarch from @System requires python(abi) = 3.12, but none of the providers can be installed
This does not seems to be a problem in Fedora.
Zbyszek
this is mine:
LANG=C sudo dnf --releasever=41 --enablerepo=updates-testing --assumeno distro-sync [sudo] password for hhlp: Updating Subscription Management repositories. Unable to read consumer identity
This system is not registered with an entitlement server. You can use subscription-manager to register.
balena-etcher 1.2 kB/s | 659 B 00:00 Hashicorp Stable - x86_64 555 B/s | 346 B 00:00 Errors during downloading metadata for repository 'hashicorp': - Status code: 404 for https://rpm.releases.hashicorp.com/fedora/41/x86_64/stable/repodata/repomd.x... (IP: 2600:9000:256f:7e00:18:566b:ecc0:93a1) Error: Failed to download metadata for repo 'hashicorp': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried keybase 10 kB/s | 3.5 kB 00:00 MySQL 8.4 LTS Community Server 19 B/s | 10 B 00:00 Errors during downloading metadata for repository 'mysql-8.4-lts-community': - Status code: 404 for http://repo.mysql.com/yum/mysql-8.4-community/fc/41/x86_64/repodata/repomd.x... (IP: 2a02:26f0:e0:298::1d68) Error: Failed to download metadata for repo 'mysql-8.4-lts-community': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried MySQL Connectors Community 18 B/s | 10 B 00:00 Errors during downloading metadata for repository 'mysql-connectors-community': - Status code: 404 for http://repo.mysql.com/yum/mysql-connectors-community/fc/41/x86_64/repodata/r... (IP: 2a02:26f0:e0:298::1d68) Error: Failed to download metadata for repo 'mysql-connectors-community': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried MySQL Tools 8.4 LTS Community 21 B/s | 10 B 00:00 Errors during downloading metadata for repository 'mysql-tools-8.4-lts-community': - Status code: 404 for http://repo.mysql.com/yum/mysql-tools-8.4-community/fc/41/x86_64/repodata/re... (IP: 2a02:26f0:e0:298::1d68) Error: Failed to download metadata for repo 'mysql-tools-8.4-lts-community': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried ProtonVPN Fedora Stable repository 531 B/s | 153 B 00:00 Errors during downloading metadata for repository 'protonvpn-fedora-stable': - Status code: 404 for https://repo.protonvpn.com/fedora-41-stable/repodata/repomd.xml (IP: 2606:4700:20::681a:523) Error: Failed to download metadata for repo 'protonvpn-fedora-stable': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried Ignoring repositories: hashicorp, mysql-8.4-lts-community, mysql-connectors-community, mysql-tools-8.4-lts-community, protonvpn-fedora-stable Error: Problem 1: package proton-vpn-gtk-app-4.4.4-1.fc40.noarch from @System requires python(abi) = 3.12, but none of the providers can be installed - python3-3.12.5-2.fc40.x86_64 from @System does not belong to a distupgrade repository - problem with installed package proton-vpn-gtk-app-4.4.4-1.fc40.noarch Problem 2: package python3-3.12.5-2.fc40.x86_64 from @System requires python3-libs(x86-64) = 3.12.5-2.fc40, but none of the providers can be installed - package python3-proton-core-0.2.0-1.fc40.noarch from @System requires python(abi) = 3.12, but none of the providers can be installed - python3-libs-3.12.5-2.fc40.x86_64 from @System does not belong to a distupgrade repository - problem with installed package python3-proton-core-0.2.0-1.fc40.noarch Problem 3: package qt5-qtwebengine-freeworld-5.15.17-1.fc41.x86_64 from rpmfusion-free requires libre2.so.9()(64bit), but none of the providers can be installed - problem with installed package qt5-qtwebengine-freeworld-5.15.17-1.fc40.x86_64 - re2-1:20220601-19.fc40.x86_64 from @System does not belong to a distupgrade repository - qt5-qtwebengine-freeworld-5.15.17-1.fc40.x86_64 from @System does not belong to a distupgrade repository Problem 4: package mysql-connector-odbc-8.0.37-1.fc41.x86_64 from fedora requires libmysqlclient.so.21()(64bit), but none of the providers can be installed - package mysql-connector-odbc-8.0.37-1.fc41.x86_64 from fedora requires libmysqlclient.so.21(libmysqlclient_21.0)(64bit), but none of the providers can be installed - problem with installed package mysql-connector-odbc-9.0.0-10.fc40.x86_64 - installed package mysql-community-libs-8.4.2-10.fc40.x86_64 obsoletes mysql-libs < 8.4.2-10.fc40 provided by mysql-libs-8.0.39-1.fc41.x86_64 from fedora - mysql-connector-odbc-9.0.0-10.fc40.x86_64 from @System does not belong to a distupgrade repository - problem with installed package mysql-community-libs-8.4.2-10.fc40.x86_64 Problem 5: package python3-numpy-f2py-1:1.26.4-8.fc41.x86_64 from fedora requires python3-devel, but none of the providers can be installed - package python3-devel-3.13.0~rc1-2.fc41.i686 from fedora conflicts with python3 < 3.13.0~rc1-2.fc41 provided by python3-3.12.5-2.fc40.x86_64 from @System - package python3-devel-3.13.0~rc1-2.fc41.x86_64 from fedora conflicts with python3 < 3.13.0~rc1-2.fc41 provided by python3-3.12.5-2.fc40.x86_64 from @System - package python3-devel-3.13.0~rc1-3.fc41.i686 from updates-testing conflicts with python3 < 3.13.0~rc1-3.fc41 provided by python3-3.12.5-2.fc40.x86_64 from @System - package python3-devel-3.13.0~rc1-3.fc41.x86_64 from updates-testing conflicts with python3 < 3.13.0~rc1-3.fc41 provided by python3-3.12.5-2.fc40.x86_64 from @System - problem with installed package python3-numpy-f2py-1:1.26.4-3.fc40.x86_64 - package python3-proton-keyring-linux-0.0.2-1.fc40.noarch from @System requires python(abi) = 3.12, but none of the providers can be installed - python3-numpy-f2py-1:1.26.4-3.fc40.x86_64 from @System does not belong to a distupgrade repository - python3-devel-3.12.5-2.fc40.x86_64 from @System does not belong to a distupgrade repository - problem with installed package python3-proton-keyring-linux-0.0.2-1.fc40.noarch Problem 6: package python3-crypt-r-3.13.1-3.fc41.x86_64 from fedora requires python(abi) = 3.13, but none of the providers can be installed - python3-3.13.0~rc1-2.fc41.i686 from fedora does not belong to a distupgrade repository - python3-3.13.0~rc1-3.fc41.i686 from updates-testing does not belong to a distupgrade repository - package anaconda-core-41.31-1.fc41.x86_64 from fedora requires python3-crypt-r, but none of the providers can be installed - cannot install both python3-3.13.0~rc1-2.fc41.x86_64 from fedora and python3-3.12.5-2.fc40.x86_64 from @System - cannot install both python3-3.13.0~rc1-3.fc41.x86_64 from updates-testing and python3-3.12.5-2.fc40.x86_64 from @System - problem with installed package anaconda-core-40.22.3-1.fc40.x86_64 - package python3-proton-keyring-linux-secretservice-0.0.2-1.fc40.noarch from @System requires python(abi) = 3.12, but none of the providers can be installed - anaconda-core-40.22.3-1.fc40.x86_64 from @System does not belong to a distupgrade repository - problem with installed package python3-proton-keyring-linux-secretservice-0.0.2-1.fc40.noarch Problem 7: cannot install both re2-1:20240702-18.fc41.x86_64 from fedora and re2-1:20220601-19.fc40.x86_64 from @System - package python3-fb-re2-1.0.7-18.fc41.x86_64 from fedora requires libre2.so.9()(64bit), but none of the providers can be installed - package grpc-1.48.4-41.fc41.x86_64 from fedora requires libre2.so.11()(64bit), but none of the providers can be installed - problem with installed package python3-fb-re2-1.0.7-15.fc40.x86_64 - problem with installed package grpc-1.48.4-34.fc40.x86_64 - python3-fb-re2-1.0.7-15.fc40.x86_64 from @System does not belong to a distupgrade repository - grpc-1.48.4-34.fc40.x86_64 from @System does not belong to a distupgrade repository Problem 8: package julia-1.11.0-6.beta1.fc41.x86_64 from fedora requires libcurl-full, but none of the providers can be installed - package libcurl-minimal-8.9.1-2.fc41.i686 from fedora conflicts with libcurl(x86-32) provided by libcurl-8.9.1-2.fc41.i686 from fedora - package libcurl-minimal-8.9.1-2.fc41.x86_64 from fedora conflicts with libcurl(x86-64) provided by libcurl-8.9.1-2.fc41.x86_64 from fedora - problem with installed package libcurl-minimal-8.6.0-10.fc40.i686 - problem with installed package libcurl-minimal-8.6.0-10.fc40.x86_64 - problem with installed package julia-1.11.0-9.beta1.fc40.x86_64 - libcurl-minimal-8.6.0-10.fc40.i686 from @System does not belong to a distupgrade repository - libcurl-minimal-8.6.0-10.fc40.x86_64 from @System does not belong to a distupgrade repository - julia-1.11.0-9.beta1.fc40.x86_64 from @System does not belong to a distupgrade repository Problem 9: package vapoursynth-libs-68-3.fc41.x86_64 from fedora requires libpython3.13.so.1.0()(64bit), but none of the providers can be installed - cannot install both python3-libs-3.13.0~rc1-2.fc41.x86_64 from fedora and python3-libs-3.12.5-2.fc40.x86_64 from @System - cannot install both python3-libs-3.13.0~rc1-3.fc41.x86_64 from updates-testing and python3-libs-3.12.5-2.fc40.x86_64 from @System - package python3-3.12.5-2.fc40.x86_64 from @System requires python3-libs(x86-64) = 3.12.5-2.fc40, but none of the providers can be installed - problem with installed package vapoursynth-libs-65-2.fc40.x86_64 - package python3-proton-vpn-api-core-0.32.2-1.fc40.noarch from @System requires python(abi) = 3.12, but none of the providers can be installed - vapoursynth-libs-65-2.fc40.x86_64 from @System does not belong to a distupgrade repository - problem with installed package python3-proton-vpn-api-core-0.32.2-1.fc40.noarch Problem 10: package unbound-libs-1.20.0-2.fc41.x86_64 from fedora requires libpython3.13.so.1.0()(64bit), but none of the providers can be installed - cannot install both python3-libs-3.13.0~rc1-2.fc41.x86_64 from fedora and python3-libs-3.12.5-2.fc40.x86_64 from @System - cannot install both python3-libs-3.13.0~rc1-3.fc41.x86_64 from updates-testing and python3-libs-3.12.5-2.fc40.x86_64 from @System - package python3-3.12.5-2.fc40.x86_64 from @System requires python3-libs(x86-64) = 3.12.5-2.fc40, but none of the providers can be installed - problem with installed package unbound-libs-1.20.0-1.fc40.x86_64 - package python3-proton-vpn-killswitch-network-manager-0.5.4-1.fc40.noarch from @System requires python(abi) = 3.12, but none of the providers can be installed - unbound-libs-1.20.0-1.fc40.x86_64 from @System does not belong to a distupgrade repository - problem with installed package python3-proton-vpn-killswitch-network-manager-0.5.4-1.fc40.noarch Problem 11: package unbound-libs-1.20.0-2.fc41.x86_64 from fedora requires libpython3.13.so.1.0()(64bit), but none of the providers can be installed - cannot install both python3-libs-3.13.0~rc1-2.fc41.x86_64 from fedora and python3-libs-3.12.5-2.fc40.x86_64 from @System - cannot install both python3-libs-3.13.0~rc1-3.fc41.x86_64 from updates-testing and python3-libs-3.12.5-2.fc40.x86_64 from @System - package python3-unbound-1.20.0-2.fc41.x86_64 from fedora requires unbound-libs(x86-64) = 1.20.0-2.fc41, but none of the providers can be installed - package python3-3.12.5-2.fc40.x86_64 from @System requires python3-libs(x86-64) = 3.12.5-2.fc40, but none of the providers can be installed - problem with installed package python3-unbound-1.20.0-1.fc40.x86_64 - package python3-proton-vpn-killswitch-network-manager-wireguard-0.1.4-1.fc40.noarch from @System requires python(abi) = 3.12, but none of the providers can be installed - python3-unbound-1.20.0-1.fc40.x86_64 from @System does not belong to a distupgrade repository - problem with installed package python3-proton-vpn-killswitch-network-manager-wireguard-0.1.4-1.fc40.noarch Problem 12: package unbound-libs-1.20.0-2.fc41.x86_64 from fedora requires libpython3.13.so.1.0()(64bit), but none of the providers can be installed - cannot install both python3-libs-3.13.0~rc1-2.fc41.x86_64 from fedora and python3-libs-3.12.5-2.fc40.x86_64 from @System - cannot install both python3-libs-3.13.0~rc1-3.fc41.x86_64 from updates-testing and python3-libs-3.12.5-2.fc40.x86_64 from @System - package unbound-anchor-1.20.0-2.fc41.x86_64 from fedora requires unbound-libs(x86-64) = 1.20.0-2.fc41, but none of the providers can be installed - package python3-3.12.5-2.fc40.x86_64 from @System requires python3-libs(x86-64) = 3.12.5-2.fc40, but none of the providers can be installed - problem with installed package unbound-anchor-1.20.0-1.fc40.x86_64 - package python3-proton-vpn-local-agent-0.10.0-1.fc40.x86_64 from @System requires python(abi) = 3.12, but none of the providers can be installed - unbound-anchor-1.20.0-1.fc40.x86_64 from @System does not belong to a distupgrade repository - problem with installed package python3-proton-vpn-local-agent-0.10.0-1.fc40.x86_64 Problem 13: package sudo-python-plugin-1.9.15-5.p5.fc41.x86_64 from fedora requires libpython3.13.so.1.0()(64bit), but none of the providers can be installed - cannot install both python3-libs-3.13.0~rc1-2.fc41.x86_64 from fedora and python3-libs-3.12.5-2.fc40.x86_64 from @System - cannot install both python3-libs-3.13.0~rc1-3.fc41.x86_64 from updates-testing and python3-libs-3.12.5-2.fc40.x86_64 from @System - package python3-3.12.5-2.fc40.x86_64 from @System requires python3-libs(x86-64) = 3.12.5-2.fc40, but none of the providers can be installed - problem with installed package sudo-python-plugin-1.9.15-2.p5.fc40.x86_64 - package python3-proton-vpn-logger-0.2.1-1.fc40.noarch from @System requires python(abi) = 3.12, but none of the providers can be installed - sudo-python-plugin-1.9.15-2.p5.fc40.x86_64 from @System does not belong to a distupgrade repository - problem with installed package python3-proton-vpn-logger-0.2.1-1.fc40.noarch Problem 14: package python3-qt5-base-5.15.10-9.fc41.x86_64 from fedora requires libpython3.13.so.1.0()(64bit), but none of the providers can be installed - cannot install both python3-libs-3.13.0~rc1-2.fc41.x86_64 from fedora and python3-libs-3.12.5-2.fc40.x86_64 from @System - cannot install both python3-libs-3.13.0~rc1-3.fc41.x86_64 from updates-testing and python3-libs-3.12.5-2.fc40.x86_64 from @System - package python3-3.12.5-2.fc40.x86_64 from @System requires python3-libs(x86-64) = 3.12.5-2.fc40, but none of the providers can be installed - problem with installed package python3-qt5-base-5.15.10-6.fc40.x86_64 - package python3-proton-vpn-network-manager-0.5.2-1.fc40.noarch from @System requires python(abi) = 3.12, but none of the providers can be installed - python3-qt5-base-5.15.10-6.fc40.x86_64 from @System does not belong to a distupgrade repository - problem with installed package python3-proton-vpn-network-manager-0.5.2-1.fc40.noarch Problem 15: package python3-qt5-base-5.15.10-9.fc41.x86_64 from fedora requires libpython3.13.so.1.0()(64bit), but none of the providers can be installed - cannot install both python3-libs-3.13.0~rc1-2.fc41.x86_64 from fedora and python3-libs-3.12.5-2.fc40.x86_64 from @System - cannot install both python3-libs-3.13.0~rc1-3.fc41.x86_64 from updates-testing and python3-libs-3.12.5-2.fc40.x86_64 from @System - package python3-qt5-5.15.10-9.fc41.x86_64 from fedora requires python3-qt5-base(x86-64) = 5.15.10-9.fc41, but none of the providers can be installed - package python3-3.12.5-2.fc40.x86_64 from @System requires python3-libs(x86-64) = 3.12.5-2.fc40, but none of the providers can be installed - problem with installed package python3-qt5-5.15.10-6.fc40.x86_64 - package python3-proton-vpn-network-manager-openvpn-0.1.0-1.fc40.noarch from @System requires python(abi) = 3.12, but none of the providers can be installed - python3-qt5-5.15.10-6.fc40.x86_64 from @System does not belong to a distupgrade repository - problem with installed package python3-proton-vpn-network-manager-openvpn-0.1.0-1.fc40.noarch Problem 16: package python3-qt5-base-5.15.10-9.fc41.x86_64 from fedora requires libpython3.13.so.1.0()(64bit), but none of the providers can be installed - package python3-qt5-5.15.10-9.fc41.x86_64 from fedora requires python3-qt5-base(x86-64) = 5.15.10-9.fc41, but none of the providers can be installed - cannot install both python3-libs-3.13.0~rc1-2.fc41.x86_64 from fedora and python3-libs-3.12.5-2.fc40.x86_64 from @System - cannot install both python3-libs-3.13.0~rc1-3.fc41.x86_64 from updates-testing and python3-libs-3.12.5-2.fc40.x86_64 from @System - package python3-qt5-webengine-5.15.6-8.fc41.x86_64 from fedora requires python3-qt5(x86-64), but none of the providers can be installed - package python3-qt5-5.15.10-6.fc40.x86_64 from @System requires python3-qt5-base(x86-64) = 5.15.10-6.fc40, but none of the providers can be installed - package python3-3.12.5-2.fc40.x86_64 from @System requires python3-libs(x86-64) = 3.12.5-2.fc40, but none of the providers can be installed - problem with installed package python3-qt5-webengine-5.15.6-6.fc40.x86_64 - package python3-qt5-base-5.15.10-6.fc40.x86_64 from @System requires python-qt5-rpm-macros = 5.15.10-6.fc40, but none of the providers can be installed - package python3-proton-vpn-network-manager-wireguard-0.4.1-1.fc40.noarch from @System requires python(abi) = 3.12, but none of the providers can be installed - python3-qt5-webengine-5.15.6-6.fc40.x86_64 from @System does not belong to a distupgrade repository - python-qt5-rpm-macros-5.15.10-6.fc40.noarch from @System does not belong to a distupgrade repository - problem with installed package python3-proton-vpn-network-manager-wireguard-0.4.1-1.fc40.noarch Problem 17: package python3-pyqt6-base-6.7.1-1.fc41.x86_64 from fedora requires libpython3.13.so.1.0()(64bit), but none of the providers can be installed - cannot install both python3-libs-3.13.0~rc1-2.fc41.x86_64 from fedora and python3-libs-3.12.5-2.fc40.x86_64 from @System - cannot install both python3-libs-3.13.0~rc1-3.fc41.x86_64 from updates-testing and python3-libs-3.12.5-2.fc40.x86_64 from @System - package python3-3.12.5-2.fc40.x86_64 from @System requires python3-libs(x86-64) = 3.12.5-2.fc40, but none of the providers can be installed - package proton-vpn-gtk-app-4.4.4-1.fc40.noarch from @System requires python(abi) = 3.12, but none of the providers can be installed - problem with installed package python3-pyqt6-base-6.7.0-5.fc40.x86_64 - package proton-vpn-gnome-desktop-0.4.0-1.fc40.noarch from @System requires proton-vpn-gtk-app, but none of the providers can be installed - python3-pyqt6-base-6.7.0-5.fc40.x86_64 from @System does not belong to a distupgrade repository - problem with installed package proton-vpn-gnome-desktop-0.4.0-1.fc40.noarch (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages)
El 2/9/24 a las 12:20, Miroslav Suchý escribió:
Do you want to make Fedora 41 better? Please spend 1 minute of your time and try to run:
dnf --releasever=41 --enablerepo=updates-testing --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 40. Please check existing reports against fedora-obsolete-packages first:
and also there is already lots of "Fails to install" (F40FailsToInstall) reports:
One note:
- you may want to run the same command with dnf5 to help test new dnf.
Do not forget to add --best otherwise DNF5 hides all problems.
For convenience here is the relevant part of Fedora Guidelines on renaming and replacing packages:
https://docs.fedoraproject.org/en-US/packaging-guidelines/#renaming-or-repla...
Thank you
Miroslav
On Mon, Sep 02, 2024 at 02:10:20PM +0200, H H L P wrote:
Problem 3: package qt5-qtwebengine-freeworld-5.15.17-1.fc41.x86_64 from rpmfusion-free requires libre2.so.9()(64bit), but none of the providers can be installed - problem with installed package qt5-qtwebengine-freeworld-5.15.17-1.fc40.x86_64 - re2-1:20220601-19.fc40.x86_64 from @System does not belong to a distupgrade repository - qt5-qtwebengine-freeworld-5.15.17-1.fc40.x86_64 from @System does not belong to a distupgrade repository
I only got this error with dnf. As this was due to RPM Fusion and seeing a discussion that maybe qt5-qtwebengine-freeworld is not so needed anymore (in https://bugzilla.rpmfusion.org/show_bug.cgi?id=7019) I just removed the package. After removing qt5-qtwebengine-freeworld: no errors.
dnf5 with --best gives me loads of errors; this while dnf no longer gives any errors. Seems related to having RPM Fusion repositories.
$ sudo dnf --releasever=41 --enablerepo=updates-testing --assumeno distro-sync Last metadata expiration check: 0:01:26 ago on Tue 03 Sep 2024 07:30:01 AM CDT. Error: Problem 1: problem with installed package signal-libringrtc-2.46.1-1.1.x86_64 - package signal-libringrtc-2.46.1-1.1.x86_64 from @System requires libabsl_strings.so.2401.0.0()(64bit), but none of the providers can be installed - package signal-libringrtc-2.46.1-1.1.x86_64 from @System requires libabsl_throw_delegate.so.2401.0.0()(64bit), but none of the providers can be installed - package signal-libringrtc-2.46.1-1.1.x86_64 from network_im_signal requires libabsl_strings.so.2401.0.0()(64bit), but none of the providers can be installed - package signal-libringrtc-2.46.1-1.1.x86_64 from network_im_signal requires libabsl_throw_delegate.so.2401.0.0()(64bit), but none of the providers can be installed - abseil-cpp-20240116.2-1.fc40.x86_64 from @System does not belong to a distupgrade repository Problem 2: problem with installed package nodejs-electron-30.4.0-2.3.x86_64 - package nodejs-electron-30.4.0-2.3.x86_64 from @System requires libabsl_cord.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from @System requires libabsl_cordz_info.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from @System requires libabsl_hash.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from @System requires libabsl_int128.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from @System requires libabsl_raw_hash_set.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from @System requires libabsl_raw_logging_internal.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from @System requires libabsl_spinlock_wait.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from @System requires libabsl_status.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from @System requires libabsl_statusor.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from @System requires libabsl_str_format_internal.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from @System requires libabsl_strings.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from @System requires libabsl_synchronization.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from @System requires libabsl_throw_delegate.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from @System requires libabsl_time.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from network_im_signal requires libabsl_cord.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from network_im_signal requires libabsl_cordz_info.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from network_im_signal requires libabsl_hash.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from network_im_signal requires libabsl_int128.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from network_im_signal requires libabsl_raw_hash_set.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from network_im_signal requires libabsl_raw_logging_internal.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from network_im_signal requires libabsl_spinlock_wait.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from network_im_signal requires libabsl_status.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from network_im_signal requires libabsl_statusor.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from network_im_signal requires libabsl_str_format_internal.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from network_im_signal requires libabsl_strings.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from network_im_signal requires libabsl_synchronization.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from network_im_signal requires libabsl_throw_delegate.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from network_im_signal requires libabsl_time.so.2401.0.0()(64bit), but none of the providers can be installed - cannot install both abseil-cpp-20240722.0-1.fc41.x86_64 from fedora and abseil-cpp-20240116.2-1.fc40.x86_64 from @System - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_synchronization.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_strings.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_hash.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_raw_hash_set.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_spinlock_wait.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_str_format_internal.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_raw_logging_internal.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_log_internal_check_op.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_log_internal_message.so.2407.0.0()(64bit), but none of the providers can be installed - problem with installed package re2-1:20220601-19.fc40.x86_64 - re2-1:20220601-19.fc40.x86_64 from @System does not belong to a distupgrade repository Problem 3: problem with installed package signal-desktop-7.22.1-1.1.x86_64 - package signal-desktop-7.22.1-1.1.x86_64 from @System requires signal-libringrtc(x86-64) = 2.46.1, but none of the providers can be installed - package signal-desktop-7.22.1-1.1.x86_64 from network_im_signal requires signal-libringrtc(x86-64) = 2.46.1, but none of the providers can be installed - package signal-libringrtc-2.46.1-1.1.x86_64 from @System requires libabsl_strings.so.2401.0.0()(64bit), but none of the providers can be installed - package signal-libringrtc-2.46.1-1.1.x86_64 from @System requires libabsl_throw_delegate.so.2401.0.0()(64bit), but none of the providers can be installed - package signal-libringrtc-2.46.1-1.1.x86_64 from network_im_signal requires libabsl_strings.so.2401.0.0()(64bit), but none of the providers can be installed - package signal-libringrtc-2.46.1-1.1.x86_64 from network_im_signal requires libabsl_throw_delegate.so.2401.0.0()(64bit), but none of the providers can be installed - cannot install both abseil-cpp-20240722.0-1.fc41.x86_64 from fedora and abseil-cpp-20240116.2-1.fc40.x86_64 from @System - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_synchronization.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_strings.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_hash.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_raw_hash_set.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_spinlock_wait.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_str_format_internal.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_raw_logging_internal.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_log_internal_check_op.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_log_internal_message.so.2407.0.0()(64bit), but none of the providers can be installed - package libarrow-16.1.0-8.fc41.x86_64 from fedora requires libre2.so.11()(64bit), but none of the providers can be installed - problem with installed package libarrow-15.0.2-5.fc40.x86_64 - libarrow-15.0.2-5.fc40.x86_64 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)
El 2/9/24 a las 12:20, Miroslav Suchý escribió:
Do you want to make Fedora 41 better? Please spend 1 minute of your time and try to run:
dnf --releasever=41 --enablerepo=updates-testing --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 40. Please check existing reports against fedora-obsolete-packages first:
and also there is already lots of "Fails to install" (F40FailsToInstall) reports: http://bit.ly/3TcO0Ng
One note:
* you may want to run the same command with dnf5 to help test new dnf. Do not forget to add --best otherwise DNF5 hides all problems.
For convenience here is the relevant part of Fedora Guidelines on renaming and replacing packages:
https://docs.fedoraproject.org/en-US/packaging-guidelines/#renaming-or-repla...
Thank you
Miroslav
It looks like most or all of these issues come from the third-party signal-libringrtc package, which I think must have come from https://download.opensuse.org/repositories/network:/im:/signal/Fedora_40/x86.... It would have to be rebuilt for Fedora 41. It doesn’t look like there is a https://download.opensuse.org/repositories/network:/im:/signal/Fedora_41/x86... yet.
On 9/3/24 8:32 AM, Globe Trotter via devel wrote:
$ sudo dnf --releasever=41 --enablerepo=updates-testing --assumeno distro-sync Last metadata expiration check: 0:01:26 ago on Tue 03 Sep 2024 07:30:01 AM CDT. Error: Problem 1: problem with installed package signal-libringrtc-2.46.1-1.1.x86_64 - package signal-libringrtc-2.46.1-1.1.x86_64 from @System requires libabsl_strings.so.2401.0.0()(64bit), but none of the providers can be installed - package signal-libringrtc-2.46.1-1.1.x86_64 from @System requires libabsl_throw_delegate.so.2401.0.0()(64bit), but none of the providers can be installed - package signal-libringrtc-2.46.1-1.1.x86_64 from network_im_signal requires libabsl_strings.so.2401.0.0()(64bit), but none of the providers can be installed - package signal-libringrtc-2.46.1-1.1.x86_64 from network_im_signal requires libabsl_throw_delegate.so.2401.0.0()(64bit), but none of the providers can be installed - abseil-cpp-20240116.2-1.fc40.x86_64 from @System does not belong to a distupgrade repository Problem 2: problem with installed package nodejs-electron-30.4.0-2.3.x86_64 - package nodejs-electron-30.4.0-2.3.x86_64 from @System requires libabsl_cord.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from @System requires libabsl_cordz_info.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from @System requires libabsl_hash.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from @System requires libabsl_int128.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from @System requires libabsl_raw_hash_set.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from @System requires libabsl_raw_logging_internal.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from @System requires libabsl_spinlock_wait.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from @System requires libabsl_status.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from @System requires libabsl_statusor.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from @System requires libabsl_str_format_internal.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from @System requires libabsl_strings.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from @System requires libabsl_synchronization.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from @System requires libabsl_throw_delegate.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from @System requires libabsl_time.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from network_im_signal requires libabsl_cord.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from network_im_signal requires libabsl_cordz_info.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from network_im_signal requires libabsl_hash.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from network_im_signal requires libabsl_int128.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from network_im_signal requires libabsl_raw_hash_set.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from network_im_signal requires libabsl_raw_logging_internal.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from network_im_signal requires libabsl_spinlock_wait.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from network_im_signal requires libabsl_status.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from network_im_signal requires libabsl_statusor.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from network_im_signal requires libabsl_str_format_internal.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from network_im_signal requires libabsl_strings.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from network_im_signal requires libabsl_synchronization.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from network_im_signal requires libabsl_throw_delegate.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from network_im_signal requires libabsl_time.so.2401.0.0()(64bit), but none of the providers can be installed - cannot install both abseil-cpp-20240722.0-1.fc41.x86_64 from fedora and abseil-cpp-20240116.2-1.fc40.x86_64 from @System - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_synchronization.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_strings.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_hash.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_raw_hash_set.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_spinlock_wait.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_str_format_internal.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_raw_logging_internal.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_log_internal_check_op.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_log_internal_message.so.2407.0.0()(64bit), but none of the providers can be installed - problem with installed package re2-1:20220601-19.fc40.x86_64 - re2-1:20220601-19.fc40.x86_64 from @System does not belong to a distupgrade repository Problem 3: problem with installed package signal-desktop-7.22.1-1.1.x86_64 - package signal-desktop-7.22.1-1.1.x86_64 from @System requires signal-libringrtc(x86-64) = 2.46.1, but none of the providers can be installed - package signal-desktop-7.22.1-1.1.x86_64 from network_im_signal requires signal-libringrtc(x86-64) = 2.46.1, but none of the providers can be installed - package signal-libringrtc-2.46.1-1.1.x86_64 from @System requires libabsl_strings.so.2401.0.0()(64bit), but none of the providers can be installed - package signal-libringrtc-2.46.1-1.1.x86_64 from @System requires libabsl_throw_delegate.so.2401.0.0()(64bit), but none of the providers can be installed - package signal-libringrtc-2.46.1-1.1.x86_64 from network_im_signal requires libabsl_strings.so.2401.0.0()(64bit), but none of the providers can be installed - package signal-libringrtc-2.46.1-1.1.x86_64 from network_im_signal requires libabsl_throw_delegate.so.2401.0.0()(64bit), but none of the providers can be installed - cannot install both abseil-cpp-20240722.0-1.fc41.x86_64 from fedora and abseil-cpp-20240116.2-1.fc40.x86_64 from @System - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_synchronization.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_strings.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_hash.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_raw_hash_set.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_spinlock_wait.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_str_format_internal.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_raw_logging_internal.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_log_internal_check_op.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_log_internal_message.so.2407.0.0()(64bit), but none of the providers can be installed - package libarrow-16.1.0-8.fc41.x86_64 from fedora requires libre2.so.11()(64bit), but none of the providers can be installed - problem with installed package libarrow-15.0.2-5.fc40.x86_64 - libarrow-15.0.2-5.fc40.x86_64 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)
El 2/9/24 a las 12:20, Miroslav Suchý escribió:
Do you want to make Fedora 41 better? Please spend 1 minute of your time and try to run:
dnf --releasever=41 --enablerepo=updates-testing --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 40. Please check existing reports against fedora-obsolete-packages first:
and also there is already lots of "Fails to install" (F40FailsToInstall) reports: http://bit.ly/3TcO0Ng
One note:
- you may want to run the same command with dnf5 to help test new dnf. Do not forget to add --best otherwise DNF5 hides all problems.
For convenience here is the relevant part of Fedora Guidelines on renaming and replacing packages:
https://docs.fedoraproject.org/en-US/packaging-guidelines/#renaming-or-repla...
Thank you
Miroslav
I have frustrations with bugzilla, and please, if you can, try the following sudo dnf/dnf5 install meld aisleriot
With every days F41 update the above crashes, and then... dnf update (always fails to fetch updates) Thanks in advance
Leslie Satenstein
On Wednesday, September 4, 2024 at 06:37:58 a.m. EDT, Ben Beasley code@musicinmybrain.net wrote:
It looks like most or all of these issues come from the third-party signal-libringrtc package, which I think must have come from https://download.opensuse.org/repositories/network:/im:/signal/Fedora_40/x86.... It would have to be rebuilt for Fedora 41. It doesn’t look like there is a https://download.opensuse.org/repositories/network:/im:/signal/Fedora_41/x86... yet.
On 9/3/24 8:32 AM, Globe Trotter via devel wrote:
$ sudo dnf --releasever=41 --enablerepo=updates-testing --assumeno distro-sync Last metadata expiration check: 0:01:26 ago on Tue 03 Sep 2024 07:30:01 AM CDT. Error: Problem 1: problem with installed package signal-libringrtc-2.46.1-1.1.x86_64 - package signal-libringrtc-2.46.1-1.1.x86_64 from @System requires libabsl_strings.so.2401.0.0()(64bit), but none of the providers can be installed - package signal-libringrtc-2.46.1-1.1.x86_64 from @System requires libabsl_throw_delegate.so.2401.0.0()(64bit), but none of the providers can be installed - package signal-libringrtc-2.46.1-1.1.x86_64 from network_im_signal requires libabsl_strings.so.2401.0.0()(64bit), but none of the providers can be installed - package signal-libringrtc-2.46.1-1.1.x86_64 from network_im_signal requires libabsl_throw_delegate.so.2401.0.0()(64bit), but none of the providers can be installed - abseil-cpp-20240116.2-1.fc40.x86_64 from @System does not belong to a distupgrade repository Problem 2: problem with installed package nodejs-electron-30.4.0-2.3.x86_64 - package nodejs-electron-30.4.0-2.3.x86_64 from @System requires libabsl_cord.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from @System requires libabsl_cordz_info.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from @System requires libabsl_hash.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from @System requires libabsl_int128.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from @System requires libabsl_raw_hash_set.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from @System requires libabsl_raw_logging_internal.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from @System requires libabsl_spinlock_wait.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from @System requires libabsl_status.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from @System requires libabsl_statusor.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from @System requires libabsl_str_format_internal.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from @System requires libabsl_strings.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from @System requires libabsl_synchronization.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from @System requires libabsl_throw_delegate.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from @System requires libabsl_time.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from network_im_signal requires libabsl_cord.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from network_im_signal requires libabsl_cordz_info.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from network_im_signal requires libabsl_hash.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from network_im_signal requires libabsl_int128.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from network_im_signal requires libabsl_raw_hash_set.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from network_im_signal requires libabsl_raw_logging_internal.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from network_im_signal requires libabsl_spinlock_wait.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from network_im_signal requires libabsl_status.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from network_im_signal requires libabsl_statusor.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from network_im_signal requires libabsl_str_format_internal.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from network_im_signal requires libabsl_strings.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from network_im_signal requires libabsl_synchronization.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from network_im_signal requires libabsl_throw_delegate.so.2401.0.0()(64bit), but none of the providers can be installed - package nodejs-electron-30.4.0-2.3.x86_64 from network_im_signal requires libabsl_time.so.2401.0.0()(64bit), but none of the providers can be installed - cannot install both abseil-cpp-20240722.0-1.fc41.x86_64 from fedora and abseil-cpp-20240116.2-1.fc40.x86_64 from @System - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_synchronization.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_strings.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_hash.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_raw_hash_set.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_spinlock_wait.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_str_format_internal.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_raw_logging_internal.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_log_internal_check_op.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_log_internal_message.so.2407.0.0()(64bit), but none of the providers can be installed - problem with installed package re2-1:20220601-19.fc40.x86_64 - re2-1:20220601-19.fc40.x86_64 from @System does not belong to a distupgrade repository Problem 3: problem with installed package signal-desktop-7.22.1-1.1.x86_64 - package signal-desktop-7.22.1-1.1.x86_64 from @System requires signal-libringrtc(x86-64) = 2.46.1, but none of the providers can be installed - package signal-desktop-7.22.1-1.1.x86_64 from network_im_signal requires signal-libringrtc(x86-64) = 2.46.1, but none of the providers can be installed - package signal-libringrtc-2.46.1-1.1.x86_64 from @System requires libabsl_strings.so.2401.0.0()(64bit), but none of the providers can be installed - package signal-libringrtc-2.46.1-1.1.x86_64 from @System requires libabsl_throw_delegate.so.2401.0.0()(64bit), but none of the providers can be installed - package signal-libringrtc-2.46.1-1.1.x86_64 from network_im_signal requires libabsl_strings.so.2401.0.0()(64bit), but none of the providers can be installed - package signal-libringrtc-2.46.1-1.1.x86_64 from network_im_signal requires libabsl_throw_delegate.so.2401.0.0()(64bit), but none of the providers can be installed - cannot install both abseil-cpp-20240722.0-1.fc41.x86_64 from fedora and abseil-cpp-20240116.2-1.fc40.x86_64 from @System - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_synchronization.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_strings.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_hash.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_raw_hash_set.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_spinlock_wait.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_str_format_internal.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_raw_logging_internal.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_log_internal_check_op.so.2407.0.0()(64bit), but none of the providers can be installed - package re2-1:20240702-18.fc41.x86_64 from fedora requires libabsl_log_internal_message.so.2407.0.0()(64bit), but none of the providers can be installed - package libarrow-16.1.0-8.fc41.x86_64 from fedora requires libre2.so.11()(64bit), but none of the providers can be installed - problem with installed package libarrow-15.0.2-5.fc40.x86_64 - libarrow-15.0.2-5.fc40.x86_64 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)
El 2/9/24 a las 12:20, Miroslav Suchý escribió:
Do you want to make Fedora 41 better? Please spend 1 minute of your time and try to run:
dnf --releasever=41 --enablerepo=updates-testing --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 40. Please check existing reports against fedora-obsolete-packages first:
and also there is already lots of "Fails to install" (F40FailsToInstall) reports: http://bit.ly/3TcO0Ng
One note:
- you may want to run the same command with dnf5 to help test new dnf. Do not forget to add --best otherwise DNF5 hides all problems.
For convenience here is the relevant part of Fedora Guidelines on renaming and replacing packages:
https://docs.fedoraproject.org/en-US/packaging-guidelines/#renaming-or-repla...
Thank you
Miroslav
Dne 04. 09. 24 v 15:36 Leslie Satenstein via devel napsal(a):
I have frustrations with bugzilla, and please, if you can, try the following
sudo dnf/dnf5 install meld aisleriot
With every days F41 update the above crashes, and then...
I think you need `meld-3.22.2-5.fc41` from `updates-testing` repo. IOW try:
~~~
$ dnf update --enable-repo=updates-testing
~~~
Vít
dnf update (always fails to fetch updates)
Thanks in advance
Leslie Satenstein
On Wednesday, September 4, 2024 at 06:37:58 a.m. EDT, Ben Beasley code@musicinmybrain.net wrote:
It looks like most or all of these issues come from the third-party signal-libringrtc package, which I think must have come from https://download.opensuse.org/repositories/network:/im:/signal/Fedora_40/x86....
It would have to be rebuilt for Fedora 41. It doesn’t look like there is a https://download.opensuse.org/repositories/network:/im:/signal/Fedora_41/x86...
yet.
On 9/3/24 8:32 AM, Globe Trotter via devel wrote:
$ sudo dnf --releasever=41 --enablerepo=updates-testing --assumeno
distro-sync
Last metadata expiration check: 0:01:26 ago on Tue 03 Sep 2024
07:30:01 AM CDT.
Error: Problem 1: problem with installed package
signal-libringrtc-2.46.1-1.1.x86_64
- package signal-libringrtc-2.46.1-1.1.x86_64 from @System
requires libabsl_strings.so.2401.0.0()(64bit), but none of the providers can be installed
- package signal-libringrtc-2.46.1-1.1.x86_64 from @System
requires libabsl_throw_delegate.so.2401.0.0()(64bit), but none of the providers can be installed
- package signal-libringrtc-2.46.1-1.1.x86_64 from
network_im_signal requires libabsl_strings.so.2401.0.0()(64bit), but none of the providers can be installed
- package signal-libringrtc-2.46.1-1.1.x86_64 from
network_im_signal requires libabsl_throw_delegate.so.2401.0.0()(64bit), but none of the providers can be installed
- abseil-cpp-20240116.2-1.fc40.x86_64 from @System does not
belong to a distupgrade repository
Problem 2: problem with installed package
nodejs-electron-30.4.0-2.3.x86_64
- package nodejs-electron-30.4.0-2.3.x86_64 from @System requires
libabsl_cord.so.2401.0.0()(64bit), but none of the providers can be installed
- package nodejs-electron-30.4.0-2.3.x86_64 from @System requires
libabsl_cordz_info.so.2401.0.0()(64bit), but none of the providers can be installed
- package nodejs-electron-30.4.0-2.3.x86_64 from @System requires
libabsl_hash.so.2401.0.0()(64bit), but none of the providers can be installed
- package nodejs-electron-30.4.0-2.3.x86_64 from @System requires
libabsl_int128.so.2401.0.0()(64bit), but none of the providers can be installed
- package nodejs-electron-30.4.0-2.3.x86_64 from @System requires
libabsl_raw_hash_set.so.2401.0.0()(64bit), but none of the providers can be installed
- package nodejs-electron-30.4.0-2.3.x86_64 from @System requires
libabsl_raw_logging_internal.so.2401.0.0()(64bit), but none of the providers can be installed
- package nodejs-electron-30.4.0-2.3.x86_64 from @System requires
libabsl_spinlock_wait.so.2401.0.0()(64bit), but none of the providers can be installed
- package nodejs-electron-30.4.0-2.3.x86_64 from @System requires
libabsl_status.so.2401.0.0()(64bit), but none of the providers can be installed
- package nodejs-electron-30.4.0-2.3.x86_64 from @System requires
libabsl_statusor.so.2401.0.0()(64bit), but none of the providers can be installed
- package nodejs-electron-30.4.0-2.3.x86_64 from @System requires
libabsl_str_format_internal.so.2401.0.0()(64bit), but none of the providers can be installed
- package nodejs-electron-30.4.0-2.3.x86_64 from @System requires
libabsl_strings.so.2401.0.0()(64bit), but none of the providers can be installed
- package nodejs-electron-30.4.0-2.3.x86_64 from @System requires
libabsl_synchronization.so.2401.0.0()(64bit), but none of the providers can be installed
- package nodejs-electron-30.4.0-2.3.x86_64 from @System requires
libabsl_throw_delegate.so.2401.0.0()(64bit), but none of the providers can be installed
- package nodejs-electron-30.4.0-2.3.x86_64 from @System requires
libabsl_time.so.2401.0.0()(64bit), but none of the providers can be installed
- package nodejs-electron-30.4.0-2.3.x86_64 from
network_im_signal requires libabsl_cord.so.2401.0.0()(64bit), but none of the providers can be installed
- package nodejs-electron-30.4.0-2.3.x86_64 from
network_im_signal requires libabsl_cordz_info.so.2401.0.0()(64bit), but none of the providers can be installed
- package nodejs-electron-30.4.0-2.3.x86_64 from
network_im_signal requires libabsl_hash.so.2401.0.0()(64bit), but none of the providers can be installed
- package nodejs-electron-30.4.0-2.3.x86_64 from
network_im_signal requires libabsl_int128.so.2401.0.0()(64bit), but none of the providers can be installed
- package nodejs-electron-30.4.0-2.3.x86_64 from
network_im_signal requires libabsl_raw_hash_set.so.2401.0.0()(64bit), but none of the providers can be installed
- package nodejs-electron-30.4.0-2.3.x86_64 from
network_im_signal requires libabsl_raw_logging_internal.so.2401.0.0()(64bit), but none of the providers can be installed
- package nodejs-electron-30.4.0-2.3.x86_64 from
network_im_signal requires libabsl_spinlock_wait.so.2401.0.0()(64bit), but none of the providers can be installed
- package nodejs-electron-30.4.0-2.3.x86_64 from
network_im_signal requires libabsl_status.so.2401.0.0()(64bit), but none of the providers can be installed
- package nodejs-electron-30.4.0-2.3.x86_64 from
network_im_signal requires libabsl_statusor.so.2401.0.0()(64bit), but none of the providers can be installed
- package nodejs-electron-30.4.0-2.3.x86_64 from
network_im_signal requires libabsl_str_format_internal.so.2401.0.0()(64bit), but none of the providers can be installed
- package nodejs-electron-30.4.0-2.3.x86_64 from
network_im_signal requires libabsl_strings.so.2401.0.0()(64bit), but none of the providers can be installed
- package nodejs-electron-30.4.0-2.3.x86_64 from
network_im_signal requires libabsl_synchronization.so.2401.0.0()(64bit), but none of the providers can be installed
- package nodejs-electron-30.4.0-2.3.x86_64 from
network_im_signal requires libabsl_throw_delegate.so.2401.0.0()(64bit), but none of the providers can be installed
- package nodejs-electron-30.4.0-2.3.x86_64 from
network_im_signal requires libabsl_time.so.2401.0.0()(64bit), but none of the providers can be installed
- cannot install both abseil-cpp-20240722.0-1.fc41.x86_64 from
fedora and abseil-cpp-20240116.2-1.fc40.x86_64 from @System
- package re2-1:20240702-18.fc41.x86_64 from fedora requires
libabsl_synchronization.so.2407.0.0()(64bit), but none of the providers can be installed
- package re2-1:20240702-18.fc41.x86_64 from fedora requires
libabsl_strings.so.2407.0.0()(64bit), but none of the providers can be installed
- package re2-1:20240702-18.fc41.x86_64 from fedora requires
libabsl_hash.so.2407.0.0()(64bit), but none of the providers can be installed
- package re2-1:20240702-18.fc41.x86_64 from fedora requires
libabsl_raw_hash_set.so.2407.0.0()(64bit), but none of the providers can be installed
- package re2-1:20240702-18.fc41.x86_64 from fedora requires
libabsl_spinlock_wait.so.2407.0.0()(64bit), but none of the providers can be installed
- package re2-1:20240702-18.fc41.x86_64 from fedora requires
libabsl_str_format_internal.so.2407.0.0()(64bit), but none of the providers can be installed
- package re2-1:20240702-18.fc41.x86_64 from fedora requires
libabsl_raw_logging_internal.so.2407.0.0()(64bit), but none of the providers can be installed
- package re2-1:20240702-18.fc41.x86_64 from fedora requires
libabsl_log_internal_check_op.so.2407.0.0()(64bit), but none of the providers can be installed
- package re2-1:20240702-18.fc41.x86_64 from fedora requires
libabsl_log_internal_message.so.2407.0.0()(64bit), but none of the providers can be installed
- problem with installed package re2-1:20220601-19.fc40.x86_64 - re2-1:20220601-19.fc40.x86_64 from @System does not belong to a
distupgrade repository
Problem 3: problem with installed package
signal-desktop-7.22.1-1.1.x86_64
- package signal-desktop-7.22.1-1.1.x86_64 from @System requires
signal-libringrtc(x86-64) = 2.46.1, but none of the providers can be installed
- package signal-desktop-7.22.1-1.1.x86_64 from network_im_signal
requires signal-libringrtc(x86-64) = 2.46.1, but none of the providers can be installed
- package signal-libringrtc-2.46.1-1.1.x86_64 from @System
requires libabsl_strings.so.2401.0.0()(64bit), but none of the providers can be installed
- package signal-libringrtc-2.46.1-1.1.x86_64 from @System
requires libabsl_throw_delegate.so.2401.0.0()(64bit), but none of the providers can be installed
- package signal-libringrtc-2.46.1-1.1.x86_64 from
network_im_signal requires libabsl_strings.so.2401.0.0()(64bit), but none of the providers can be installed
- package signal-libringrtc-2.46.1-1.1.x86_64 from
network_im_signal requires libabsl_throw_delegate.so.2401.0.0()(64bit), but none of the providers can be installed
- cannot install both abseil-cpp-20240722.0-1.fc41.x86_64 from
fedora and abseil-cpp-20240116.2-1.fc40.x86_64 from @System
- package re2-1:20240702-18.fc41.x86_64 from fedora requires
libabsl_synchronization.so.2407.0.0()(64bit), but none of the providers can be installed
- package re2-1:20240702-18.fc41.x86_64 from fedora requires
libabsl_strings.so.2407.0.0()(64bit), but none of the providers can be installed
- package re2-1:20240702-18.fc41.x86_64 from fedora requires
libabsl_hash.so.2407.0.0()(64bit), but none of the providers can be installed
- package re2-1:20240702-18.fc41.x86_64 from fedora requires
libabsl_raw_hash_set.so.2407.0.0()(64bit), but none of the providers can be installed
- package re2-1:20240702-18.fc41.x86_64 from fedora requires
libabsl_spinlock_wait.so.2407.0.0()(64bit), but none of the providers can be installed
- package re2-1:20240702-18.fc41.x86_64 from fedora requires
libabsl_str_format_internal.so.2407.0.0()(64bit), but none of the providers can be installed
- package re2-1:20240702-18.fc41.x86_64 from fedora requires
libabsl_raw_logging_internal.so.2407.0.0()(64bit), but none of the providers can be installed
- package re2-1:20240702-18.fc41.x86_64 from fedora requires
libabsl_log_internal_check_op.so.2407.0.0()(64bit), but none of the providers can be installed
- package re2-1:20240702-18.fc41.x86_64 from fedora requires
libabsl_log_internal_message.so.2407.0.0()(64bit), but none of the providers can be installed
- package libarrow-16.1.0-8.fc41.x86_64 from fedora requires
libre2.so.11()(64bit), but none of the providers can be installed
- problem with installed package libarrow-15.0.2-5.fc40.x86_64 - libarrow-15.0.2-5.fc40.x86_64 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)
El 2/9/24 a las 12:20, Miroslav Suchý escribió:
Do you want to make Fedora 41 better? Please spend 1 minute of your
time and try to run:
dnf --releasever=41 --enablerepo=updates-testing --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 40. Please check existing reports against fedora-obsolete-packages first:
and also there is already lots of "Fails to install"
(F40FailsToInstall) reports:
One note:
- you may want to run the same command with dnf5 to help test new
dnf. Do not forget to add --best otherwise DNF5 hides all problems.
For convenience here is the relevant part of Fedora Guidelines on
renaming and replacing packages:
https://docs.fedoraproject.org/en-US/packaging-guidelines/#renaming-or-repla...
Thank you
Miroslav
-- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
dnf --releasever=41 --enablerepo=updates-testing --assumeno distro-sync
Looks good (on an uptodate F40 system), just with an oddity: IIRC this package was manually installed, not sure why it is being removed:
Removing dependent packages: python3-jose noarch 3.3.0-29.fc40 @updates 250 k
Error: Problem 1: package wxGTK3-3.0.5.1-10.fc38.x86_64 from @System requires libtiff.so.5()(64bit), but none of the providers can be installed - package wxGTK3-3.0.5.1-10.fc38.x86_64 from @System requires libtiff.so.5(LIBTIFF_4.0)(64bit), but none of the providers can be installed - libtiff-4.6.0-2.fc40.x86_64 from @System does not belong to a distupgrade repository - problem with installed package wxGTK3-3.0.5.1-10.fc38.x86_64 Problem 2: package gimp-jxl-plugin-1:0.10.3-3.fc41.x86_64 from fedora requires libgimp-2.0.so.0()(64bit), but none of the providers can be installed - package gimp-jxl-plugin-1:0.10.3-3.fc41.x86_64 from fedora requires libgimpcolor-2.0.so.0()(64bit), but none of the providers can be installed - package gimp-jxl-plugin-1:0.10.3-3.fc41.x86_64 from fedora requires libgimpui-2.0.so.0()(64bit), but none of the providers can be installed - package gimp-jxl-plugin-1:0.10.3-3.fc41.x86_64 from fedora requires libgimpwidgets-2.0.so.0()(64bit), but none of the providers can be installed - problem with installed package gimp-jxl-plugin-1:0.8.3-1.fc40.x86_64 - gimp-libs-2:2.10.38-1.fc40.x86_64 from @System does not belong to a distupgrade repository - gimp-jxl-plugin-1:0.8.3-1.fc40.x86_64 from @System does not belong to a distupgrade repository Problem 3: package python3-fb-re2-1.0.7-18.fc41.x86_64 from fedora requires libre2.so.9()(64bit), but none of the providers can be installed - problem with installed package python3-fb-re2-1.0.7-15.fc40.x86_64 - re2-1:20220601-19.fc40.x86_64 from @System does not belong to a distupgrade repository - python3-fb-re2-1.0.7-15.fc40.x86_64 from @System does not belong to a distupgrade repository (try to add '--skip-broken' to skip uninstallable packages)
On 9/2/24 03:20, Miroslav Suchý wrote:
Do you want to make Fedora 41 better? Please spend 1 minute of your time and try to run:
dnf --releasever=41 --enablerepo=updates-testing --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 40. Please check existing reports against fedora-obsolete-packages first:
and also there is already lots of "Fails to install" (F40FailsToInstall) reports:
One note:
- you may want to run the same command with dnf5 to help test new dnf.
Do not forget to add --best otherwise DNF5 hides all problems.
For convenience here is the relevant part of Fedora Guidelines on renaming and replacing packages:
https://docs.fedoraproject.org/en-US/packaging-guidelines/#renaming-or-repla...
Thank you
Miroslav
On Mon, 2 Sep 2024 07:20:46 -0700, Pablo Sebastián Greco wrote:
Error: Problem 1: package wxGTK3-3.0.5.1-10.fc38.x86_64 from @System requires libtiff.so.5()(64bit), but none of the providers can be installed
The wxGTK3 package does not exist anymore in Fedora 39 and later.
File dead.package tells it's been replaced by wxGTK, but I see no Obsoletes tags. Possibly just the wording is ambiguous, and it doesn't *really* replace wxGTK3.
https://src.fedoraproject.org/rpms/wxGTK3/blob/rawhide/f/dead.package
Dne 02. 09. 24 v 7:52 odp. Michael Schwendt napsal(a):
Error: Problem 1: package wxGTK3-3.0.5.1-10.fc38.x86_64 from @System requires libtiff.so.5()(64bit), but none of the providers can be installed
The wxGTK3 package does not exist anymore in Fedora 39 and later.
File dead.package tells it's been replaced by wxGTK, but I see no Obsoletes tags. Possibly just the wording is ambiguous, and it doesn't really replace wxGTK3.
https://src.fedoraproject.org/rpms/wxGTK3/blob/rawhide/f/dead.package
Reported
https://src.fedoraproject.org/rpms/wxGTK/pull-request/4
On Mon, Sep 2, 2024 at 10:21 AM Miroslav Suchý msuchy@redhat.com wrote:
In case you hit dependency issues, please report it against the appropriate package.
The only problem I get is:
Error: Problem: package python3-fb-re2-1.0.7-18.fc41.x86_64 from fedora requires libre2.so.9()(64bit), but none of the providers can be installed - problem with installed package python3-fb-re2-1.0.7-15.fc40.x86_64 - re2-1:20220601-19.fc40.x86_64 from @System does not belong to a distupgrade repository - python3-fb-re2-1.0.7-15.fc40.x86_64 from @System does not belong to a distupgrade repository (try to add '--skip-broken' to skip uninstallable packages)
Which I think is a result of the recent libre2 soname bump that may still being worked on. Otherwise, looking good.
I think the correct solution here will be to build the “official” Python bindings in the re2 source distribution, which are actively maintained and which also provide a somewhat-compatible “import re2,” but are distributed on PyPI as google-re2 rather than fb-re2.
As the new maintainer of the re2 package in Fedora, I can do this at any time, but because the two packages would conflict, python-fb-re2 would need to be retired. I’ve been trying to get the consent of the python-fb-re2 maintainer, but so far there has been no response.
More details and supporting links are in https://bugzilla.redhat.com/show_bug.cgi?id=2260410.
On Mon, Sep 2, 2024, at 2:18 PM, Gary Buhrmaster wrote:
On Mon, Sep 2, 2024 at 10:21 AM Miroslav Suchý msuchy@redhat.com wrote:
In case you hit dependency issues, please report it against the appropriate package.
The only problem I get is:
Error: Problem: package python3-fb-re2-1.0.7-18.fc41.x86_64 from fedora requires libre2.so.9()(64bit), but none of the providers can be installed
- problem with installed package python3-fb-re2-1.0.7-15.fc40.x86_64
- re2-1:20220601-19.fc40.x86_64 from @System does not belong to a
distupgrade repository
- python3-fb-re2-1.0.7-15.fc40.x86_64 from @System does not belong
to a distupgrade repository (try to add '--skip-broken' to skip uninstallable packages)
Which I think is a result of the recent libre2 soname bump that may still being worked on. Otherwise, looking good. -- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
On 2.09.2024 12:20, Miroslav Suchý wrote:
Do you want to make Fedora 41 better? Please spend 1 minute of your time and try to run:
dnf --releasever=41 --enablerepo=updates-testing --assumeno distro-sync
I have several packages from RPMFusion so some problems (1, 3, 4, 7, 9, 10, 11) are related to it:
Problem 1: package ffmpeg-libs-6.1.2-2.fc40.x86_64 from @System requires libjxl.so.0.8()(64bit), but none of the providers can be installed - package ffmpeg-libs-6.1.2-2.fc40.x86_64 from @System requires libjxl.so.0.8(JXL_0)(64bit), but none of the providers can be installed - package ffmpeg-libs-6.1.2-2.fc40.x86_64 from @System requires libjxl_threads.so.0.8()(64bit), but none of the providers can be installed - package ffmpeg-libs-6.1.2-2.fc40.x86_64 from @System requires libjxl_threads.so.0.8(JXL_0)(64bit), but none of the providers can be installed - libjxl-1:0.8.3-1.fc40.x86_64 from @System does not belong to a distupgrade repository - problem with installed package ffmpeg-libs-6.1.2-2.fc40.x86_64
Problem 3: package mesa-vdpau-drivers-freeworld-24.1.6-1.fc40.x86_64 from @System requires mesa-filesystem(x86-64) = 24.1.6, but none of the providers can be installed - mesa-filesystem-24.1.6-1.fc40.x86_64 from @System does not belong to a distupgrade repository - problem with installed package mesa-vdpau-drivers-freeworld-24.1.6-1.fc40.x86_64
Problem 4: package python3-rpmfusion-cert-0.7.2-8.fc40.noarch from @System requires python(abi) = 3.12, but none of the providers can be installed - python3-3.12.5-1.fc40.x86_64 from @System does not belong to a distupgrade repository - problem with installed package python3-rpmfusion-cert-0.7.2-8.fc40.noarch
Problem 7: package rpmfusion-free-release-40-0.1.noarch from @System requires system-release(40), but none of the providers can be installed - fedora-release-40-39.noarch from @System does not belong to a distupgrade repository - problem with installed package rpmfusion-free-release-40-0.1.noarch
Problem 9: package ffmpeg-libs-6.1.2-2.fc40.x86_64 from @System requires libplacebo.so.338()(64bit), but none of the providers can be installed - package ffmpeg-6.1.2-2.fc40.x86_64 from @System requires ffmpeg-libs(x86-64) = 6.1.2-2.fc40, but none of the providers can be installed - libplacebo-6.338.2-1.fc40.x86_64 from @System does not belong to a distupgrade repository - problem with installed package ffmpeg-6.1.2-2.fc40.x86_64
Problem 10: package ffmpeg-libs-6.1.2-2.fc40.x86_64 from @System requires libvmaf.so.1()(64bit), but none of the providers can be installed - package libavdevice-6.1.2-2.fc40.x86_64 from @System requires ffmpeg-libs(x86-64) = 6.1.2-2.fc40, but none of the providers can be installed - libvmaf-2.3.0-7.fc40.x86_64 from @System does not belong to a distupgrade repository - problem with installed package libavdevice-6.1.2-2.fc40.x86_64
Problem 11: package python3-rpmfusion-cert-0.7.2-8.fc40.noarch from @System requires python(abi) = 3.12, but none of the providers can be installed - package python3-3.12.5-1.fc40.x86_64 from @System requires python3-libs(x86-64) = 3.12.5-1.fc40, but none of the providers can be installed - package rpmfusion-packager-0.7.2-8.fc40.noarch from @System requires python3-rpmfusion-cert, but none of the providers can be installed - python3-libs-3.12.5-1.fc40.x86_64 from @System does not belong to a distupgrade repository - problem with installed package rpmfusion-packager-0.7.2-8.fc40.noarch
Two are libtiff related:
Problem 12: package alizams-1.9.10-2.fc41.x86_64 from fedora requires libITKCommon-4.13.so.1()(64bit), but none of the providers can be installed - package alizams-1.9.10-2.fc41.x86_64 from fedora requires libITKStatistics-4.13.so.1()(64bit), but none of the providers can be installed - package alizams-1.9.10-2.fc41.x86_64 from fedora requires libITKTransform-4.13.so.1()(64bit), but none of the providers can be installed - package InsightToolkit-4.13.3-15.fc39.x86_64 from @System requires libtiff.so.5()(64bit), but none of the providers can be installed - package InsightToolkit-4.13.3-15.fc39.x86_64 from @System requires libtiff.so.5(LIBTIFF_4.0)(64bit), but none of the providers can be installed - package InsightToolkit-4.13.3-15.fc39.x86_64 from fedora requires libtiff.so.5()(64bit), but none of the providers can be installed - package InsightToolkit-4.13.3-15.fc39.x86_64 from fedora requires libtiff.so.5(LIBTIFF_4.0)(64bit), but none of the providers can be installed - problem with installed package alizams-1.9.9-2.fc40.x86_64 - libtiff-4.6.0-2.fc40.x86_64 from @System does not belong to a distupgrade repository - alizams-1.9.9-2.fc40.x86_64 from @System does not belong to a distupgrade repository
Problem 14: problem with installed package InsightToolkit-4.13.3-15.fc39.x86_64 - package InsightToolkit-4.13.3-15.fc39.x86_64 from @System requires libtiff.so.5()(64bit), but none of the providers can be installed - package InsightToolkit-4.13.3-15.fc39.x86_64 from @System requires libtiff.so.5(LIBTIFF_4.0)(64bit), but none of the providers can be installed - package InsightToolkit-4.13.3-15.fc39.x86_64 from fedora requires libtiff.so.5()(64bit), but none of the providers can be installed - package InsightToolkit-4.13.3-15.fc39.x86_64 from fedora requires libtiff.so.5(LIBTIFF_4.0)(64bit), but none of the providers can be installed - cannot install both libtiff-4.6.0-6.fc41.x86_64 from fedora and libtiff-4.6.0-2.fc40.x86_64 from @System - package libtiff-devel-4.6.0-6.fc41.x86_64 from fedora requires libtiff(x86-64) = 4.6.0-6.fc41, but none of the providers can be installed - problem with installed package libtiff-devel-4.6.0-2.fc40.x86_64 - libtiff-devel-4.6.0-2.fc40.x86_64 from @System does not belong to a distupgrade repository
Three are Python issues:
Problem 5: package rfpkg-1.27.3-1.fc40.noarch from @System requires python3.12dist(python-bugzilla), but none of the providers can be installed - python3-bugzilla-3.2.0-10.fc40.noarch from @System does not belong to a distupgrade repository - problem with installed package rfpkg-1.27.3-1.fc40.noarch
Problem 6: package rfpkgdb-cli-2.15.1-1.fc40.noarch from @System requires python3.12dist(beautifulsoup4), but none of the providers can be installed - python3-beautifulsoup4-4.12.3-3.fc40.noarch from @System does not belong to a distupgrade repository - problem with installed package rfpkgdb-cli-2.15.1-1.fc40.noarch
Problem 13: problem with installed package python3-devel-3.12.5-1.fc40.x86_64 - package python3-devel-3.13.0~rc1-2.fc41.x86_64 from fedora conflicts with python3 < 3.13.0~rc1-2.fc41 provided by python3-3.12.5-1.fc40.x86_64 from @System - package python3-devel-3.13.0~rc1-3.fc41.x86_64 from updates-testing conflicts with python3 < 3.13.0~rc1-3.fc41 provided by python3-3.12.5-1.fc40.x86_64 from @System - package python3-libusb1-3.1.0-1.fc41.noarch from fedora requires python(abi) = 3.12, but none of the providers can be installed - problem with installed package python3-libusb1-3.0.0-9.fc40.noarch - python3-libusb1-3.0.0-9.fc40.noarch from @System does not belong to a distupgrade repository - python3-devel-3.12.5-1.fc40.x86_64 from @System does not belong to a distupgrade repository
And the rest two:
Problem 2: package ghc-foldable1-classes-compat-0.1-4.fc40.x86_64 from @System requires libHSarray-0.5.4.0-ghc9.4.5.so()(64bit), but none of the providers can be installed - ghc-array-0.5.4.0-142.fc40.x86_64 from @System does not belong to a distupgrade repository - problem with installed package ghc-foldable1-classes-compat-0.1-4.fc40.x86_64
Problem 8: package fedora-release-40-39.noarch from @System requires fedora-release-common = 40-39, but none of the providers can be installed - package rpmfusion-nonfree-release-40-0.1.noarch from @System requires system-release(40), but none of the providers can be installed - fedora-release-common-40-39.noarch from @System does not belong to a distupgrade repository - problem with installed package rpmfusion-nonfree-release-40-0.1.noarch
You have some other issue as all those rpmfusion dep issues are bogus.
Marcin Juszkiewicz wrote:
On 2.09.2024 12:20, Miroslav Suchý wrote:
Do you want to make Fedora 41 better? Please spend 1 minute of your time and try to run: dnf --releasever=41 --enablerepo=updates-testing --assumeno distro-sync I have several packages from RPMFusion so some problems (1, 3, 4, 7,
9, 10, 11) are related to it: Problem 1: package ffmpeg-libs-6.1.2-2.fc40.x86_64 from @System requires libjxl.so.0.8()(64bit), but none of the providers can be installed
- package ffmpeg-libs-6.1.2-2.fc40.x86_64 from @System requires libjxl.so.0.8(JXL_0)(64bit), but none of the providers can be installed
- package ffmpeg-libs-6.1.2-2.fc40.x86_64 from @System requires libjxl_threads.so.0.8()(64bit), but none of the providers can be installed
- package ffmpeg-libs-6.1.2-2.fc40.x86_64 from @System requires libjxl_threads.so.0.8(JXL_0)(64bit), but none of the providers can be installed
- libjxl-1:0.8.3-1.fc40.x86_64 from @System does not belong to a distupgrade repository
- problem with installed package ffmpeg-libs-6.1.2-2.fc40.x86_64
Problem 3: package mesa-vdpau-drivers-freeworld-24.1.6-1.fc40.x86_64 from @System requires mesa-filesystem(x86-64) = 24.1.6, but none of the providers can be installed
- mesa-filesystem-24.1.6-1.fc40.x86_64 from @System does not belong to a distupgrade repository
- problem with installed package mesa-vdpau-drivers-freeworld-24.1.6-1.fc40.x86_64
Problem 4: package python3-rpmfusion-cert-0.7.2-8.fc40.noarch from @System requires python(abi) = 3.12, but none of the providers can be installed
- python3-3.12.5-1.fc40.x86_64 from @System does not belong to a distupgrade repository
- problem with installed package python3-rpmfusion-cert-0.7.2-8.fc40.noarch
Problem 7: package rpmfusion-free-release-40-0.1.noarch from @System requires system-release(40), but none of the providers can be installed
- fedora-release-40-39.noarch from @System does not belong to a distupgrade repository
- problem with installed package rpmfusion-free-release-40-0.1.noarch
Problem 9: package ffmpeg-libs-6.1.2-2.fc40.x86_64 from @System requires libplacebo.so.338()(64bit), but none of the providers can be installed
- package ffmpeg-6.1.2-2.fc40.x86_64 from @System requires ffmpeg-libs(x86-64) = 6.1.2-2.fc40, but none of the providers can be installed
- libplacebo-6.338.2-1.fc40.x86_64 from @System does not belong to a distupgrade repository
- problem with installed package ffmpeg-6.1.2-2.fc40.x86_64
Problem 10: package ffmpeg-libs-6.1.2-2.fc40.x86_64 from @System requires libvmaf.so.1()(64bit), but none of the providers can be installed
- package libavdevice-6.1.2-2.fc40.x86_64 from @System requires ffmpeg-libs(x86-64) = 6.1.2-2.fc40, but none of the providers can be installed
- libvmaf-2.3.0-7.fc40.x86_64 from @System does not belong to a distupgrade repository
- problem with installed package libavdevice-6.1.2-2.fc40.x86_64
Problem 11: package python3-rpmfusion-cert-0.7.2-8.fc40.noarch from @System requires python(abi) = 3.12, but none of the providers can be installed
- package python3-3.12.5-1.fc40.x86_64 from @System requires python3-libs(x86-64) = 3.12.5-1.fc40, but none of the providers can be installed
- package rpmfusion-packager-0.7.2-8.fc40.noarch from @System requires python3-rpmfusion-cert, but none of the providers can be installed
- python3-libs-3.12.5-1.fc40.x86_64 from @System does not belong to a distupgrade repository
- problem with installed package rpmfusion-packager-0.7.2-8.fc40.noarch
Two are libtiff related: Problem 12: package alizams-1.9.10-2.fc41.x86_64 from fedora requires libITKCommon-4.13.so.1()(64bit), but none of the providers can be installed
- package alizams-1.9.10-2.fc41.x86_64 from fedora requires libITKStatistics-4.13.so.1()(64bit), but none of the providers can be installed
- package alizams-1.9.10-2.fc41.x86_64 from fedora requires libITKTransform-4.13.so.1()(64bit), but none of the providers can be installed
- package InsightToolkit-4.13.3-15.fc39.x86_64 from @System requires libtiff.so.5()(64bit), but none of the providers can be installed
- package InsightToolkit-4.13.3-15.fc39.x86_64 from @System requires libtiff.so.5(LIBTIFF_4.0)(64bit), but none of the providers can be installed
- package InsightToolkit-4.13.3-15.fc39.x86_64 from fedora requires libtiff.so.5()(64bit), but none of the providers can be installed
- package InsightToolkit-4.13.3-15.fc39.x86_64 from fedora requires libtiff.so.5(LIBTIFF_4.0)(64bit), but none of the providers can be installed
- problem with installed package alizams-1.9.9-2.fc40.x86_64
- libtiff-4.6.0-2.fc40.x86_64 from @System does not belong to a distupgrade repository
- alizams-1.9.9-2.fc40.x86_64 from @System does not belong to a distupgrade repository
Problem 14: problem with installed package InsightToolkit-4.13.3-15.fc39.x86_64
- package InsightToolkit-4.13.3-15.fc39.x86_64 from @System requires libtiff.so.5()(64bit), but none of the providers can be installed
- package InsightToolkit-4.13.3-15.fc39.x86_64 from @System requires libtiff.so.5(LIBTIFF_4.0)(64bit), but none of the providers can be installed
- package InsightToolkit-4.13.3-15.fc39.x86_64 from fedora requires libtiff.so.5()(64bit), but none of the providers can be installed
- package InsightToolkit-4.13.3-15.fc39.x86_64 from fedora requires libtiff.so.5(LIBTIFF_4.0)(64bit), but none of the providers can be installed
- cannot install both libtiff-4.6.0-6.fc41.x86_64 from fedora and libtiff-4.6.0-2.fc40.x86_64 from @System
- package libtiff-devel-4.6.0-6.fc41.x86_64 from fedora requires libtiff(x86-64) = 4.6.0-6.fc41, but none of the providers can be installed
- problem with installed package libtiff-devel-4.6.0-2.fc40.x86_64
- libtiff-devel-4.6.0-2.fc40.x86_64 from @System does not belong to a distupgrade repository
Three are Python issues: Problem 5: package rfpkg-1.27.3-1.fc40.noarch from @System requires python3.12dist(python-bugzilla), but none of the providers can be installed
- python3-bugzilla-3.2.0-10.fc40.noarch from @System does not belong to a distupgrade repository
- problem with installed package rfpkg-1.27.3-1.fc40.noarch
Problem 6: package rfpkgdb-cli-2.15.1-1.fc40.noarch from @System requires python3.12dist(beautifulsoup4), but none of the providers can be installed
- python3-beautifulsoup4-4.12.3-3.fc40.noarch from @System does not belong to a distupgrade repository
- problem with installed package rfpkgdb-cli-2.15.1-1.fc40.noarch
Problem 13: problem with installed package python3-devel-3.12.5-1.fc40.x86_64
- package python3-devel-3.13.0~rc1-2.fc41.x86_64 from fedora conflicts with python3 < 3.13.0~rc1-2.fc41 provided by python3-3.12.5-1.fc40.x86_64 from @System
- package python3-devel-3.13.0~rc1-3.fc41.x86_64 from updates-testing conflicts with python3 < 3.13.0~rc1-3.fc41 provided by python3-3.12.5-1.fc40.x86_64 from @System
- package python3-libusb1-3.1.0-1.fc41.noarch from fedora requires python(abi) = 3.12, but none of the providers can be installed
- problem with installed package python3-libusb1-3.0.0-9.fc40.noarch
- python3-libusb1-3.0.0-9.fc40.noarch from @System does not belong to a distupgrade repository
- python3-devel-3.12.5-1.fc40.x86_64 from @System does not belong to a distupgrade repository
And the rest two: Problem 2: package ghc-foldable1-classes-compat-0.1-4.fc40.x86_64 from @System requires libHSarray-0.5.4.0-ghc9.4.5.so()(64bit), but none of the providers can be installed
- ghc-array-0.5.4.0-142.fc40.x86_64 from @System does not belong to a distupgrade repository
- problem with installed package ghc-foldable1-classes-compat-0.1-4.fc40.x86_64
Problem 8: package fedora-release-40-39.noarch from @System requires fedora-release-common = 40-39, but none of the providers can be installed
- package rpmfusion-nonfree-release-40-0.1.noarch from @System requires system-release(40), but none of the providers can be installed
- fedora-release-common-40-39.noarch from @System does not belong to a distupgrade repository
- problem with installed package rpmfusion-nonfree-release-40-0.1.noarch
Odd as i also had problems with RPMFusion but removed it and then it works, just updated 1.3GB of Fedora 40 updates on my test laptop and now downloading and installing 2.3GB of Fedora 41 pre release packages
Den tis 3 sep. 2024 kl 10:09 skrev Leigh Scott leigh123linux@gmail.com:
You have some other issue as all those rpmfusion dep issues are bogus.
Marcin Juszkiewicz wrote:
On 2.09.2024 12:20, Miroslav Suchý wrote:
Do you want to make Fedora 41 better? Please spend 1 minute of your time and try to run: dnf --releasever=41 --enablerepo=updates-testing --assumeno distro-sync I have several packages from RPMFusion so some problems (1, 3, 4, 7,
9, 10, 11) are related to it: Problem 1: package ffmpeg-libs-6.1.2-2.fc40.x86_64 from @System requires libjxl.so.0.8()(64bit), but none of the providers can be installed
- package ffmpeg-libs-6.1.2-2.fc40.x86_64 from @System requires libjxl.so.0.8(JXL_0)(64bit), but none of the providers can be installed
- package ffmpeg-libs-6.1.2-2.fc40.x86_64 from @System requires libjxl_threads.so.0.8()(64bit), but none of the providers can be installed
- package ffmpeg-libs-6.1.2-2.fc40.x86_64 from @System requires libjxl_threads.so.0.8(JXL_0)(64bit), but none of the providers can be installed
- libjxl-1:0.8.3-1.fc40.x86_64 from @System does not belong to a distupgrade repository
- problem with installed package ffmpeg-libs-6.1.2-2.fc40.x86_64
Problem 3: package mesa-vdpau-drivers-freeworld-24.1.6-1.fc40.x86_64 from @System requires mesa-filesystem(x86-64) = 24.1.6, but none of the providers can be installed
- mesa-filesystem-24.1.6-1.fc40.x86_64 from @System does not belong to a distupgrade repository
- problem with installed package mesa-vdpau-drivers-freeworld-24.1.6-1.fc40.x86_64
Problem 4: package python3-rpmfusion-cert-0.7.2-8.fc40.noarch from @System requires python(abi) = 3.12, but none of the providers can be installed
- python3-3.12.5-1.fc40.x86_64 from @System does not belong to a distupgrade repository
- problem with installed package python3-rpmfusion-cert-0.7.2-8.fc40.noarch
Problem 7: package rpmfusion-free-release-40-0.1.noarch from @System requires system-release(40), but none of the providers can be installed
- fedora-release-40-39.noarch from @System does not belong to a distupgrade repository
- problem with installed package rpmfusion-free-release-40-0.1.noarch
Problem 9: package ffmpeg-libs-6.1.2-2.fc40.x86_64 from @System requires libplacebo.so.338()(64bit), but none of the providers can be installed
- package ffmpeg-6.1.2-2.fc40.x86_64 from @System requires ffmpeg-libs(x86-64) = 6.1.2-2.fc40, but none of the providers can be installed
- libplacebo-6.338.2-1.fc40.x86_64 from @System does not belong to a distupgrade repository
- problem with installed package ffmpeg-6.1.2-2.fc40.x86_64
Problem 10: package ffmpeg-libs-6.1.2-2.fc40.x86_64 from @System requires libvmaf.so.1()(64bit), but none of the providers can be installed
- package libavdevice-6.1.2-2.fc40.x86_64 from @System requires ffmpeg-libs(x86-64) = 6.1.2-2.fc40, but none of the providers can be installed
- libvmaf-2.3.0-7.fc40.x86_64 from @System does not belong to a distupgrade repository
- problem with installed package libavdevice-6.1.2-2.fc40.x86_64
Problem 11: package python3-rpmfusion-cert-0.7.2-8.fc40.noarch from @System requires python(abi) = 3.12, but none of the providers can be installed
- package python3-3.12.5-1.fc40.x86_64 from @System requires python3-libs(x86-64) = 3.12.5-1.fc40, but none of the providers can be installed
- package rpmfusion-packager-0.7.2-8.fc40.noarch from @System requires python3-rpmfusion-cert, but none of the providers can be installed
- python3-libs-3.12.5-1.fc40.x86_64 from @System does not belong to a distupgrade repository
- problem with installed package rpmfusion-packager-0.7.2-8.fc40.noarch
Two are libtiff related: Problem 12: package alizams-1.9.10-2.fc41.x86_64 from fedora requires libITKCommon-4.13.so.1()(64bit), but none of the providers can be installed
- package alizams-1.9.10-2.fc41.x86_64 from fedora requires libITKStatistics-4.13.so.1()(64bit), but none of the providers can be installed
- package alizams-1.9.10-2.fc41.x86_64 from fedora requires libITKTransform-4.13.so.1()(64bit), but none of the providers can be installed
- package InsightToolkit-4.13.3-15.fc39.x86_64 from @System requires libtiff.so.5()(64bit), but none of the providers can be installed
- package InsightToolkit-4.13.3-15.fc39.x86_64 from @System requires libtiff.so.5(LIBTIFF_4.0)(64bit), but none of the providers can be installed
- package InsightToolkit-4.13.3-15.fc39.x86_64 from fedora requires libtiff.so.5()(64bit), but none of the providers can be installed
- package InsightToolkit-4.13.3-15.fc39.x86_64 from fedora requires libtiff.so.5(LIBTIFF_4.0)(64bit), but none of the providers can be installed
- problem with installed package alizams-1.9.9-2.fc40.x86_64
- libtiff-4.6.0-2.fc40.x86_64 from @System does not belong to a distupgrade repository
- alizams-1.9.9-2.fc40.x86_64 from @System does not belong to a distupgrade repository
Problem 14: problem with installed package InsightToolkit-4.13.3-15.fc39.x86_64
- package InsightToolkit-4.13.3-15.fc39.x86_64 from @System requires libtiff.so.5()(64bit), but none of the providers can be installed
- package InsightToolkit-4.13.3-15.fc39.x86_64 from @System requires libtiff.so.5(LIBTIFF_4.0)(64bit), but none of the providers can be installed
- package InsightToolkit-4.13.3-15.fc39.x86_64 from fedora requires libtiff.so.5()(64bit), but none of the providers can be installed
- package InsightToolkit-4.13.3-15.fc39.x86_64 from fedora requires libtiff.so.5(LIBTIFF_4.0)(64bit), but none of the providers can be installed
- cannot install both libtiff-4.6.0-6.fc41.x86_64 from fedora and libtiff-4.6.0-2.fc40.x86_64 from @System
- package libtiff-devel-4.6.0-6.fc41.x86_64 from fedora requires libtiff(x86-64) = 4.6.0-6.fc41, but none of the providers can be installed
- problem with installed package libtiff-devel-4.6.0-2.fc40.x86_64
- libtiff-devel-4.6.0-2.fc40.x86_64 from @System does not belong to a distupgrade repository
Three are Python issues: Problem 5: package rfpkg-1.27.3-1.fc40.noarch from @System requires python3.12dist(python-bugzilla), but none of the providers can be installed
- python3-bugzilla-3.2.0-10.fc40.noarch from @System does not belong to a distupgrade repository
- problem with installed package rfpkg-1.27.3-1.fc40.noarch
Problem 6: package rfpkgdb-cli-2.15.1-1.fc40.noarch from @System requires python3.12dist(beautifulsoup4), but none of the providers can be installed
- python3-beautifulsoup4-4.12.3-3.fc40.noarch from @System does not belong to a distupgrade repository
- problem with installed package rfpkgdb-cli-2.15.1-1.fc40.noarch
Problem 13: problem with installed package python3-devel-3.12.5-1.fc40.x86_64
- package python3-devel-3.13.0~rc1-2.fc41.x86_64 from fedora conflicts with python3 < 3.13.0~rc1-2.fc41 provided by python3-3.12.5-1.fc40.x86_64 from @System
- package python3-devel-3.13.0~rc1-3.fc41.x86_64 from updates-testing conflicts with python3 < 3.13.0~rc1-3.fc41 provided by python3-3.12.5-1.fc40.x86_64 from @System
- package python3-libusb1-3.1.0-1.fc41.noarch from fedora requires python(abi) = 3.12, but none of the providers can be installed
- problem with installed package python3-libusb1-3.0.0-9.fc40.noarch
- python3-libusb1-3.0.0-9.fc40.noarch from @System does not belong to a distupgrade repository
- python3-devel-3.12.5-1.fc40.x86_64 from @System does not belong to a distupgrade repository
And the rest two: Problem 2: package ghc-foldable1-classes-compat-0.1-4.fc40.x86_64 from @System requires libHSarray-0.5.4.0-ghc9.4.5.so()(64bit), but none of the providers can be installed
- ghc-array-0.5.4.0-142.fc40.x86_64 from @System does not belong to a distupgrade repository
- problem with installed package ghc-foldable1-classes-compat-0.1-4.fc40.x86_64
Problem 8: package fedora-release-40-39.noarch from @System requires fedora-release-common = 40-39, but none of the providers can be installed
- package rpmfusion-nonfree-release-40-0.1.noarch from @System requires system-release(40), but none of the providers can be installed
- fedora-release-common-40-39.noarch from @System does not belong to a distupgrade repository
- problem with installed package rpmfusion-nonfree-release-40-0.1.noarch
-- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Did run through a full update with dnf4 on my Fedora 40 i3 Spin install to 41 i3 spin (Pre Release) and nothing exploded on my ThinkPad Edge 0217A16 laptop
https://i.imgur.com/vReaIwy.png
Den tis 3 sep. 2024 kl 10:38 skrev Luna Jernberg droidbittin@gmail.com:
Odd as i also had problems with RPMFusion but removed it and then it works, just updated 1.3GB of Fedora 40 updates on my test laptop and now downloading and installing 2.3GB of Fedora 41 pre release packages
Den tis 3 sep. 2024 kl 10:09 skrev Leigh Scott leigh123linux@gmail.com:
You have some other issue as all those rpmfusion dep issues are bogus.
Marcin Juszkiewicz wrote:
On 2.09.2024 12:20, Miroslav Suchý wrote:
Do you want to make Fedora 41 better? Please spend 1 minute of your time and try to run: dnf --releasever=41 --enablerepo=updates-testing --assumeno distro-sync I have several packages from RPMFusion so some problems (1, 3, 4, 7,
9, 10, 11) are related to it: Problem 1: package ffmpeg-libs-6.1.2-2.fc40.x86_64 from @System requires libjxl.so.0.8()(64bit), but none of the providers can be installed
- package ffmpeg-libs-6.1.2-2.fc40.x86_64 from @System requires libjxl.so.0.8(JXL_0)(64bit), but none of the providers can be installed
- package ffmpeg-libs-6.1.2-2.fc40.x86_64 from @System requires libjxl_threads.so.0.8()(64bit), but none of the providers can be installed
- package ffmpeg-libs-6.1.2-2.fc40.x86_64 from @System requires libjxl_threads.so.0.8(JXL_0)(64bit), but none of the providers can be installed
- libjxl-1:0.8.3-1.fc40.x86_64 from @System does not belong to a distupgrade repository
- problem with installed package ffmpeg-libs-6.1.2-2.fc40.x86_64
Problem 3: package mesa-vdpau-drivers-freeworld-24.1.6-1.fc40.x86_64 from @System requires mesa-filesystem(x86-64) = 24.1.6, but none of the providers can be installed
- mesa-filesystem-24.1.6-1.fc40.x86_64 from @System does not belong to a distupgrade repository
- problem with installed package mesa-vdpau-drivers-freeworld-24.1.6-1.fc40.x86_64
Problem 4: package python3-rpmfusion-cert-0.7.2-8.fc40.noarch from @System requires python(abi) = 3.12, but none of the providers can be installed
- python3-3.12.5-1.fc40.x86_64 from @System does not belong to a distupgrade repository
- problem with installed package python3-rpmfusion-cert-0.7.2-8.fc40.noarch
Problem 7: package rpmfusion-free-release-40-0.1.noarch from @System requires system-release(40), but none of the providers can be installed
- fedora-release-40-39.noarch from @System does not belong to a distupgrade repository
- problem with installed package rpmfusion-free-release-40-0.1.noarch
Problem 9: package ffmpeg-libs-6.1.2-2.fc40.x86_64 from @System requires libplacebo.so.338()(64bit), but none of the providers can be installed
- package ffmpeg-6.1.2-2.fc40.x86_64 from @System requires ffmpeg-libs(x86-64) = 6.1.2-2.fc40, but none of the providers can be installed
- libplacebo-6.338.2-1.fc40.x86_64 from @System does not belong to a distupgrade repository
- problem with installed package ffmpeg-6.1.2-2.fc40.x86_64
Problem 10: package ffmpeg-libs-6.1.2-2.fc40.x86_64 from @System requires libvmaf.so.1()(64bit), but none of the providers can be installed
- package libavdevice-6.1.2-2.fc40.x86_64 from @System requires ffmpeg-libs(x86-64) = 6.1.2-2.fc40, but none of the providers can be installed
- libvmaf-2.3.0-7.fc40.x86_64 from @System does not belong to a distupgrade repository
- problem with installed package libavdevice-6.1.2-2.fc40.x86_64
Problem 11: package python3-rpmfusion-cert-0.7.2-8.fc40.noarch from @System requires python(abi) = 3.12, but none of the providers can be installed
- package python3-3.12.5-1.fc40.x86_64 from @System requires python3-libs(x86-64) = 3.12.5-1.fc40, but none of the providers can be installed
- package rpmfusion-packager-0.7.2-8.fc40.noarch from @System requires python3-rpmfusion-cert, but none of the providers can be installed
- python3-libs-3.12.5-1.fc40.x86_64 from @System does not belong to a distupgrade repository
- problem with installed package rpmfusion-packager-0.7.2-8.fc40.noarch
Two are libtiff related: Problem 12: package alizams-1.9.10-2.fc41.x86_64 from fedora requires libITKCommon-4.13.so.1()(64bit), but none of the providers can be installed
- package alizams-1.9.10-2.fc41.x86_64 from fedora requires libITKStatistics-4.13.so.1()(64bit), but none of the providers can be installed
- package alizams-1.9.10-2.fc41.x86_64 from fedora requires libITKTransform-4.13.so.1()(64bit), but none of the providers can be installed
- package InsightToolkit-4.13.3-15.fc39.x86_64 from @System requires libtiff.so.5()(64bit), but none of the providers can be installed
- package InsightToolkit-4.13.3-15.fc39.x86_64 from @System requires libtiff.so.5(LIBTIFF_4.0)(64bit), but none of the providers can be installed
- package InsightToolkit-4.13.3-15.fc39.x86_64 from fedora requires libtiff.so.5()(64bit), but none of the providers can be installed
- package InsightToolkit-4.13.3-15.fc39.x86_64 from fedora requires libtiff.so.5(LIBTIFF_4.0)(64bit), but none of the providers can be installed
- problem with installed package alizams-1.9.9-2.fc40.x86_64
- libtiff-4.6.0-2.fc40.x86_64 from @System does not belong to a distupgrade repository
- alizams-1.9.9-2.fc40.x86_64 from @System does not belong to a distupgrade repository
Problem 14: problem with installed package InsightToolkit-4.13.3-15.fc39.x86_64
- package InsightToolkit-4.13.3-15.fc39.x86_64 from @System requires libtiff.so.5()(64bit), but none of the providers can be installed
- package InsightToolkit-4.13.3-15.fc39.x86_64 from @System requires libtiff.so.5(LIBTIFF_4.0)(64bit), but none of the providers can be installed
- package InsightToolkit-4.13.3-15.fc39.x86_64 from fedora requires libtiff.so.5()(64bit), but none of the providers can be installed
- package InsightToolkit-4.13.3-15.fc39.x86_64 from fedora requires libtiff.so.5(LIBTIFF_4.0)(64bit), but none of the providers can be installed
- cannot install both libtiff-4.6.0-6.fc41.x86_64 from fedora and libtiff-4.6.0-2.fc40.x86_64 from @System
- package libtiff-devel-4.6.0-6.fc41.x86_64 from fedora requires libtiff(x86-64) = 4.6.0-6.fc41, but none of the providers can be installed
- problem with installed package libtiff-devel-4.6.0-2.fc40.x86_64
- libtiff-devel-4.6.0-2.fc40.x86_64 from @System does not belong to a distupgrade repository
Three are Python issues: Problem 5: package rfpkg-1.27.3-1.fc40.noarch from @System requires python3.12dist(python-bugzilla), but none of the providers can be installed
- python3-bugzilla-3.2.0-10.fc40.noarch from @System does not belong to a distupgrade repository
- problem with installed package rfpkg-1.27.3-1.fc40.noarch
Problem 6: package rfpkgdb-cli-2.15.1-1.fc40.noarch from @System requires python3.12dist(beautifulsoup4), but none of the providers can be installed
- python3-beautifulsoup4-4.12.3-3.fc40.noarch from @System does not belong to a distupgrade repository
- problem with installed package rfpkgdb-cli-2.15.1-1.fc40.noarch
Problem 13: problem with installed package python3-devel-3.12.5-1.fc40.x86_64
- package python3-devel-3.13.0~rc1-2.fc41.x86_64 from fedora conflicts with python3 < 3.13.0~rc1-2.fc41 provided by python3-3.12.5-1.fc40.x86_64 from @System
- package python3-devel-3.13.0~rc1-3.fc41.x86_64 from updates-testing conflicts with python3 < 3.13.0~rc1-3.fc41 provided by python3-3.12.5-1.fc40.x86_64 from @System
- package python3-libusb1-3.1.0-1.fc41.noarch from fedora requires python(abi) = 3.12, but none of the providers can be installed
- problem with installed package python3-libusb1-3.0.0-9.fc40.noarch
- python3-libusb1-3.0.0-9.fc40.noarch from @System does not belong to a distupgrade repository
- python3-devel-3.12.5-1.fc40.x86_64 from @System does not belong to a distupgrade repository
And the rest two: Problem 2: package ghc-foldable1-classes-compat-0.1-4.fc40.x86_64 from @System requires libHSarray-0.5.4.0-ghc9.4.5.so()(64bit), but none of the providers can be installed
- ghc-array-0.5.4.0-142.fc40.x86_64 from @System does not belong to a distupgrade repository
- problem with installed package ghc-foldable1-classes-compat-0.1-4.fc40.x86_64
Problem 8: package fedora-release-40-39.noarch from @System requires fedora-release-common = 40-39, but none of the providers can be installed
- package rpmfusion-nonfree-release-40-0.1.noarch from @System requires system-release(40), but none of the providers can be installed
- fedora-release-common-40-39.noarch from @System does not belong to a distupgrade repository
- problem with installed package rpmfusion-nonfree-release-40-0.1.noarch
-- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
On 3.09.2024 10:08, Leigh Scott wrote:
You have some other issue as all those rpmfusion dep issues are bogus.
Thanks for pointing it out. Sorted out rpmfusion issues.
Two problems left:
Problem 1: package alizams-1.9.10-2.fc41.x86_64 from fedora requires libITKCommon-4.13.so.1()(64bit), but none of the providers can be installed - package alizams-1.9.10-2.fc41.x86_64 from fedora requires libITKStatistics-4.13.so.1()(64bit), but none of the providers can be installed - package alizams-1.9.10-2.fc41.x86_64 from fedora requires libITKTransform-4.13.so.1()(64bit), but none of the providers can be installed - package InsightToolkit-4.13.3-15.fc39.x86_64 from @System requires libtiff.so.5()(64bit), but none of the providers can be installed - package InsightToolkit-4.13.3-15.fc39.x86_64 from @System requires libtiff.so.5(LIBTIFF_4.0)(64bit), but none of the providers can be installed - package InsightToolkit-4.13.3-15.fc39.x86_64 from fedora requires libtiff.so.5()(64bit), but none of the providers can be installed - package InsightToolkit-4.13.3-15.fc39.x86_64 from fedora requires libtiff.so.5(LIBTIFF_4.0)(64bit), but none of the providers can be installed - problem with installed package alizams-1.9.9-2.fc40.x86_64 - libtiff-4.6.0-2.fc40.x86_64 from @System does not belong to a distupgrade repository - alizams-1.9.9-2.fc40.x86_64 from @System does not belong to a distupgrade repository
Problem 2: problem with installed package InsightToolkit-4.13.3-15.fc39.x86_64 - package InsightToolkit-4.13.3-15.fc39.x86_64 from @System requires libtiff.so.5()(64bit), but none of the providers can be installed - package InsightToolkit-4.13.3-15.fc39.x86_64 from @System requires libtiff.so.5(LIBTIFF_4.0)(64bit), but none of the providers can be installed - package InsightToolkit-4.13.3-15.fc39.x86_64 from fedora requires libtiff.so.5()(64bit), but none of the providers can be installed - package InsightToolkit-4.13.3-15.fc39.x86_64 from fedora requires libtiff.so.5(LIBTIFF_4.0)(64bit), but none of the providers can be installed - cannot install both libtiff-4.6.0-6.fc41.x86_64 from fedora and libtiff-4.6.0-2.fc40.x86_64 from @System - package libtiff-devel-4.6.0-6.fc41.x86_64 from fedora requires libtiff(x86-64) = 4.6.0-6.fc41, but none of the providers can be installed - problem with installed package libtiff-devel-4.6.0-2.fc40.x86_64 - libtiff-devel-4.6.0-2.fc40.x86_64 from @System does not belong to a distupgrade repository
On Wed, Sep 04, 2024 at 11:23:34AM +0200, Marcin Juszkiewicz wrote:
On 3.09.2024 10:08, Leigh Scott wrote:
You have some other issue as all those rpmfusion dep issues are bogus.
Thanks for pointing it out. Sorted out rpmfusion issues.
Two problems left:
Problem 1: package alizams-1.9.10-2.fc41.x86_64 from fedora requires libITKCommon-4.13.so.1()(64bit), but none of the providers can be installed
- package alizams-1.9.10-2.fc41.x86_64 from fedora requires libITKStatistics-4.13.so.1()(64bit), but none of the providers can be installed
- package alizams-1.9.10-2.fc41.x86_64 from fedora requires libITKTransform-4.13.so.1()(64bit), but none of the providers can be installed
- package InsightToolkit-4.13.3-15.fc39.x86_64 from @System requires libtiff.so.5()(64bit), but none of the providers can be installed
- package InsightToolkit-4.13.3-15.fc39.x86_64 from @System requires libtiff.so.5(LIBTIFF_4.0)(64bit), but none of the providers can be installed
- package InsightToolkit-4.13.3-15.fc39.x86_64 from fedora requires libtiff.so.5()(64bit), but none of the providers can be installed
- package InsightToolkit-4.13.3-15.fc39.x86_64 from fedora requires libtiff.so.5(LIBTIFF_4.0)(64bit), but none of the providers can be installed
- problem with installed package alizams-1.9.9-2.fc40.x86_64
- libtiff-4.6.0-2.fc40.x86_64 from @System does not belong to a distupgrade repository
- alizams-1.9.9-2.fc40.x86_64 from @System does not belong to a distupgrade repository
Problem 2: problem with installed package InsightToolkit-4.13.3-15.fc39.x86_64
- package InsightToolkit-4.13.3-15.fc39.x86_64 from @System requires libtiff.so.5()(64bit), but none of the providers can be installed
- package InsightToolkit-4.13.3-15.fc39.x86_64 from @System requires libtiff.so.5(LIBTIFF_4.0)(64bit), but none of the providers can be installed
- package InsightToolkit-4.13.3-15.fc39.x86_64 from fedora requires libtiff.so.5()(64bit), but none of the providers can be installed
- package InsightToolkit-4.13.3-15.fc39.x86_64 from fedora requires libtiff.so.5(LIBTIFF_4.0)(64bit), but none of the providers can be installed
- cannot install both libtiff-4.6.0-6.fc41.x86_64 from fedora and libtiff-4.6.0-2.fc40.x86_64 from @System
- package libtiff-devel-4.6.0-6.fc41.x86_64 from fedora requires libtiff(x86-64) = 4.6.0-6.fc41, but none of the providers can be installed
- problem with installed package libtiff-devel-4.6.0-2.fc40.x86_64
- libtiff-devel-4.6.0-2.fc40.x86_64 from @System does not belong to a distupgrade repository
The first problem is caused by the second. The second is because InsightToolkit-4.13.3-15.fc39 was the last successful build. We need to either build it or retire: 2260959 InsightToolkit: FTBFS in Fedora rawhide/f40 2300545 InsightToolkit: FTBFS in Fedora rawhide/f41 2301800 F41FailsToInstall: InsightToolkit
Zbyszek
In my case on two boxes I went all the way, actually did the upgrade.
Somewhat boringly it just worked in both cases.
-- Ian Laurie FAS: nixuser | IRC: nixuser TZ: Australia/Sydney
On Mon, Sep 2, 2024 at 10:21 AM Miroslav Suchý msuchy@redhat.com wrote:
Do you want to make Fedora 41 better? Please spend 1 minute of your time
and try to run:
dnf --releasever=41 --enablerepo=updates-testing --assumeno
distro-sync
I got this:
Error: Problem 1: package ghc-foldable1-classes-compat-0.1-4.fc40.x86_64 from @System requires libHSarray-0.5.4.0-ghc9.4.5.so()(64bit), but none of the providers can be installed - ghc-array-0.5.4.0-142.fc40.x86_64 from @System does not belong to a distupgrade repository - problem with installed package ghc-foldable1-classes-compat-0.1-4.fc40.x86_64 Problem 2: package ghc-foldable1-classes-compat-devel-0.1-4.fc40.x86_64 from @System requires ghc-devel(base-4.17.1.0), but none of the providers can be installed - package ghc-foldable1-classes-compat-devel-0.1-4.fc40.x86_64 from @System requires ghc-devel(ghc-prim-0.9.0), but none of the providers can be installed - ghc-base-devel-4.17.1.0-142.fc40.x86_64 from @System does not belong to a distupgrade repository - problem with installed package ghc-foldable1-classes-compat-devel-0.1-4.fc40.x86_64 Problem 3: package dolphin-emu-5.0.21460-3.fc41.x86_64 from fedora requires libfmt.so.10()(64bit), but none of the providers can be installed - problem with installed package dolphin-emu-5.0.20347-9.fc40.x86_64 - fmt-10.2.1-4.fc40.x86_64 from @System does not belong to a distupgrade repository - dolphin-emu-5.0.20347-9.fc40.x86_64 from @System does not belong to a distupgrade repository Problem 4: package python3-fb-re2-1.0.7-18.fc41.x86_64 from fedora requires libre2.so.9()(64bit), but none of the providers can be installed - problem with installed package python3-fb-re2-1.0.7-15.fc40.x86_64 - re2-1:20220601-19.fc40.x86_64 from @System does not belong to a distupgrade repository - python3-fb-re2-1.0.7-15.fc40.x86_64 from @System does not belong to a distupgrade repository
Dridi
On Tue, Sep 03, 2024 at 07:52:47AM +0000, Dridi Boukelmoune wrote:
Error: Problem 1: package ghc-foldable1-classes-compat-0.1-4.fc40.x86_64 from @System requires libHSarray-0.5.4.0-ghc9.4.5.so()(64bit), but none of the providers can be installed
Already resolved, https://bugzilla.redhat.com/show_bug.cgi?id=2315865.
Problem 3: package dolphin-emu-5.0.21460-3.fc41.x86_64 from fedora requires libfmt.so.10()(64bit), but none of the providers can be installed
dolphin-emu-2407-1.fc41 was built and resolved the issue.
Problem 4: package python3-fb-re2-1.0.7-18.fc41.x86_64 from fedora requires libre2.so.9()(64bit), but none of the providers can be installed
- problem with installed package python3-fb-re2-1.0.7-15.fc40.x86_64
- re2-1:20220601-19.fc40.x86_64 from @System does not belong to a
distupgrade repository
- python3-fb-re2-1.0.7-15.fc40.x86_64 from @System does not belong to a
distupgrade repository
Someone else reported a problem with re2, but it seems to have been resolved already.
Zbyszek
On Fri, Oct 4, 2024, at 9:51 AM, Zbigniew Jędrzejewski-Szmek wrote:
Problem 4: package python3-fb-re2-1.0.7-18.fc41.x86_64 from fedora requires libre2.so.9()(64bit), but none of the providers can be installed
- problem with installed package python3-fb-re2-1.0.7-15.fc40.x86_64
- re2-1:20220601-19.fc40.x86_64 from @System does not belong to a
distupgrade repository
- python3-fb-re2-1.0.7-15.fc40.x86_64 from @System does not belong to a
distupgrade repository
Someone else reported a problem with re2, but it seems to have been resolved already.
Zbyszek
The python-fb-re2 package, which was unmaintained upstream, was retired for F41, replaced by the python3-google-re2 subpackage, which is the “official” bindings now built from the re2 package.[1] Both provide mostly-compatible modules for 'import re2', and the new subpackage has Conflicts/Obsoletes for python3-fb-re2, but it doesn’t Provide python3-fb-re2 or python3dist(fb-re2) since they are different PyPI projects. I think this is was all correctly handled, but I’m happy to fix anything I might have missed.
[1] https://src.fedoraproject.org/rpms/re2/c/63114e05d5c71de41dca62d0804b229e259...
Tested on Fedora 40 running Gnome with nvidia hybrid on a zephyrus g14 laptop, no errors to report
On Mon, 2 Sept 2024, 15:51 Miroslav Suchý, msuchy@redhat.com wrote:
Do you want to make Fedora 41 better? Please spend 1 minute of your time and try to run:
dnf --releasever=41 --enablerepo=updates-testing --assumenodistro-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 40. Please check existing reports against fedora-obsolete-packages first:
and also there is already lots of "Fails to install" (F40FailsToInstall) reports: http://bit.ly/3TcO0Ng
One note:
- you may want to run the same command with dnf5 to help test new dnf. Do
not forget to add --best otherwise DNF5 hides all problems.
For convenience here is the relevant part of Fedora Guidelines on renaming and replacing packages:
https://docs.fedoraproject.org/en-US/packaging-guidelines/#renaming-or-repla...
Thank you Miroslav -- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
I tried both dnf & dnf5 on my three Fedora installations, which, for the most part, only have the minimal development tools needed to build and test our software (Cube, OTF2, OPARI2, Score-P, Scalasca). Everything seemed to work fine without any errors. Also tried to update one of the installations and that also went (mostly) smooth. Pipewire crashed after the first reboot but worked fine afterwards.
Best, Jan
On 02.09.24 12:20, Miroslav Suchý wrote:
Do you want to make Fedora 41 better? Please spend 1 minute of your time and try to run:
dnf --releasever=41 --enablerepo=updates-testing --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 40. Please check existing reports against fedora-obsolete-packages first:
and also there is already lots of "Fails to install" (F40FailsToInstall) reports:
One note:
- you may want to run the same command with dnf5 to help test new dnf.
Do not forget to add --best otherwise DNF5 hides all problems.
For convenience here is the relevant part of Fedora Guidelines on renaming and replacing packages:
https://docs.fedoraproject.org/en-US/packaging-guidelines/#renaming-or-repla...
Thank you
Miroslav
One note:
- you may want to run the same command with dnf5 to help test new dnf. Do not forget to add --best otherwise DNF5 hides all problems.
One thing I've noticed with dnf5 is that somethings are missing, I'm not sure if they've been replaced with something else. EG "dnf config-manager --set-enabled updates-testing" doesn't work, is there a FAQ/guide that I've missed for things like that?
Peter
V Tue, Sep 03, 2024 at 02:28:38PM +0100, Peter Robinson napsal(a):
One note:
- you may want to run the same command with dnf5 to help test new dnf. Do not forget to add --best otherwise DNF5 hides all problems.
One thing I've noticed with dnf5 is that somethings are missing, I'm not sure if they've been replaced with something else. EG "dnf config-manager --set-enabled updates-testing" doesn't work, is there a FAQ/guide that I've missed for things like that?
There is doc/changes.rst file https://github.com/rpm-software-management/dnf5/blob/main/doc/changes.rst in the sources. I don't know why it isn't packaged. I opened https://github.com/rpm-software-management/dnf5/issues/1674 request for packaging it.
-- Petr
- you may want to run the same command with dnf5 to help test new dnf. Do not forget to add --best otherwise DNF5 hides all problems.
One thing I've noticed with dnf5 is that somethings are missing, I'm not sure if they've been replaced with something else. EG "dnf config-manager --set-enabled updates-testing" doesn't work, is there a FAQ/guide that I've missed for things like that?
There is doc/changes.rst file https://github.com/rpm-software-management/dnf5/blob/main/doc/changes.rst in the sources. I don't know why it isn't packaged. I opened https://github.com/rpm-software-management/dnf5/issues/1674 request for packaging it.
It seems the main problem is that dnf-plugins-core isn't obsoleted by dnf5-plugins and I think that dnf5-plugins might be useful to have a plugins-core that has key plugins like config-manager and have it enabled by default just like in dnf v4.
Peter
I get the following result on my F40 machine:
``` Error: Problem: package python3-fb-re2-1.0.7-18.fc41.x86_64 from fedora requires libre2.so.9()(64bit), but none of the providers can be installed - problem with installed package python3-fb-re2-1.0.7-15.fc40.x86_64 - re2-1:20220601-19.fc40.x86_64 from @System does not belong to a distupgrade repository - python3-fb-re2-1.0.7-15.fc40.x86_64 from @System does not belong to a distupgrade repository ```
-- Tau~
Dne 02. 09. 24 v 12:20 odp. Miroslav Suchý napsal(a):
Do you want to make Fedora 41 better? Please spend 1 minute of your time and try to run:
dnf --releasever=41 --enablerepo=updates-testing --assumeno distro-sync
I hit
Problem 1: installed package compat-golang-github-shirou-gopsutil-3-devel-3.24.5-1.fc40.noarch requires golang-ipath(github.com/shirou/gopsutil) = 3.24.5-1.fc40, but none of the providers can be installed - golang-github-shirou-gopsutil-devel-3.24.5-1.fc40.noarch does not belong to a distupgrade repository - problem with installed package Problem 2: installed package compat-golang-github-xhit-str2duration-2-devel-2.1.0-5.fc40.noarch requires golang-ipath(github.com/xhit/go-str2duration) = 2.1.0-5.fc40, but none of the providers can be installed - golang-github-xhit-str2duration-devel-2.1.0-5.fc40.noarch does not belong to a distupgrade repository - problem with installed package Problem 3: installed package compat-golang-gotest-3-devel-3.3.0-7.fc40.noarch requires golang-ipath(gotest.tools) = 3.3.0-7.fc40, but none of the providers can be installed - golang-gotest-devel-3.3.0-7.fc40.noarch does not belong to a distupgrade repository - problem with installed package
And I am not able to decipher the golang dependency and what package is in fault.
On 9/5/24 06:57 AM, Miroslav Suchý wrote:
dnf --releasever=41 --enablerepo=updates-testing --assumeno distro-sync
Most of my issues are due to gimp: gutenprint-plugin, gimp-resynthesizer, gimp-lqr-plugin.
Problem #2 relates to kicad-nightly which comes from Copr, so that may not be a fair test.
The list below is generated by dnf. When I tried dnf5 there were no errors reported.
Error: Problem 1: package gutenprint-plugin-5.3.4-16.fc40.x86_64 from @System requires libgimp-2.0.so.0()(64bit), but none of the providers can be installed - package gutenprint-plugin-5.3.4-16.fc40.x86_64 from @System requires libgimpbase-2.0.so.0()(64bit), but none of the providers can be installed - package gutenprint-plugin-5.3.4-16.fc40.x86_64 from @System requires libgimpui-2.0.so.0()(64bit), but none of the providers can be installed - gimp-libs-2:2.10.38-1.fc40.x86_64 from @System does not belong to a distupgrade repository - problem with installed package gutenprint-plugin-5.3.4-16.fc40.x86_64 Problem 2: package kicad-nightly-1:8.99.0-1.20240827gita9e1159.fc40.x86_64 from @System requires libTKMath.so.7()(64bit), but none of the providers can be installed - package kicad-nightly-1:8.99.0-1.20240827gita9e1159.fc40.x86_64 from @System requires libTKernel.so.7()(64bit), but none of the providers can be installed - opencascade-foundation-7.6.3-4.fc39.x86_64 from @System does not belong to a distupgrade repository - problem with installed package kicad-nightly-1:8.99.0-1.20240827gita9e1159.fc40.x86_64 Problem 3: package gimp-resynthesizer-2.0.3-14.20190428gitadfa25a.fc41.x86_64 from fedora requires gimp, but none of the providers can be installed - package gimp-2:2.99.19^20240826git3ded3c47fe-1.fc41.x86_64 from fedora requires gimp-libs(x86-64) = 2:2.99.19^20240826git3ded3c47fe-1.fc41, but none of the providers can be installed - package gimp-2:2.99.19^20240902gitb44687eb2f-1.fc41.x86_64 from updates-testing requires gimp-libs(x86-64) = 2:2.99.19^20240902gitb44687eb2f-1.fc41, but none of the providers can be installed - cannot install both gimp-libs-2:2.99.19^20240826git3ded3c47fe-1.fc41.x86_64 from fedora and gimp-libs-2:2.10.38-1.fc40.x86_64 from @System - cannot install both gimp-libs-2:2.99.19^20240902gitb44687eb2f-1.fc41.x86_64 from updates-testing and gimp-libs-2:2.10.38-1.fc40.x86_64 from @System - package gimp-jxl-plugin-1:0.10.3-3.fc41.x86_64 from fedora requires libgimp-2.0.so.0()(64bit), but none of the providers can be installed - package gimp-jxl-plugin-1:0.10.3-3.fc41.x86_64 from fedora requires libgimpcolor-2.0.so.0()(64bit), but none of the providers can be installed - package gimp-jxl-plugin-1:0.10.3-3.fc41.x86_64 from fedora requires libgimpui-2.0.so.0()(64bit), but none of the providers can be installed - package gimp-jxl-plugin-1:0.10.3-3.fc41.x86_64 from fedora requires libgimpwidgets-2.0.so.0()(64bit), but none of the providers can be installed - problem with installed package gimp-resynthesizer-2.0.3-13.20190428gitadfa25a.fc40.x86_64 - problem with installed package gimp-jxl-plugin-1:0.8.3-1.fc40.x86_64 - gimp-resynthesizer-2.0.3-13.20190428gitadfa25a.fc40.x86_64 from @System does not belong to a distupgrade repository - gimp-jxl-plugin-1:0.8.3-1.fc40.x86_64 from @System does not belong to a distupgrade repository - gimp-2:2.10.38-1.fc40.x86_64 from @System does not belong to a distupgrade repository Problem 4: package gimp-lqr-plugin-0.7.2-26.fc41.x86_64 from fedora requires gimp(x86-64) >= 2.4, but none of the providers can be installed - package gimp-2:2.99.19^20240826git3ded3c47fe-1.fc41.x86_64 from fedora requires gimp-libs(x86-64) = 2:2.99.19^20240826git3ded3c47fe-1.fc41, but none of the providers can be installed - package gimp-2:2.99.19^20240902gitb44687eb2f-1.fc41.x86_64 from updates-testing requires gimp-libs(x86-64) = 2:2.99.19^20240902gitb44687eb2f-1.fc41, but none of the providers can be installed - cannot install both gimp-libs-2:2.99.19^20240826git3ded3c47fe-1.fc41.x86_64 from fedora and gimp-libs-2:2.10.38-1.fc40.x86_64 from @System - cannot install both gimp-libs-2:2.99.19^20240902gitb44687eb2f-1.fc41.x86_64 from updates-testing and gimp-libs-2:2.10.38-1.fc40.x86_64 from @System - package gimp-lqr-plugin-0.7.2-26.fc41.x86_64 from fedora requires libgimp-2.0.so.0()(64bit), but none of the providers can be installed - package gimp-lqr-plugin-0.7.2-26.fc41.x86_64 from fedora requires libgimpbase-2.0.so.0()(64bit), but none of the providers can be installed - package gimp-lqr-plugin-0.7.2-26.fc41.x86_64 from fedora requires libgimpcolor-2.0.so.0()(64bit), but none of the providers can be installed - package gimp-lqr-plugin-0.7.2-26.fc41.x86_64 from fedora requires libgimpui-2.0.so.0()(64bit), but none of the providers can be installed - package gimp-lqr-plugin-0.7.2-26.fc41.x86_64 from fedora requires libgimpwidgets-2.0.so.0()(64bit), but none of the providers can be installed - package gimp-2:2.10.38-1.fc40.x86_64 from @System requires libjxl.so.0.8()(64bit), but none of the providers can be installed - package gimp-2:2.10.38-1.fc40.x86_64 from @System requires libjxl.so.0.8(JXL_0)(64bit), but none of the providers can be installed - package gimp-2:2.10.38-1.fc40.x86_64 from @System requires libjxl_threads.so.0.8()(64bit), but none of the providers can be installed - package gimp-2:2.10.38-1.fc40.x86_64 from @System requires libjxl_threads.so.0.8(JXL_0)(64bit), but none of the providers can be installed - problem with installed package gimp-lqr-plugin-0.7.2-25.fc40.x86_64 - libjxl-1:0.8.3-1.fc40.x86_64 from @System does not belong to a distupgrade repository - gimp-lqr-plugin-0.7.2-25.fc40.x86_64 from @System does not belong to a distupgrade repository
On Mon, Sep 2, 2024 at 5:21 AM Miroslav Suchý msuchy@redhat.com wrote:
Do you want to make Fedora 41 better? Please spend 1 minute of your time and try to run:
dnf --releasever=41 --enablerepo=updates-testing --assumenodistro-sync
Here's my results, seems to be some issues with InsightToolkit, gussing a FTBFS issue since it's tagged f39 and we've had a rebuild since then:
Error: Problem 1: package alizams-1.9.10-2.fc41.x86_64 from fedora requires libITKCommon-4.13.so.1()(64bit), but none of the providers can be installed - package alizams-1.9.10-2.fc41.x86_64 from fedora requires libITKStatistics-4.13.so.1()(64bit), but none of the providers can be installed - package alizams-1.9.10-2.fc41.x86_64 from fedora requires libITKTransform-4.13.so.1()(64bit), but none of the providers can be installed - package InsightToolkit-4.13.3-15.fc39.x86_64 from @System requires libtiff.so.5()(64bit), but none of the providers can be installed - package InsightToolkit-4.13.3-15.fc39.x86_64 from @System requires libtiff.so.5(LIBTIFF_4.0)(64bit), but none of the providers can be installed - package InsightToolkit-4.13.3-15.fc39.x86_64 from fedora requires libtiff.so.5()(64bit), but none of the providers can be installed - package InsightToolkit-4.13.3-15.fc39.x86_64 from fedora requires libtiff.so.5(LIBTIFF_4.0)(64bit), but none of the providers can be installed - problem with installed package alizams-1.9.9-2.fc40.x86_64 - libtiff-4.6.0-2.fc40.x86_64 from @System does not belong to a distupgrade repository - alizams-1.9.9-2.fc40.x86_64 from @System does not belong to a distupgrade repository Problem 2: problem with installed package InsightToolkit-4.13.3-15.fc39.x86_64 - package InsightToolkit-4.13.3-15.fc39.x86_64 from @System requires libtiff.so.5()(64bit), but none of the providers can be installed - package InsightToolkit-4.13.3-15.fc39.x86_64 from @System requires libtiff.so.5(LIBTIFF_4.0)(64bit), but none of the providers can be installed - package InsightToolkit-4.13.3-15.fc39.x86_64 from fedora requires libtiff.so.5()(64bit), but none of the providers can be installed - package InsightToolkit-4.13.3-15.fc39.x86_64 from fedora requires libtiff.so.5(LIBTIFF_4.0)(64bit), but none of the providers can be installed - cannot install both libtiff-4.6.0-6.fc41.x86_64 from fedora and libtiff-4.6.0-2.fc40.x86_64 from @System - package libtiff-devel-4.6.0-6.fc41.x86_64 from fedora requires libtiff(x86-64) = 4.6.0-6.fc41, but none of the providers can be installed - problem with installed package libtiff-devel-4.6.0-2.fc40.x86_64 - libtiff-devel-4.6.0-2.fc40.x86_64 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)
Thanks, Richard
On 05/09/2024 16.24, Richard Shaw wrote:
On Mon, Sep 2, 2024 at 5:21 AM Miroslav Suchý msuchy@redhat.com wrote:
Do you want to make Fedora 41 better? Please spend 1 minute of your time and try to run:
dnf --releasever=41 --enablerepo=updates-testing --assumenodistro-sync
It looks good. I assume the rpm-fusion issue without `--allowerasing` is to be expected at this time.
`dnf --releasever=41 --enablerepo=updates-testing --assumeno distro-sync` ``` Last metadata expiration check: 0:00:43 ago on Thu 05 Sep 2024 04:59:55 PM CEST. Error: Problem 1: package mesa-va-drivers-freeworld-24.1.7-1.fc40.x86_64 from @System requires mesa-filesystem(x86-64) = 24.1.7, but none of the providers can be installed - mesa-filesystem-24.1.7-1.fc40.x86_64 from @System does not belong to a distupgrade repository - problem with installed package mesa-va-drivers-freeworld-24.1.7-1.fc40.x86_64 Problem 2: problem with installed package mesa-dri-drivers-24.1.7-1.fc40.x86_64 - package mesa-dri-drivers-24.2.0-2.fc41.x86_64 from fedora requires mesa-filesystem(x86-64) = 24.2.0-2.fc41, but none of the providers can be installed - package mesa-dri-drivers-24.2.1-5.fc41.x86_64 from updates-testing requires mesa-filesystem(x86-64) = 24.2.1-5.fc41, but none of the providers can be installed - cannot install both mesa-filesystem-24.2.0-2.fc41.x86_64 from fedora and mesa-filesystem-24.1.7-1.fc40.x86_64 from @System - cannot install both mesa-filesystem-24.2.1-5.fc41.x86_64 from updates-testing and mesa-filesystem-24.1.7-1.fc40.x86_64 from @System - package mesa-vdpau-drivers-freeworld-24.1.7-1.fc40.x86_64 from @System requires mesa-filesystem(x86-64) = 24.1.7, but none of the providers can be installed - mesa-dri-drivers-24.1.7-1.fc40.x86_64 from @System does not belong to a distupgrade repository - problem with installed package mesa-vdpau-drivers-freeworld-24.1.7-1.fc40.x86_64 (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages) ```
`dnf --releasever=41 --enablerepo=updates-testing --assumeno distro-sync --allowerasing` ``` Last metadata expiration check: 0:03:38 ago on Thu 05 Sep 2024 04:59:55 PM CEST. Dependencies resolved. ============================================================================================================================= Package Arch Version Repository Size ============================================================================================================================= Installing: ... ... <packages> ... ... Installing group/module packages: ... ... <packages> ... ... Installing weak dependencies: calligra-okular-odpgenerator x86_64 4.0.1-2.fc41 updates-testing 41 k calligra-okular-odtgenerator x86_64 4.0.1-2.fc41 updates-testing 59 k Removing: kernel x86_64 6.10.3-200.fc40 @updates 0 kernel-core x86_64 6.10.3-200.fc40 @updates 69 M kernel-modules x86_64 6.10.3-200.fc40 @updates 62 M kernel-modules-core x86_64 6.10.3-200.fc40 @updates 36 M kernel-modules-extra x86_64 6.10.3-200.fc40 @updates 2.7 M Removing dependent packages: mesa-va-drivers-freeworld x86_64 24.1.7-1.fc40 @rpmfusion-free-updates 15 M mesa-vdpau-drivers-freeworld x86_64 24.1.7-1.fc40 @rpmfusion-free-updates 15 M Downgrading: python3-sentry-sdk noarch 2.13.0-1.fc41 fedora 644 k wpa_supplicant x86_64 1:2.11-2.fc41 fedora 1.7 M
Transaction Summary ============================================================================================================================= Install 37 Packages Upgrade 2613 Packages Remove 7 Packages Downgrade 2 Packages
Total download size: 4.3 G ```
Best, Chris
-
Alec Leamas -
Artur Frenszek-Iwicki -
Ben Beasley -
Christopher Klooz -
Cristian Le -
Dridi Boukelmoune -
Fabio Valentini -
Gary Buhrmaster -
Globe Trotter -
H H L P -
Ian Laurie -
Jan André Reuter -
Kanitha Chim -
Leigh Scott -
Leslie Satenstein -
Luna Jernberg -
Marcin Juszkiewicz -
Michael Schwendt -
Miroslav Suchý -
Olav Vitters -
Pablo Sebastián Greco -
Peter Robinson -
Petr Pisar -
Rajeesh K V -
Richard Shaw -
Steven A. Falco -
Tau Gärtli -
Vít Ondruch -
Zbigniew Jędrzejewski-Szmek -
Zerotwo02