Update fedora from 29 to 31,but getting 29 conflicting requests

,

I want to upgrade fedora 29 to 31,but there are 29 confilcting requests alaways,but when i type neofetch but i can see Fedora release 31 (Thirty One) x86_64,and my kernel is 5.3.11-100.fc29。how could i slove these conflicting request.:confused:

Last metadata expiration check: 0:02:01 ago on Wed 22 Jan 2020 09:48:00 AM CST.
Modular dependency problems:

 Problem 1: conflicting requests
  - nothing provides module(platform:f29) needed by module afterburn:rolling:2920191015163839:c5ebb199-0.x86_64
 Problem 2: conflicting requests
  - nothing provides module(platform:f29) needed by module askalono-cli:rolling:2920190721090701:c5ebb199-0.x86_64
 Problem 3: conflicting requests
  - nothing provides module(platform:f29) needed by module avocado:69lts:2920191004211344:6c81f848-0.x86_64
 Problem 4: conflicting requests
  - nothing provides module(platform:f29) needed by module bat:latest:2920190714171319:c5ebb199-0.x86_64
 Problem 5: conflicting requests
  - nothing provides module(platform:f29) needed by module cbindgen:rolling:2920190515070043:b8a06959-0.x86_64
 Problem 6: conflicting requests
  - nothing provides module(platform:f29) needed by module dutree:rolling:2920190926112243:c5ebb199-0.x86_64
 Problem 7: conflicting requests
  - nothing provides module(platform:f29) needed by module dwm:6.2:2920190206214000:6c81f848-0.x86_64
 Problem 8: conflicting requests
  - nothing provides module(platform:f29) needed by module exa:latest:2920190721165838:c5ebb199-0.x86_64
 Problem 9: conflicting requests
  - nothing provides module(platform:f29) needed by module fd-find:rolling:2920190722174030:c5ebb199-0.x86_64
 Problem 10: conflicting requests
  - nothing provides module(platform:f29) needed by module ffsend:latest:2920190630105436:c5ebb199-0.x86_64
 Problem 11: conflicting requests
  - nothing provides module(platform:f29) needed by module fish:3:2920190219150858:139e1eeb-0.x86_64
 Problem 12: conflicting requests
  - nothing provides module(platform:f29) needed by module gimp:2.10:2920191106095052:6c81f848-0.x86_64
 Problem 13: conflicting requests
  - nothing provides module(platform:f29) needed by module heatseeker:latest:2920190921124230:c5ebb199-0.x86_64
 Problem 14: conflicting requests
  - nothing provides module(platform:f29) needed by module hyperfine:latest:2920190721071357:c5ebb199-0.x86_64
 Problem 15: conflicting requests
  - nothing provides module(platform:f29) needed by module lsd:rolling:2920190803124134:c5ebb199-0.x86_64
 Problem 16: conflicting requests
  - nothing provides module(platform:f29) needed by module meson:latest:2920191009081836:06d0a27d-0.x86_64
 Problem 17: conflicting requests
  - nothing provides module(platform:f29) needed by module minetest:5:2920190308194723:6c81f848-0.x86_64
 Problem 18: conflicting requests
  - nothing provides module(platform:f29) needed by module newsboat:latest:2920190722112326:c5ebb199-0.x86_64
 Problem 19: conflicting requests
  - nothing provides module(platform:f29) needed by module ninja:latest:2920190131012415:6c81f848-0.x86_64
 Problem 20: conflicting requests
  - nothing provides module(platform:f29) needed by module pretty-git-prompt:rolling:2920190714104357:c5ebb199-0.x86_64
 Problem 21: conflicting requests
  - nothing provides module(platform:f29) needed by module ripgrep:latest:2920190803131619:c5ebb199-0.x86_64
 Problem 22: conflicting requests
  - nothing provides module(platform:f29) needed by module rpick:latest:2920190515141045:b8a06959-0.x86_64
 Problem 23: conflicting requests
  - nothing provides module(platform:f29) needed by module sd:rolling:2920190921120742:c5ebb199-0.x86_64
 Problem 24: conflicting requests
  - nothing provides module(platform:f29) needed by module silver:rolling:2920190912064049:c5ebb199-0.x86_64
 Problem 25: conflicting requests
  - nothing provides module(platform:f29) needed by module skim:rolling:2920190921123929:c5ebb199-0.x86_64
 Problem 26: conflicting requests
  - nothing provides module(platform:f29) needed by module stratis:1:2920190907214611:c5ebb199-0.x86_64
 Problem 27: conflicting requests
  - nothing provides module(platform:f29) needed by module tokei:rolling:2920190921122652:c5ebb199-0.x86_64
 Problem 28: conflicting requests
  - nothing provides module(platform:f29) needed by module zola:rolling:2920190922161148:c5ebb199-0.x86_64
