2025-01-14T23:00:00Z
ROME users attention please:
Process finished.
It should be safe to distro-sync ROME system again.
It’s expected another ROME upgrade soon, mostly to fix the remaining issues or fine-tuning so please watch this topic.
2025-01-14T23:00:00Z
ROME users attention please:
Process finished.
It should be safe to distro-sync ROME system again.
It’s expected another ROME upgrade soon, mostly to fix the remaining issues or fine-tuning so please watch this topic.
2025-02-18T23:00:00Z
ROME users attention please:
The process to copy cooker repositories to rolling (ROME) started.
We suggest to not update the system or install software until it’s finished.
We’ll keep you informed when it will be the time to perform distro-sync again.
Stay tuned.
Internal testing is going on.
Please do:
sudo dnf remove hfsutils
first of all before to start distro-sync at due time.
Dependencies resolved.
=========================================
Package Architecture Version Repository Size
=========================================
Removing:
hfsutils x86_64 3.2.6-41 @rolling-x86_64 271 k
Transaction Summary
=========================================
Remove 1 Package
Freed space: 271 k
Is this ok [y/N]: Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing : 1/1
Erasing : hfsutils-3.2.6-41.x86_64 1/1
Removed:
hfsutils-3.2.6-41.x86_64
Complete!
2025-02-20T23:00:00Z
ROME users attention please:
Process finished.
Repository and metadata are all fine.
It should be safe to distro-sync your ROME system again.
Disable any third party repository,
do:
sudo dnf clean all ; dnf clean all ; dnf repolist
sudo dnf distro-sync --refresh --allowerasing 2>&1| tee dsync-log.txt
enable additional repos and do:
sudo dnf distro-sync --refresh --allowerasing 2>&1| tee dsync2-log.txt
Should you encounter any problem, abort the transaction, open a new topic with a descriptive title in Support category and attach the full dsync-log.txt file.
2025-03-24T23:00:00Z
ROME users attention please:
The process to copy cooker repositories to rolling (ROME) is starting.
We suggest to not update the system or install software until it’s finished.
We’ll keep you informed when it will be the time to safely perform distro-sync again.
Stay tuned.
Situation update:
For your information, GO/all-clear delayed because of still fixing some issues discovered after repositories sync by internal testing.
That’s not a bug that’s a feature ![]()
We want to make the users to perform a safe distro-sync, not rushing just for the sake of do it.
2025-04-13T22:00:00Z
It looks like the last showstopper has been addressed.
The kernel 6.14.2-2 is on the way to ROME repos as well and barring unexpected events will be available in a few hours or so.
ROME users don’t worry if you have not received significant updates since some time.
A lot of changes are going on in cooker like the KDE packages renaming as part of getting rid of Plasma5, or the switch from xorg to xlibre which looks like one of the most wanted feature our users are eager to get as soon as possible (nonetheless it implying a lot of work and testing), just to mention a couple of them.
In the mean time we have fixed most of the issues reported to the Issue Tracker as well as fullfilled almost all the new package requests and added a huge number of new software to the repositories thanks to new contributors.
Of course we also regularly push updates to the already existing software.
Everything will be available with the next copy of cooker repos to rolling, to make you happy.
But we are almost there. We’ll come back to you soon, you can be sure.
Stay tuned and enjoy your ROME [safe rolling] system ![]()
The big sync is now running again, it should take another hour or two to finish (and then a few more hours for mirrors to catch up).
It’s finished now, as a last step an updated distro-release is building.
ROME major upgrade november 2025
Some minor things with ROME upgrade (09-11-2025)
Aggiornamenti di novembre 2025 (IT)
Should you encounter any problem, abort the transaction, open a new topic with a descriptive title in Support category and attach the full dsync-log.txt file.
2025-12-05T00:00:00Z Major ROME upgrade is in progress.
dsync or distro-sync your ROME(rolling) system until we have had time to test this.We can not know if special instructions are needed for one of these upgrades until we test.
If you were going to use upgrade or up don’t. You need to read the Big Fat Warning blue banner at the top of this page.
2026-02-13T00:00:00Z Major ROME upgrade is in progress.
dsync or distro-sync your ROME(rolling) system until we have had time to test this.We can not know if special instructions are needed for one of these upgrades until we test.
If you were going to use upgrade or up don’t. You need to read the Big Fat Warning blue banner at the top of this page.
As of testing 6 days ago this upgrade would work fine with this command:
sudo dnf clean all ; sudo dnf dsync --allowerasing
But it would be wise to let us test this before proceeding.
We will inform users here when it is safe proceed and will include any special instructions if they are necessary.
2026-09-08T22:00:00Z
ROME users attention please:
The process to copy cooker repositories to rolling (ROME) is going to start soon.
We suggest to not update the system or install software until it’s finished.
We’ll keep you informed when it will be the time to safely perform distro-sync again.
Stay tuned.
2026-09-09T22:00:00Z
Please ignore the latest announcement. The process has been delayed.
For more details feel free to ask @bero who is the only person who decided, against all QA group and contributors’ opinion.
If anyone is running Cooker and would like to change back to ROME, now would be the time to switch your repositories to ROLLING in the repository selector in the OM-Welcome app. Don’t do a dsync until we have tested everything.
2026-09-13T00:00:00Z Major ROME upgrade is in progress.
disto-sync) your ROME system.Our recent testing does not show any need for special instructions beyond the following:
If you were going to use dnf upgrade or dnf up don’t. You need to read the Big Fat Warning blue banner at the top of this page.
As of recent testing this upgrade would work fine with this command:
sudo dnf clean all ; sudo dnf dsync --allowerasing
NOTE: This is a major upgrade, there will be over 1500 downloads. To create a log file while doing this transaction is a very good idea just in case there is a problem. To do that use this command:
sudo dnf clean all ; sudo dnf dsync --allowerasing 2>&1| tee dsync-log.txt
OR we have tested doing this using the System Upgrade utility and that seems to work well.
NOTE: When using the --allowerasing it is wise to check what, if anything, might get removed.
If you have any problems or questions please ask in the English Support forum with a descriptive title and include your dsync-log.txt file.