I wanted to let everyone know there’s a new package in Cooker/Rome that’s available for testing. It’s a graphical updater and installer. Install the package om-updater, and you get a very basic graphical installer and even better, a system tray-based updater you can configure to run on startup.
The usual caveats apply: this is unofficial, it needs testing, etc. But please, give it a try and let me know what you think.
For more information, see the project page, and if you have particular issues, please add them there.
This looks like a useful little addition, especially for ROME/Cooker users who prefer having something visible in the tray instead of remembering to check for updates manually. I’d definitely give it a try. The configurable startup option sounds particularly handy, and testing it over a few updates should give a good idea of how reliable it is in everyday use.
Yeah; my goal was to give non-technical users (i.e., my mom) an easy way to keep their systems up to date. This is in keeping with the spirit of the old Mandriva Linux, so I thought it would be good to have in OpenMandriva.
Hey I tried this out and it is not working for me. The installer will open but locks up with this error when I click on the flatpack tab. The updater fail to launch at all.
If you want me to try anything to help fix this let me know
I’ll have a look at the installer error. The updater should work fine; it doesn’t appear until after it’s checked to see if updates are available, so it can show the right icon.
I dont know if it makes any difference but the first thing I clicked on was the updater. I had just done a system update a minute before so I wasnt thinking about an installer.
I thought the errors you posted came from the installer, not the updater? They’re two separate programs. The updater launches and just sits in your tray. If you have no updates, it’s just a green circle. When you have updates, it turns red with an exclamation point.
I guess I didnt catch that, so yes the updater just did update brave for me. I mistook that bright red explamation point for an error and just closed it.. maybe I should have drank my coffee before posting this morning.
So I fundamentally misundertood how your program works. I thought it was two seperate gui’s that you brought up though the application menu. I did not realize that the updater has to reside open in the system tray for the installer to work.
So now I can still get the Installer to crash, when typing in the search box, switching between rpm and flatpak works fine. However if nothing is in the search box hitting the flatpak tab causes the program to hang. Otherewise everything seems to work good, I installed stella from our rpms through your installer and it worked well.
Is there a reason why the updater asks for the admin password when updating Flatpaks? I have been installing and updating Flatpaks without the admin password when using the terminal or Flatdrake.
They are two separate programs. The updater is just to notify you when updates are available, and then to install those updates. The installer is a graphical installer meant to do the functions of dnfdrake, but with a simpler interface. Neither one requires the other, but they’re packaged together.
Yes; Flatpaks can be installed via sudo as well, which makes them available system-wide. If you install a Flatpak as just your user, that Flatpack is available only to your user. This is fine on a system that only one user uses, but if it’s a shared computer, you’ll want to install your Flatpaks via sudo, and thus update them also via sudo.
I have no idea. I just know that Flatpaks can be installed system-wide, and they can be installed for just the user. Since I can’t predict how each user will decide to do it, the update updates user Flatpaks, and then it asks for the password so it can update system Flatpaks.
Fair enough. From a securuty point of view, much can be said for isolating apps as much as possible. From a convenience POV, much can be said for not doing so.
I’m the only user of my machine, so I don’t mind isolating my stuff, thoug I have had to grant further permissions to Flatpacks to make them usefull: Giving SPEK access to my folder full of music, for example.
Okay, I just built a new version that’s available in Cooker. If you’re running Cooker, you can just update. I don’t know if you’re on x86_64 or znver1, but if you’re running ROME, you can still install it this way:
Since this program handles packages all round (installation, removal, and update), why not call it a more generic name?
For example OM-Software, OM-Store or OM-Applications.