Hurray! 52 updates processed after launching your terminal command on the Shanon repo.
Thanks Josh and the whole team, it seems good to be out of this bad dream, Solus didn't deserve to be forgotten.

Also, I'd like to know if there are any plans to reactivate a link to the little help modules in Solus, they were so convenient when you needed a specific terminal command for example (of course, I can understand that it will take time to restore them).

    macmau74 Si da un pochi di anni, mi trovo bene, però in questi ultimi tempi ha avuto diversi problemi e dopo un totale fermo di 3 mesi circa è ripartita, da pochissimo, in questo esatto momento stanno cercando di riparare e aggiornare tutto il possibile, la definerei convalescente. Il forum è molto utile. E una distrubuzione molto orientata al pc, se vuoi dei server non è la distro giusta. Mai avuto problemi col fatto che è rolling, però non sono in tanti a lavorarci per cui non sempre stanno dietro agli aggiornamenti e non trovi tutti i pacchetti, ma trovi quasi sempre soluzioni (flatpack e simili) alternative e qui ti aiutano molto in questo senso. Inoltre spesso di default trovi pacchetti che altrove non sai neanche esistano...cioè di base le cose che fanno le fanno bene e in modo innovativo.

        FAb7D Ciao, si sono anche io sul Solus da qualche anno, anche se solo con un laptop di casa. Dopo l'angoscia degli ultimi mesi, l'ultima settima è stata entusiasmante ;-) Ikey è un genio, Josh una garanzia.
        Mi devo scusare perché non ho riletto il precedente post prima di pubblicare.. e Ti volevo chiedere come hai installato Dike che mi sembra venisse distribuito solo come .deb

            macmau74 Non è che mi ricordo molto bene, cmq quanto segue:
            -installato libappindicator,
            -copiato dal pacchetto debian gosign2 il contenuto delle cartelle data/opt e data/usr rispettivamente su /opt e /usr rispettando i percorsi in termini di sottocartelle.

                FAb7D grazie!
                sul tema ( ma non con riferimento a Solus) avevo trovato anche questo:
                Per non dar noia qui, nel caso ti posso trovare altrove? Matrix, Telegram?

                    Is this normal? I updated (which had no errors) and rebooted. I'm paranoid so I always run an eopkg check.

                    zsolus@zsolus ~ $ eopkg check sudo
                    \Checking integrity of sudo Broken
                    Access denied: /usr/share/defaults/etc/sudo/sudoers
                    Corrupted file: /usr/lib/tmpfiles.d/sudo.conf

                    Want to make sure all is good before I switch the rest of the machines over.

                      macmau74 Seguo it.comp.os.linuxiniziare (newsgroup) e poco o nulla gli altri social...

                          FAb7D ok. Cancello i miei messaggi non pertinenti con il thread, prima che arrivino gli admin! Alla prossima!
                          ah no, vedo che non mi è possibile..

                            Question, perhaps a stupid one: What is CDN? Do I have to change anything in the future, when regular update channel is back , if I go the CDN route now?

                              elfprince CDN stands for Content Delivery Network. It's a web term for a "smart" hosting that serves you content from a location close to you automatically (without any manual configuration of mirrors). This is why people are reporting that package download speeds are significantly faster now than they used to be. In our case we're also using this for caching files with the CDN provider which means we can reduce the bandwidth that hits our actual package repo.

                              If you switch to the CDN repo today you won't have to do anything in the future. The CDN repo is likely to become our permanent repo but even if we have to go a different route we'll still push an update to switch you to the new endpoint automatically (just like we'll likely push an update to switch the RIT users over to the new CDN endpoint).

                                  Installed Solus from the 4.3 ISO and updated from the CDN today.
                                  I updated from the terminal, and halfway through the update the session ended.
                                  I used eopkg rdb and ran the update from TTY, and everything worked out.
                                  It's good to be back.

                                  Did an update, following the recipe above. 63 packages, roughly same speed as before. No problems with the update, but will boot tomorrow. Only a short time left till shutdown/sundown. 😃

                                  ReillyBrogan
                                  If I understand the CDN route correctly, then how does Solus ensure that the packages served by the CDN are exactly the same as those served by the main server? (the one at RIT at the moment).
                                  I'm thinking along the security and integrity perspectives of these updated packages.
                                  To remove all doubt, should users update directly from Solus servers?

                                      snowee almost everything nowadays is served via some kind of CDN. I do not think caching the content on the edge (CDN) is something that could be easily poisoned by malicious party.
                                      Correct me if I'm wrong, but Solus moved everything away from RIT premises and now using the SerpentOS or a copy of it.

                                          snowee then how does Solus ensure that the packages served by the CDN are exactly the same as those served by the main server

                                          The CDN pulls data from our package server directly in the event of cache misses and merely stores them on their edge servers / network closer geographically to the user. We can perform cache invalidation at any point in time. Alongside this, eopkg will validate the shasum from the index. We do not have any security concerns related to the CDN.

                                          snowee To remove all doubt, should users update directly from Solus servers?

                                          Users should use the CDN and once RIT is syncing from us, I'll be pushing a modification to eopkg that will convert existing systems using RIT to the CDN automatically. Intentionally using the non-CDN will mean that not only are you hammering our server more for no reason (when that bandwidth could otherwise be soaked up by the CDN service, to a magnitude of a 97% reduction from the metrics I've seen), but you're doing it at the cost of a worse download experience.

                                          presianbg now using the SerpentOS or a copy of it.

                                          This is not correct. While our infrastructure is no longer hosted by RIT, what we are using is still the previous build infra tech (with various fixes) such as our build management scripts, ferryd, and solbuild. They haven't been replaced with summit and vessel from Serpent OS yet and we're likely quite far out from that as they are coupled closely to moss (Serpent OS package manager).

                                                Recovered a Solus Plasma backup I made more than a year ago with Clonezilla, with an AMD RX 570.
                                                Now I have a GeForce 3060 Ti.
                                                Booted up perfectly (with nouveau), changed repo, upgraded:

                                                Rebooted, launched DoFlicky and I am on sail again!
                                                Glad to see you back, @JoshStrobl! (and the rest of the team, ofc)

                                                Changed to CDN, made the update, went through everything perfectly, except:

                                                > sudo eopkg check
...
Checking integrity of sudo       Broken
Checking integrity of python3    Broken
...

                                                Doing:
                                                > sudo eopkg install --reinstall sudo python3

                                                That fixed python3, but not sudo. sudo itself seems to work, though.

                                                Thank you, BTW, for bringing everything back to life. I'm happy again.