No match for argument: 2
Error: No packages marked for upgrade.

I want to upgrade fedora 29 to 31,but there are 29 confilcting requests alaways,but when i type neofetch but i can see Fedora release 31 (Thirty One) x86_64Fedora release 31 (Thirty One) 6_64

I hope there are no other repositories involved. Otherwise, try the following:

sudo dnf update --best --allowerasing

Recommended method is DNF: System upgrade plugin.


What @twohot says isn’t supported:
Can I upgrade between Fedora releases using only DNF?

1 Like

We learn everyday. I will try this upgrade plugin soon – just seeing it for the first time.

If neofetch says that you are on Fedora 31, then you managed to perform the upgrade. :thinking:
What you posted is the output of which command?

I post the conflicting requests by command sudo dnf update.
I upgrade the os from feodra 29 to fedora 31 success,but I always get these conflicting requests print when i try to update my system.I feel it’s :disappointed:.I want to find a solution to eliminate these tips.

@twohot when i type command

$ sudo dnf update --best --allowerasing

I get these tips

Error:
 Problem: The operation would result in removing the following protected packages: dnf
(try to add '--skip-broken' to skip uninstallable packages)

is there something wrong?

Don’t do that! :sweat_smile:

Could you post the content of these files?
/etc/redhat-release
/etc/os-release

1 Like

+1 (supporting @alciregi here)
You need dnf – do NOT remove it

@alciregi sure

Fedora release 31 (Thirty One)

$ cat /etc/os-release
NAME=Fedora
VERSION="31 (Server Edition)"
ID=fedora
VERSION_ID=31
VERSION_CODENAME=""
PLATFORM_ID="platform:f31"
PRETTY_NAME="Fedora 31 (Server Edition)"
ANSI_COLOR="0;34"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:31"
HOME_URL="https://fedoraproject.org/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f31/system-administrators-guide/"
SUPPORT_URL="https://fedoraproject.org/wiki/Communicating_and_getting_help"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=31
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=31
PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy"
VARIANT="Server Edition"
VARIANT_ID=server
bash

Can TS now use a “system upgrade plugin” to “upgrade” form 31 to 31. Something like “distro-sync”?

I think that the problem is caused by some erroneous behavior in Fedora modularity. Modularity in F29 was switched on by default and if you are consuming some modular content, you can arrive into troubles, because that modular content might stop exist in F30 or F31, so there is no way to upgrade, because the target is simply missing.

You should try the following:

  • Run dnf module list --enabled to see if you have some modular streams enabled.
  • Run dnf module list --installed if you have some modules installed.
  • If so, you might want to remove them with dnf module remove <module>.
  • Even more importantly, you need to reset the state of the modules using dnf module reset <module> to drop the modular information.
  • Then you can try upgrading the system.
  • If you want to be on the safe side, disabling modular repos, after you have uninstalled and reset everything might help, too.

If you need an application that is only provided by a module, which in F31 should not generally be the case, you will reinstall it, when you have upgraded.

3 Likes

In the worst case your can firstly backup everything of value, then reinstall Fedora (preferably not touching /home), then dnf upgrade.

Finally-also: Your can make a list of all installed packages with something like:

# dnf creates list
# awk takes only package names
# tail skips first line with word "Installed"
# sed removes .x86_64 .noarch et all.
# final output stored in my_treasures.txt
dnf list --installed |\
    awk '{print $1}' |\
    tail -n+2        |\
    sed 's@\(.\+\)\(\..\+\)@\1@' >\
    my_treasures.txt
# install it all with
dnf install `cat my_treasures.txt`

:sob: maybe this is my only way now.

Do you have third party repos enabled when doing the upgrade? When I have issues updating packages, or anytime I’m gonna upgrade my system, I’ll clean my cache and run the dnf transaction with just the official repos:

dnf clean all
dnf upgrade -y --disablerepo=* --enablerepo=fedora,updates

  Why it’s not a --enablerepo=*fedora* ?  (Is fedora and updates are aliases for all that fedora-modular and fedora-updates-modular things too?)

Because if you do a “dnf repolist” you’ll see those are the names of the repos. Those are the two main repos needed for a full system upgrade. Anything else is just going to complicate it.

1 Like

I have reinstalled Fedora 31 and upgrade from Fedora 31 to Fedora 32, this time it went smoothly.thanks for both you replys. :smile: