lal309

joined 2 years ago
MODERATOR OF
[–] lal309 5 points 8 months ago

Thank for the dup vs up tip. I found it odd having to do both.

[–] lal309 1 points 8 months ago (1 children)

Did not find any meta packages installed

[–] lal309 1 points 8 months ago (2 children)

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?

[–] lal309 2 points 8 months ago (1 children)

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

[–] lal309 2 points 9 months ago

Following. Sounds interesting.

[–] lal309 2 points 9 months ago

The council members would like to “speak to you” about a recent “developments” we’ve been made aware of. We assure you, nothing will happen to you…

[–] lal309 26 points 9 months ago

Lemme fix the headline for you.

HashiCorp joins the list of companies and software killed by IBM.

[–] lal309 1 points 9 months ago

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

[–] lal309 1 points 9 months ago

This looks interesting too

[–] lal309 5 points 9 months ago (1 children)

Love that username tho!! Yeah might just do RSS. I already run FreshRSS and it’s ability to filter stuff would probably come in handy too

[–] lal309 5 points 9 months ago

This sounds like the simplest and most effective solution. Thanks!

[–] lal309 1 points 9 months ago (1 children)

Interesting… do you like this way more or the rss route more?

view more: ‹ prev next ›