github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-07-15 20:09:18 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Upgrade 1.0 (docker image) to 1.1.0 (docker image) #449

New Issue
Closed
opened 2025-11-02 03:23:48 -06:00 by GiteaMirror · 5 comments
GiteaMirror commented 2025-11-02 03:23:48 -06:00
Owner
Copy Link

Originally created by @avelino on GitHub (Mar 9, 2017).

  1. Please speak English, this is the language all of us can speak and write.
  2. Please ask questions or configuration/deploy problems on our Gitter channel: https://gitter.im/go-gitea/gitea
  3. Please take a moment to search check that your issue doesn't already exist.
  4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report.

You MUST delete the content above including this line before posting, otherwise your issue will be invalid.

  • Gitea version (or commit ref): 1.1.0
  • Git version:
  • Operating system: Linux (run via docker image)
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

web_1       | 2017/03/09 19:40:19 [T] Custom path: /data/gitea
web_1       | 2017/03/09 19:40:19 [T] Log path: /app/gitea/log
postgres_1  | ERROR:  relation "IDX_repo_unit_S" already exists
postgres_1  | STATEMENT:  CREATE INDEX "IDX_repo_unit_S" ON "repo_unit" ("repo_id","type");

Screenshots

screenshot 2017-03-09 16 42 48

Originally created by @avelino on GitHub (Mar 9, 2017). 1. Please speak English, this is the language all of us can speak and write. 2. Please ask questions or configuration/deploy problems on our Gitter channel: https://gitter.im/go-gitea/gitea 3. Please take a moment to search check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. **You MUST delete the content above including this line before posting, otherwise your issue will be invalid.** - Gitea version (or commit ref): 1.1.0 - Git version: - Operating system: Linux (run via docker image) - Database (use `[x]`): - [x] PostgreSQL - [ ] MySQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [x] No - [ ] Not relevant - Log gist: ## Description ``` web_1 | 2017/03/09 19:40:19 [T] Custom path: /data/gitea web_1 | 2017/03/09 19:40:19 [T] Log path: /app/gitea/log postgres_1 | ERROR: relation "IDX_repo_unit_S" already exists postgres_1 | STATEMENT: CREATE INDEX "IDX_repo_unit_S" ON "repo_unit" ("repo_id","type"); ``` ## Screenshots ![screenshot 2017-03-09 16 42 48](https://cloud.githubusercontent.com/assets/31996/23767489/7b7d3c3c-04e7-11e7-9b8b-4eb695d6f7f1.png)
GiteaMirror added the type/questiontopic/deployment labels 2025-11-02 03:23:48 -06:00
GiteaMirror commented 2025-11-02 03:23:48 -06:00
Author
Owner
Copy Link

@tboerger commented on GitHub (Mar 9, 2017):

Repo units have been introduced with 1.1, so it can't be possible that this index have been existing before?

@tboerger commented on GitHub (Mar 9, 2017): Repo units have been introduced with 1.1, so it can't be possible that this index have been existing before?
GiteaMirror commented 2025-11-02 03:23:49 -06:00
Author
Owner
Copy Link

@avelino commented on GitHub (Mar 9, 2017):

Yep:

avelino@avelino:~/docker-gitea$ sudo docker-compose up
sudo: unable to resolve host avelino.riska
Starting dockergitea_pg_data_1
Starting dockergitea_data_1
Starting dockergitea_postgres_1
Recreating dockergitea_web_1
Attaching to dockergitea_data_1, dockergitea_pg_data_1, dockergitea_postgres_1, dockergitea_web_1
dockergitea_data_1 exited with code 0
web_1       | Mar  9 22:19:58 syslogd started: BusyBox v1.24.2
postgres_1  | LOG:  database system was shut down at 2017-03-09 22:19:49 UTC
dockergitea_pg_data_1 exited with code 0
web_1       | Mar  9 22:19:58 sshd[20]: Server listening on :: port 22.
postgres_1  | LOG:  MultiXact member wraparound protections are now enabled
web_1       | Mar  9 22:19:58 sshd[20]: Server listening on 0.0.0.0 port 22.
postgres_1  | LOG:  autovacuum launcher started
postgres_1  | LOG:  database system is ready to accept connections
web_1       | 2017/03/09 22:19:59 [T] Custom path: /data/gitea
web_1       | 2017/03/09 22:19:59 [T] Log path: /app/gitea/log
postgres_1  | ERROR:  relation "IDX_repo_unit_S" already exists
postgres_1  | STATEMENT:  CREATE INDEX "IDX_repo_unit_S" ON "repo_unit" ("repo_id","type");
web_1       | 2017/03/09 22:20:00 [T] Custom path: /data/gitea
web_1       | 2017/03/09 22:20:00 [T] Log path: /app/gitea/log
postgres_1  | ERROR:  relation "IDX_repo_unit_S" already exists
postgres_1  | STATEMENT:  CREATE INDEX "IDX_repo_unit_S" ON "repo_unit" ("repo_id","type");
^CGracefully stopping... (press Ctrl+C again to force)
Stopping dockergitea_web_1 ... done
Stopping dockergitea_postgres_1 ... done
avelino@avelino:~/docker-gitea$ cat docker-compose.yml
web:
  image: gitea/gitea:1.1
