$ 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: https://red.ht/2kuBDPu 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-replacing-existing-packages Thank you Miroslav -- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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 -- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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
