[SOLVED] Fedora Upgrade 35 to 36 error: passenger needs libruby, but can't be installed from any providers...passenger-6.0.4-5.fc34 is giving trouble

About a year ago, I upgraded my Fedora server to version 35.
Within a year, it seems there have been 2 upgrades, the current version is 37.

This time, I first tried to upgrade to ver. 36.

But I got the above error, and cannot upgrade the server to ver. 36.
(Error message was, "system not ready for upgrade" or something like that.)

What did I do?
1. dnf upgrade --refresh
2. dnf distro-sync --refresh
3. dnf system-upgrade download --releasever=36

After 10-15 minutes of downloading various packages, I got the above error.

The error messages also mentioned that I can use "--skip-broken" to skip the uninstallable package.

Q1. Where do I use the --skip-broken command? With #3 above?

But I am worried that I might break something.

This Fedora server has DNS server in it, and I do not want to break, because I don't know how to fix it if it does not work. (I did not install/manage the DNS server, the person who installed/managed has left, without any documentation.)

The Passenger package seems to be some kind of web server/application server.
My sever has Apache server, and I am happy with Apache. I don't use (or remember installing) this Passenger package.

Q2. Would it be safe to use "--skip-broken" and see if I can get through to ver. 36?

Or any other ways I might try to get it done? (35 to 36).

After I upgrade to ver. 36, I will try to upgrade to ver. 37.

I would appreciate any hint.
Thanks.

# inxi -S
System:
  Host: p5bse Kernel: 6.0.12-100.fc35.x86_64 arch: x86_64 bits: 64
    Console: pty pts/0 Distro: Fedora release 35 (Thirty Five)
# dnf search assenger
Last metadata expiration check: 0:01:35 ago on Sun 02 Apr 2023 01:32:35 AM EDT.
===== Name & Summary Matched: assenger =====
mod_passenger.x86_64 : Apache Module for Phusion Passenger
passenger.i686 : Phusion Passenger application server
passenger.x86_64 : Phusion Passenger application server
passenger-devel.i686 : Phusion Passenger development files
passenger-devel.x86_64 : Phusion Passenger development files

# inxi -S
System:
  Host: gb970 Kernel: 6.2.7-100.fc36.x86_64 arch: x86_64 bits: 64
    Console: pty pts/0 Distro: Fedora release 36 (Thirty Six)
# dnf search assenger
Last metadata expiration check: 0:00:41 ago on Sun 02 Apr 2023 01:10:38 AM EDT.
No matches found.
#

I suggest to try instead of --skip-broken with dnf system-upgrade download --releasever=36 to use --allowerasing and/or --best. I think I'd try --best alone first, and if no good, --allowerasing alone next, and if still no good, both. I used to use Apache, and never heard of Passenger. If you actually need it you can probably add it back from some non-default source after the upgrade removes it. Removal normally removes the application, but leaves behind any customized configurations you might have applied.

@mrmazda, Thank you for comments.

I also had not heard about this Passenger package, and I did not insall it.
By the way, I got similar output when I executed "dnf search Passenger"

mod_passenger.x86_64 : Apache Module for Phusion Passenger
passenger.x86_64 : Phusion Passenger application server
passenger.i686 : Phusion Passenger application server
passenger-devel.i686 : Phusion Passenger development files
passenger-devel.x86_64 : Phusion Passenger development files

and, inxi -S gives:

System:
  Host: xxx Kernel: 6.0.12-100.fc35.x86_64 arch: x86_64 bits: 64
    Console: pty pts/0 Distro: Fedora release 35 (Thirty Five)

I will try your suggestions later.

I will wait for a few days if there are other ideas from other readers...

@mrmazda, "--allowerasing" did the trick! ("--best" didn't work)
I now have ver. 36 (from ver. 35), will upgrade to ver. 37 later.

Thank you very much.