nolan yes, from the user experience from the last epoch, it is progressive, like a normal update, the script for the new epoch would be installed then activated in a later moment, the user wouldn't notice the transition.
Harvey It tells you what will happen and when it is planned to happen: The update script is already in the Unstable repository for opt-in testing. After it is synced to the Shannon (Stable) repository on October 17, users can opt-in to run the script on their systems for wider feedback and testing. One week after that, assuming that no major blockers have been found, on the sync of October 24, all users on Shannon will automatically undergo the epoch transition.
DinimixisDEMZ I'm stable user... I need use the eposh command (echo EPOCH_ENABLE=yes | sudo tee /etc/sysconfig/epoch)...? or i only wait for october 24 update?
alfisya DinimixisDEMZ Just wait until 24th of October. It will done automatically. As already said in the blogpost and @Harvey already highlighted.
brent AlphaElwedritsch if echo EPOCH_ENABLE=yes | sudo tee /etc/sysconfig/epoch was the only requirement, I did as well. alfisya Just wait until 24th of October. It will done automatically. nah.. 🙂
craigtoyoracer EbonJaeger Clear and concise, I thank you and the team for great communication . I find it fascinating watching the evolution over the years and it just keeps getting better. Well done.
WhiteWolf I am in new epoch already 😉 p.s. I see "No status data could be sent: $NOTIFY_SOCKET was not set" any concerns about it? Just playing with the script. I was moved to new repo and solus-sc was removed 🙁
brent WhiteWolf p.s. I see "No status data could be sent: $NOTIFY_SOCKET was not set" any concerns about it? Just playing with the script. I was moved to new repo and solus-sc was removed 🙁 can't answer that. I was expecting the download/install Discover to be the the immediate next step. Surprised.
alfisya WhiteWolf So the new software center not get installed? What DE are you using when running the epoch script?
silke WhiteWolf The $NOTIFY_SOCKET was not set error is because you ran the script directly instead of the systemd service. The error is nothing to worry about, but I have included a fix for it (along with fixes for other reported issues) here nonetheless.
WhiteWolf alfisya wasn't needed as I installed it manually some time ago. So script worked nice. I will play with it this week more, test cases: Old iso with solus-sc only and will run the script Manually adding polaris repo with only solus-sc installed Manually adding polaris repo with solus-sc and gnome-software installed And will let you know how it went. Looks like all those cases are covered and work nicly 🙂
brent EbonJaeger question to you or any dev: I've had negative experiences in the past with kpackages on Budgie (baloo, kwallet, falkon) so can I uninstall/remove Discover as soon as you install it? And continue to use Gnome Software (well eopkg mainly)? Asking because I don't know what's (or what will be) baked into what when the switcheroo comes. Thank you. edit/added question mark
AlphaElwedritsch Since my early days with Solus, I've exclusively used the console: eopkg and flatpak. I've never used SC or Gnome Software Center or any other graphical GUI
AlphaElwedritsch Borderliner Once the epoch bump is complete, we will be updating GNOME to 49. This release uses API only present in a newer systemd, so we can’t really update it before then. After that, we will be going into feature freeze so we can start creating and testing new ISOs for a Solus release so new users can begin using Solus straightaway without having to go through the epoch transition process. Wait or start... 😉 But I don't know why you should wait...
brent AlphaElwedritsch Wait or start... 😉 But I don't know why you should wait... tell him the part about ETAs 🙂
theabdulhakim I really loved the Solus Software Center. GNOME Software has always felt slow to me — even though it offers a lot of apps, the overall experience is sluggish.
