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

Upgrade to master not working ? #7415

Closed
2 of 7 tasks
theAkito opened this issue Jul 10, 2019 · 3 comments
Closed
2 of 7 tasks

Upgrade to master not working ? #7415

theAkito opened this issue Jul 10, 2019 · 3 comments

Comments

@theAkito
Copy link

  • Gitea version (or commit ref): de facto: b04a1d9 but should be: b84a251
  • Git version: 2.11.0
  • Operating system: DietPi (based on Raspbian Stretch)
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist: x

Description

Ran the upgrade as shown here: https://docs.gitea.io/en-us/install-from-source/ to upgrade to master, without checking out to any version. git branch confirms master branch. But git show displays commit b04a1d9d639a285db6c3fb9fd675ccb22a04fd14 which is an old commit from April 1st.

Now I did a git fetch && git pull in $GOPATH/src/code.gitea.io/gitea, so it updated to the newest commit. Then I ran go get -d -u code.gitea.io/gitea

Is this a gitea or go bug?



Workaround

cd "$GOPATH/src/code.gitea.io/gitea"
git fetch && git pull
go get -d -u code.gitea.io/gitea
TAGS="bindata" make generate build
@jolheiser
Copy link
Member

go get -d -u code.gitea.io/gitea should download the most recent version of https://github.com/go-gitea/gitea
There are some cases where it would behave differently, but those are generally limited to using modules or other development.


I ran the following, moving GOPATH to a tmp location for testing

GOPATH=/tmp/go go get -d -u code.gitea.io/gitea

And now git show is giving me b84a251 (latest)

I reset my commit to the one you mentioned above (b04a1d9) and ran my command again.
git show is giving me b84a251 again

Were any errors given by chance? I'm not sure what else could have happened.

@stale
Copy link

stale bot commented Sep 8, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale stale bot added the issue/stale label Sep 8, 2019
@stale
Copy link

stale bot commented Sep 22, 2019

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale stale bot closed this as completed Sep 22, 2019
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants