Upgrading/distro-sync ROME (2024-04-20)

Support
, , , ,
7

2024-04-19T22:00:00Z

Latest ROME/rolling package upgrade is complete. It is now safe for user to dsync or disto-sync their ROME/rolling system.This one is more straight forward than the last one. Instructions:

  1. If user has not already done this then run:

sudo dnf rm falkon-kde

  1. Then in order to not erase already downloaded packages this command sequence:

sudo dnf --refresh dsync 2>&1| tee dsync-log.txt
sudo dnf autoremove 2>&1| tee autoremove-log.txt
sudo dnf clean all

Explanation: From dnf --help:
--refresh >>> set metadata as expired before running the command
This forces dnf dsync to use latest metadata ensuring that absolute most recent packages are installed.

autoremove >>> remove all unneeded packages that were originally installed as dependencies

Explanation from dnf command reference

: Clean Command

Command: clean

Performs cleanup of temporary files kept for repositories. This includes any such data left behind from disabled or removed repositories as well as for different distribution release versions.

dnf clean dbcache

Removes cache files generated from the repository metadata. This forces DNF to regenerate the cache files the next time it is run.

dnf clean expire-cache

Marks the repository metadata expired. DNF will re-validate the cache for each repository the next time it is used.

dnf clean metadata

Removes repository metadata. Those are the files which DNF uses to determine the remote availability of packages. Using this option will make DNF download all the metadata the next time it is run.

dnf clean packages

Removes any cached packages from the system.

dnf clean all

Does all of the above.

Edit: Should happy user encounter any problems you may post questions here. If you issue arises from the sudo dnf --refresh dsync 2>&1| tee dsync-log.txt then please post the dsync-log.txt. If your issue arises from the sudo dnf autoremove 2>&1| tee autoremove-log.txt please post the autoremove-log.txt .

1 Like