Upgrade to master not working ? #3566

New Issue

GiteaMirror · 2025-11-02T05:17:29-06:00

GiteaMirror commented

2025-11-02 05:17:29 -06:00

Originally created by @theAkito on GitHub (Jul 10, 2019).

Gitea version (or commit ref): de facto: b04a1d9d63 but should be: b84a251fca
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

Originally created by @theAkito on GitHub (Jul 10, 2019).   - Gitea version (or commit ref): de facto: b04a1d9d639a285db6c3fb9fd675ccb22a04fd14 but should be: b84a251fca78784682d49e3699eaae51203f8ffd - Git version: 2.11.0 - Operating system: DietPi (based on Raspbian Stretch) - Database (use `[x]`): - [x] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] 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 1. ``` cd "$GOPATH/src/code.gitea.io/gitea" ``` 2. ``` git fetch && git pull ``` 3. ``` go get -d -u code.gitea.io/gitea ``` 4. ``` TAGS="bindata" make generate build ```

GiteaMirror added the issue/stale label 2025-11-02 05:17:29 -06:00

GiteaMirror closed this issue

2025-11-02 05:17:29 -06:00

GiteaMirror commented

2025-11-02 05:17:30 -06:00

@jolheiser commented on GitHub (Jul 10, 2019):

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 b84a251fca (latest)

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

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

@jolheiser commented on GitHub (Jul 10, 2019): `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 b84a251fca78784682d49e3699eaae51203f8ffd (latest) I reset my commit to the one you mentioned above (b04a1d9d639a285db6c3fb9fd675ccb22a04fd14) and ran my command again. `git show` is giving me b84a251fca78784682d49e3699eaae51203f8ffd again Were any errors given by chance? I'm not sure what else could have happened.

GiteaMirror commented

2025-11-02 05:17:30 -06:00

@stale[bot] commented on GitHub (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[bot] commented on GitHub (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.

GiteaMirror commented

2025-11-02 05:17:31 -06:00

@stale[bot] commented on GitHub (Sep 22, 2019):

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

@stale[bot] commented on GitHub (Sep 22, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.

GiteaMirror referenced this issue

2025-11-02 12:23:57 -06:00

[PR #3566] [MERGED] Fix remove team member issue #17000

GiteaMirror referenced this issue

2025-11-02 12:24:01 -06:00

[PR #3570] [MERGED] Fix remove team member issue (#3566) #17003

Sign in to join this conversation.