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.

                      I installed for the first time on an SSD. Since it's a rig I'm modifying myself, I can only spend a little time here/a little time etc.
                      But I can't tell any apparent differences with 4.5 which is a good thing. seamless as it was indended.

                        brent I installed for the first time on an SSD.

                        How did you like the performance of the SSD? The first time I used one, I was pretty impressed. I started looking for a seat belt.

                            WetGeek Where have you been all my life?

                            that was my response 🙂. snappy devil. It was a 2.5 Sata ssd so I wasn't expecting a spaceship...but pretty noticeable from the HDD.
                            Installing backup distro B 'alongside' solus at later date. Thanks for asking

                              ermo ah, so thats what defines the new epoch, get it now
                              thanks for explaining

                                labeled

                                Depends on what happens once we can update the baselayout package again.

                                You may end up in a situation where the file you edited does not get upgraded, because eopkg determines that you have edited it, and then goes on to just save new updates to a backup file name so you never see them.

                                  ssr14 Omg, you don't read much stuff do you. It's at the start of this post.