Conversation
Notices
-
Embed this notice
andy (andy@friendica.hubup.pro)'s status on Saturday, 07-Jan-2023 03:47:03 JST andy @utzer let me understand your current situation?
How is this the currently installed Gitea 1.17.4 provided on your system?
Can you upgrade to Gitea 1.18.0? This is needed for migrating. Migration from gitea to forgejo requires the same version.-
Embed this notice
Forgejo (forgejo@floss.social)'s status on Saturday, 07-Jan-2023 03:47:03 JST Forgejo @andy @utzer it's fine to upgrade directly from #Gitea 1.17.x to #Forgejo 1.18.x. There's no need to go via Gitea 1.18. (You still need to do backups etc just like with a Gitea major version upgrade.)
~ @caesarSteffen K9 ? likes this. -
Embed this notice
andy (andy@friendica.hubup.pro)'s status on Saturday, 07-Jan-2023 03:47:05 JST andy @utzer I moved to forgejo. git.hubup.pro
It was a simple process and really straight forward. I use the binary and not a distro package.
One has to merely upgrade to the latest gitea version and then drop the forgejo binary in place, replacing the gitea binary. Future upgrades than will be as usual. -
Embed this notice
utzer (utzer@social.yl.ms)'s status on Saturday, 07-Jan-2023 03:47:05 JST utzer @andy
Future upgrades than will be as usual.
What is the usual way? For us it was pacman -Syu up to now. ?
Are you into giteaforgejo, maybe you'd like to volunteer?
I think the best is to keep using a package, this will somewhat ensure that the Forgejo versions dependencies are fulfilled by the other packages I guess, at least if the maintainer is doing a good job. -
Embed this notice
utzer (utzer@social.yl.ms)'s status on Saturday, 07-Jan-2023 03:47:07 JST utzer Hello @developers
I asked the maintained if the #Arch #Linux #Gitea package if he plans to switch the upstream source to Forgejo and he responded that he does not plan to do so.
I don't want to share more details publicly.
What should we do with the gitea instance git.friendi.ca? Keep running gitea or switch to #Forgejo?
-
Embed this notice