I’ve been thinking about running EndeavorOS but seeing people here complain about Arch breaking when the AUR is used, makes me shy away from EOS. Do you use packages from AUR and have you had any issues with the OS? Running Tumbleweed right now.
Something else to check is your infill percentage. Make sure you don’t have it at 100% (unless you absolutely need to build something completely solid). Another thing to check is your print speed. Too low and it will take a decade to print something simple. Too fast and it cause your print to fail. At this point we will all be throwing spaghetti against the wall. Can you share a screenshot of your settings?
Took me a bit to see these patterns/packages (mainly because I've never used Yast). I can see these patterns and the software that they install, is it better to use Yast to remove the packages and the patterns and mark them as "Don't install that sh.t again" or through cli?
Okay so I ran sudo zypper search pattern* and found one called patterns-games-games and patterns-office-office. I assume these are the "patterns" responsible for installing stuff like Kmines, KSoduku, LibreOffice, etc which I don't want. I also assume I can run sudo zypper remove patterns-games-games to remove it all? Or do I need to remove the packages individually and then remove the pattern?
Well when I boot after reboot, I see updated software packages and running uname-a shows the new kernel zipper said it was going to install. Based on that I assume that the answer would be no
Not quiet. I was running gitea before so my mount was ./gitea:/data but since switching over to forgejo, I renamed my ./gitea directory to ./forgejo. Adjusted my compose file to have a mount of ./forgejo:/data.
Now inside of that renamed forgejo directory, there are a bunch of gitea references and even one more directory called gitea. When I migrated everything worked right away but since I wanted a cleaner transition, I renamed and switched all gitea references to forgejo but went I brought the stack back online, it went belly up.
As a troubleshooting step, I recreated my compose file and created a new empty ./forgejo on a different machine just to see what a new and fresh install would look like and the forgejo stack itself created all kinds of gitea references and gitea directory once I brought it up. So to fix my original deployment, I reverted all the references back from forgejo to gitea and everything worked again.
For fun, I went out to codeberg to look at the Dockerfile and saw that they had a bunch of gitea things within their own Dockerfile so nothing I can do for now
Uh oh. How did the partition get deleted from your fstab?