Harvey Ahh ok thats the part I was missing
I skipped budgie during that time and used mate so prob why it didnt click.
Thanx for the reply

      Axios if you still got file-roller you don't need engrampa. engrampa drags in xreader, doesn't it? I would avoid both if you are able to. glad to know that stuff is not on 4.6

          brent I would avoid both if you are able to.

          ....why...? And they most certainly are on 4.6.

              brent You got confused like I did
              Harvey explained it proper.

                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 👍️

                          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

                                AlphaElwedritsch

                                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.

                                  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.

                                        ermo

                                        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.

                                        • ermo replied to this.

                                            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.

                                              ermo 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.

                                              For me, everything is fine. I'm not confused either, because I already understood the "epoch bump". But I didn't know until now that /etc/os-release was also related to it.
                                              I just wanted to report it.
                                              So, everything is fine so far.
                                              Thanks for the explanation.
                                              Keep at it. You're doing a GREAT job

                                                Sebastian I guess Solus 5 will named "End Game", "Eternity" or something that tells us about the future of the distro

                                                  Lucien_Lachance

                                                  We use "epoch" it the sense "the start of a new timeline" or "era", because there will be a "before" (python2 eopkg and Solus SC is the default in the package repo we use) and an "after" (python3 eopkg and KDE Discover/Gnome-Software will be the default in the package repo we use, python2 eopkg will not be around and python2 may be removed entirely, depending on the outcome of our internal R&D).

                                                  This will be a pretty big deal for the people maintaining the distro. For users, it should ideally be super boring and uneventful, paradoxically enough.