Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrading gogs on CentOS 6 to gitea 1.0.0 #627

Closed
RichieB2B opened this issue Jan 9, 2017 · 8 comments
Closed

Upgrading gogs on CentOS 6 to gitea 1.0.0 #627

RichieB2B opened this issue Jan 9, 2017 · 8 comments
Labels
type/docs This PR mainly updates/creates documentation
Milestone

Comments

@RichieB2B
Copy link
Contributor

RichieB2B commented Jan 9, 2017

I just went through the process of upgrading gogs 0.9.97 to gitea 1.0.0. Since I used the RPM to install gogs I needed to modify several things to get things working.

I started following this guide, but soon realized all you need from there is:

cp -r gitea-v1.0.0/options /opt/gogs/options

Interestingly enough that guide does not tell you to install the gitea binary, which I installed as /opt/gogs/gitea-1.0.0-linux-amd64

The only real problem is that the gitea binary is linked against glibc 2.14:

$ ./gitea-1.0.0-linux-amd64 web
./gitea-1.0.0-linux-amd64: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by ./gitea)

The solution for this is to install glibc 2.14 in /opt.

To load the new libc I created a new script /opt/gogs/gogs (replaces the old gogs binary):

#!/bin/sh

LD_LIBRARY_PATH=/opt/glibc-2.14/lib /opt/gogs/gitea-1.0.0-linux-amd64 "$@"

I linked this file to /opt/gogs/gitea because gitea writes this path in ~/.ssh/authorized_keys

ln -s /opt/gogs/gogs /opt/gogs/gitea

After this gitea is a true drop-in replacement for gogs. Perhaps this above can be documented somewhere.

@tboerger
Copy link
Member

tboerger commented Jan 9, 2017

For 1.1.0 we will provide binaries without the glibc requirement. Beside that we still want to provide proper rpms for the major distros and this will also resolve this issue

@lunny
Copy link
Member

lunny commented Jan 10, 2017

So we need a document update to close this issue?

@tboerger
Copy link
Member

@lunny at least we should add a note to the docs for now

@lunny lunny added this to the 1.1.0 milestone Jan 10, 2017
@lunny lunny added the type/docs This PR mainly updates/creates documentation label Jan 10, 2017
@RichieB2B
Copy link
Contributor Author

I modified my solution slightly because after gitea rebuilds /home/gogs/.ssh/authorized_keys it puts /opt/gogs/gitea in there. So this needs to be a wrapper script as well.

@donguidou
Copy link

The nightly builds still require glibc-2.14.

@tboerger
Copy link
Member

The nightly builds still require glibc-2.14.

Of course, because the issue is not resolved yet.

@lunny
Copy link
Member

lunny commented Jan 25, 2017

Is there any docs updated to close this?

minecrafter added a commit to minecrafter/docs-1 that referenced this issue Feb 9, 2017
In the future, we will provide builds for these older distributions (go-gitea/gitea#551). For now, document the issue and suggest upgrading or building from source.

Closes go-gitea/gitea#627
lunny pushed a commit to go-gitea/docs that referenced this issue Feb 9, 2017
In the future, we will provide builds for these older distributions (go-gitea/gitea#551). For now, document the issue and suggest upgrading or building from source.

Closes go-gitea/gitea#627
@tboerger
Copy link
Member

tboerger commented Mar 7, 2017

The upcoming release 1.1.0 won't depend on glibc anymore because of #985

@go-gitea go-gitea locked and limited conversation to collaborators Nov 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/docs This PR mainly updates/creates documentation
Projects
None yet
Development

No branches or pull requests

4 participants