Mate-desktop-configs, rubygem-thin-1.8.0-1.fc34.x86_64 not allowing upgrade from 35 to 37

I am trying to upgrade my fedora35 box to 37, I am following instructions by using
dnf system-upgrade download --releasever=37

I get blocked with 3 errors as follows:

Error:
Problem 1: package rubygem-thin-1.8.0-1.fc34.x86_64 requires libruby.so.3.0()(64bit), but none of the providers can be installed

  • ruby-libs-3.0.5-155.fc35.x86_64 does not belong to a distupgrade repository
  • problem with installed package rubygem-thin-1.8.0-1.fc34.x86_64
    Problem 2: conflicting requests
  • package mate-desktop-configs-1.26.0-6.fc37.noarch conflicts with systemd-oomd-defaults provided by systemd-oomd-defaults-251.7-611.fc37.noarch
  • package mate-desktop-configs-1.26.0-6.fc37.noarch conflicts with systemd-oomd-defaults provided by systemd-oomd-defaults-251.13-6.fc37.noarch
  • package mate-desktop-1.26.0-6.fc37.x86_64 requires mate-desktop-configs = 1.26.0-6.fc37, but none of the providers can be installed
  • problem with installed package mate-desktop-1.26.0-1.fc35.x86_64
  • systemd-oomd-defaults-249.13-6.fc35.noarch does not belong to a distupgrade repository
  • mate-desktop-1.26.0-1.fc35.x86_64 does not belong to a distupgrade repository
    Problem 3: problem with installed package systemd-oomd-defaults-249.13-6.fc35.noarch
  • package mate-desktop-configs-1.26.0-6.fc37.noarch conflicts with systemd-oomd-defaults provided by systemd-oomd-defaults-251.7-611.fc37.noarch
  • package mate-desktop-configs-1.26.0-6.fc37.noarch conflicts with systemd-oomd-defaults provided by systemd-oomd-defaults-251.13-6.fc37.noarch
  • package mate-desktop-1.26.0-6.fc37.x86_64 requires mate-desktop-configs = 1.26.0-6.fc37, but none of the providers can be installed
  • package mate-system-monitor-1.26.0-3.fc37.x86_64 requires mate-desktop, but none of the providers can be installed
  • package systemd-oomd-defaults-249.13-6.fc35.noarch requires systemd = 249.13-6.fc35, but none of the providers can be installed
  • problem with installed package mate-system-monitor-1.26.0-1.fc35.x86_64
  • package mate-desktop-1.26.0-1.fc35.x86_64 requires mate-desktop-libs(x86-64) = 1.26.0-1.fc35, but none of the providers can be installed
  • systemd-249.13-6.fc35.x86_64 does not belong to a distupgrade repository
  • mate-system-monitor-1.26.0-1.fc35.x86_64 does not belong to a distupgrade repository
  • mate-desktop-libs-1.26.0-1.fc35.x86_64 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)

I tried ‘–allowerasing’ and ‘–skip-broken’, command runs but after a while the terminal just shut down. Can you please tell me what I should do in order to make the upgrade goes through? Than ks in advance

I’m sure you have but have you made sure that your system is fully up to date.Since F35 is not supported any more I don’t know if it will update.Also you might try and remove rubygem as you can always reinstall it again later.I haven’t used Mate in many years but you might try and upgrade to F36 then upgrade to F37.

Tim I tried to upgrade to 36, getting the exact same errors

Other than trying to remove ruby and trying again I’m sorry I don’t know what else to suggest.I hope someone who knows more about upgrading Mate can read this post and try and help you.

Try the following
dnf upgrade --refresh
dnf distro-sync --refresh

Fix any errors reported in either of those 2 processes before attempting to do an upgrade to a newer version. As noted, it may be necessary to uninstall conflicting packages to proceed.
It also may be necessary to uninstall packages from 3rd party repos and possibly even disable those repos before proceding.

Essentially the issue is that if you have something that is not directly upgraded with the new version you may need to remove it before upgrading.

I note that some of the complaints are about fc34 packages so that would be what I looked at first. Are they needed or can they be removed? Anything that can be removed can usually be reinstalled after the upgrades are completed.

1 Like

So many thanks JeffV, I did remove the ruby and upgrade went through and I was able to log to the fedora 37. However, I will try to benefit from this thread to ask for another similar issue for a 2nd fedora 35. When I run the

dnf upgrade --refresh

I get the following

Error: Transaction test error:
file /usr/share/doc/expat/Changes from install of expat-2.5.0-1.fc35.i686 conflicts with file from package expat-2.4.9-1.fc35.x86_64
file /usr/share/man/man1/xmlwf.1.gz from install of expat-2.5.0-1.fc35.i686 conflicts with file from package expat-2.4.9-1.fc35.x86_64
file /usr/share/doc/libxcrypt/NEWS from install of libxcrypt-4.4.33-3.fc35.i686 conflicts with file from package libxcrypt-4.4.28-1.fc35.x86_64

When I try to remove expat
sudo dnf remove expat --skip-broken
or
sudo dnf remove expat expat-2.4.9-1.fc35.x86_64 --skip-broken
I get an alert

Error:
Problem: The operation would result in removing the following protected packages: systemd

Soreally stuck and refresh never goes through even when I use --skip-broken or --exclude=expat-2.4.9-1.fc35.x86_64

sudo dnf remove expat.i686 libxcrypt.i686

So many thanks Vladislav, the 1st statement did the job and
sudo dnf upgrade --refresh
goes well and rebooted after it was successful. However, when I run

sudo dnf system-upgrade download --releasever=37

It downloads files then it starts transaction check and all of a suydden terminal shuts down by itself, this happened 3 times

Are you running out of memory?

If you are running out of memory — and the out-of-memory killer stopping the process in an attempt to keep this from making the system responsive would explain what you’re seeing — see this:

1 Like

A post was split to a new topic: What is the best to clean/remove unused packages/files/logs?

Thanks Matthew, the VM has 6gig of RAM, in fact, I rebooted then reissued the command for theth time and update went through.