@avelino commented on GitHub (Mar 9, 2017): Yep: ``` avelino@avelino:~/docker-gitea$ sudo docker-compose up sudo: unable to resolve host avelino.riska Starting dockergitea_pg_data_1 Starting dockergitea_data_1 Starting dockergitea_postgres_1 Recreating dockergitea_web_1 Attaching to dockergitea_data_1, dockergitea_pg_data_1, dockergitea_postgres_1, dockergitea_web_1 dockergitea_data_1 exited with code 0 web_1 | Mar 9 22:19:58 syslogd started: BusyBox v1.24.2 postgres_1 | LOG: database system was shut down at 2017-03-09 22:19:49 UTC dockergitea_pg_data_1 exited with code 0 web_1 | Mar 9 22:19:58 sshd[20]: Server listening on :: port 22. postgres_1 | LOG: MultiXact member wraparound protections are now enabled web_1 | Mar 9 22:19:58 sshd[20]: Server listening on 0.0.0.0 port 22. postgres_1 | LOG: autovacuum launcher started postgres_1 | LOG: database system is ready to accept connections web_1 | 2017/03/09 22:19:59 [T] Custom path: /data/gitea web_1 | 2017/03/09 22:19:59 [T] Log path: /app/gitea/log postgres_1 | ERROR: relation "IDX_repo_unit_S" already exists postgres_1 | STATEMENT: CREATE INDEX "IDX_repo_unit_S" ON "repo_unit" ("repo_id","type"); web_1 | 2017/03/09 22:20:00 [T] Custom path: /data/gitea web_1 | 2017/03/09 22:20:00 [T] Log path: /app/gitea/log postgres_1 | ERROR: relation "IDX_repo_unit_S" already exists postgres_1 | STATEMENT: CREATE INDEX "IDX_repo_unit_S" ON "repo_unit" ("repo_id","type"); ^CGracefully stopping... (press Ctrl+C again to force) Stopping dockergitea_web_1 ... done Stopping dockergitea_postgres_1 ... done avelino@avelino:~/docker-gitea$ cat docker-compose.yml web: image: gitea/gitea:1.1 ```
GiteaMirror commented 2025-11-02 03:23:49 -06:00
Author
Owner
Copy Link

@tboerger commented on GitHub (Mar 9, 2017):

@lunny any idea?

@tboerger commented on GitHub (Mar 9, 2017): @lunny any idea?
GiteaMirror commented 2025-11-02 03:23:49 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Mar 10, 2017):

If you have tested master, the migration has been executed once, when you turn it back and upgrade to 1.1 it will be executed twice, then the problem is occupied. Please drop the table repo_unit manually. and run it again it should be OK. @avelino

@lunny commented on GitHub (Mar 10, 2017): If you have tested master, the migration has been executed once, when you turn it back and upgrade to 1.1 it will be executed twice, then the problem is occupied. Please drop the table `repo_unit` manually. and run it again it should be OK. @avelino
GiteaMirror commented 2025-11-02 03:23:49 -06:00
Author
Owner
Copy Link

@avelino commented on GitHub (Mar 10, 2017):

Very very good, thanks.

Application Version: 1.1.0 built

@avelino commented on GitHub (Mar 10, 2017): Very very good, thanks. `Application Version: 1.1.0 built`
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label topic/deployment type/question
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#449
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?