Hello
I’m a new user on ROME (moving away from fedora, awesome experience so far), naturally after installation I used dnf update like I assumed it works with rpm distros, but later found out that dnf dsync is the proper command. While I’m not seeing any serious breakage, it seems like I haven’t been getting updates for days. Assuming that’s not normal of course
Is it better to reinstall? Have set everything up already but I’m probably better off with a properly updated installation. That said the thing with distro-sync should definitely be made more obvious imo, it’s especially confusing for those moving from an rpm distro. Thanks
There are very few instances where update will cause a breaking change in ROME. Given we haven’t done the updates to ROME yet, you should be okay. Let us know if there are things that were working that are not working now. This would also be a good read to get more familiar with our package update process:
Thats a good question. I have been using debian Testing for a while and the docs are quite confusing when it come to doing updates I was using apt update && apt upgrade for a while but one day that nolonger worked the fix was using apt dist-upgrade so have been using that ever since. I think it has something to do with how apt handles package conflicts during the upgrade but not sure. Is dsync comparable to dist-upgrade in this sense? You could probably just run dsync and that fix anything update missed but wait for someone who knows what they’re talking about.
Yeah things seem to work alright at this moment, so I guess I leave it be. There are some little issues like VMware not completely uninstalling (couldn’t get it working because of the Clang/GCC stuff), broken pop-up transparency in Qt5 apps and a weird dependency conflict with the Nicotine+ package from the Extra repo (had to use --allow-erasing since I really need it installed but now it nags about conflicting lib64appindicator packages), but those are likely unrelated, will maybe test on a VM
and that should pull any packages dnf upgrade or dnf upmissed.
The issue is more that dnf up might miss some packages that dnf dsync pulls. OpenMandriva uses distro-release-repos-pkgprefs which is the current list of preferred packages and dsync reads that up does not. And in OMLx Cooker and ROME distro-release-repos-pkgprefs package is changed by developers often.
dnf up does not read the distro-release-repos-pkgprefs and only tries to find what it thinks is the highest numerical package name. That can result in changes by OM devs being missed.
For information the distro-release* stack look something like this:
If you don’t find what you are looking for, try an Internet search. One can find out a lot from documentation or forum posts at other Linux distros. If user finds something written for another distro but you have some doubt ask at OpenMandriva Chat.
For serious technical issues and package/feature requests please file a bug report here.
Note: We are a small group. All the contributors and developers here are unpaid volunteers.
You can make OpenMandriva grow and improve by getting involved
Any help with testing would be appreciated whether one is technically proficient or a very non-technical user. The more people and more hardware we can get involved the better we can make OMLx releases and packaging. We do a lot of testing in VM’s as well. Developers tend to use Qemu, most user level testers use VirtualBox.
Also for cooker btw, but distro-sync in Rock won’t hurt either and big fat warnings are better done (and read) if short
Users can read more at the link provided.
