I have Budgie fully updated but still have fileroller am I missing something?
Solus 4.6 Convergence Released
File Roller will not be removed automatically. It may also still be needed as a dependency of other installed software.
- Edited
EbonJaeger So I have to install engrampa its not installed
Same for xreader to I guess
- Edited
Axios
That would be correct. Just like in the past where nemo
replaced nautilus
for Budgie users, defaults are usually not forced on existing installs because we have no way of knowing if a user deliberately installed the alternative to our new default or not.
We can only use a "replaces" which forces the swap when the old package is not staying around, such as when switching to hard fork of a dead project. Otherwise Gnome users would be forced to switch too for no reason.
brent I would avoid both if you are able to.
....why...? And they most certainly are on 4.6.
EbonJaeger not a fan of apps that have their own pdf reader and /or terminal outside of system pdf reader etc. stuff that leads to duplicate default apps happens sometimes--see it more elsewhere to be clear I have not seen it here yet
brent Engrampa is an archive manager from the MATE project. XReader is a dedicated PDF reader application from the XApps project. I'm a bit confused because I don't see the connection.
EbonJaeger I got it. Multi-tasking/communicating not my strength tonight apparently. please disregard.
Congrats with the new ISO release! Tried XViewer, it's ok as gnome viewer replacement ️
- Edited
Harvey
Tried the 4.6 plasma right now...
Solus-Plasma-Release-2024-10-14.iso
Live session
Installed system
both are reported as 4.5.
Correct, or error?
ive read the blog posts but i dont get what epoch bumb is, maybe its not relevant to regular users
Expected. The difference is the 4.6 ISO has a hacky solution to set /etc/os-release to 4.6 which is where some applications like info center on Plasma get the information.
Lucien_Lachance Check the usr merge blog post for detailed explanation
Sebastian i did, and didnt get it
- Edited
AlphaElwedritsch Correct, or error?
Both.
This is a bug that we cannot fix the correct way yet*, because the package that owns /etc/os-release
(the baselayout
package) cannot be reliably upgraded without potentially bricking installed systems.
We are in the process of preparing a switch to a newer package repository version (v1 -> v2). This process is called the "epoch bump" in our internal discussions. Completing this process will enable us to update the baselayout
package again.
We understand that it must be very confusing for some users to not see the updated version 4.6 in /etc/os-release
.
However, in reality, the only thing that is different between a fully updated Solus 4.5 (or 4.4, or 4.3, or 4.2, or 4.1, or (...)) system and a fully updated Solus 4.6 system, is currently the contents of the /etc/os-release
file.
In other words:
Every single other package on a fully updated 4.5 system is identical to the packages on a fully updated 4.6 system.
Lucien_Lachance i did, and didnt get it
Do you understand now?
*: We are looking at workarounds that will silently update the /etc/os-release
file on older Solus installs, just so we don't have to spend oodles of time engaging with confused users whose expectations don't match reality.
EDIT: As of the sync on 2024-10-29, the above issue should be fixed.
- Edited
WetGeek I've recently created four Solus VMs based on the newly released .ISO files, and I can confirm that all four of them report their versions as 4.6.
This is because we manually overwrite the contents of /etc/os-release
on ISO creation currently.
This is also an ugly workaround. But it's better than having people think they downloaded a 4.5 ISO and then re-downloading and trying to re-install, only to get the same outcome...
As I said, we are working on a workaround for the version shown. Stay tuned for ... wait for it ... updates.