github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

downgrade database version from 280" to'189" is not supported and may result in loss of data integrity. #12856

New Issue
Closed
opened 2025-11-02 10:23:05 -06:00 by GiteaMirror · 7 comments
GiteaMirror commented 2025-11-02 10:23:05 -06:00
Owner
Copy Link

Originally created by @x2358473 on GitHub (Apr 16, 2024).

Description

我使用的mysql数据库。今天从1.21.10更新到1.21.11后运行就报错了

Gitea Version

1.21.11

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

1.21.10

Operating System

linux

How are you running Gitea?

docker

Database

MySQL/MariaDB

Originally created by @x2358473 on GitHub (Apr 16, 2024). ### Description 我使用的mysql数据库。今天从1.21.10更新到1.21.11后运行就报错了 ### Gitea Version 1.21.11 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version 1.21.10 ### Operating System linux ### How are you running Gitea? docker ### Database MySQL/MariaDB
GiteaMirror added the issue/needs-feedback label 2025-11-02 10:23:06 -06:00
GiteaMirror commented 2025-11-02 10:23:07 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Apr 16, 2024):

I think you upgraded to a wrong version. 189 is a previous version which should be 1.14.x . For minor versions, there will be no database version changes.

@lunny commented on GitHub (Apr 16, 2024): I think you upgraded to a wrong version. 189 is a previous version which should be 1.14.x . For minor versions, there will be no database version changes.
GiteaMirror commented 2025-11-02 10:23:07 -06:00
Author
Owner
Copy Link

@x2358473 commented on GitHub (Apr 16, 2024):

我认为您升级到了错误的版本。 189 是以前的版本，应该是 1.14.x 。对于次要版本，不会有数据库版本更改。

我是使用的docker版本，从hub.docker上拉取的latest版本。然后把docker中的/data映射到本地目录。之前的升级都正常。但是这次的升级出现了问题

@x2358473 commented on GitHub (Apr 16, 2024): > 我认为您升级到了错误的版本。 189 是以前的版本，应该是 1.14.x 。对于次要版本，不会有数据库版本更改。 我是使用的docker版本，从hub.docker上拉取的latest版本。然后把docker中的/data映射到本地目录。之前的升级都正常。但是这次的升级出现了问题
GiteaMirror commented 2025-11-02 10:23:07 -06:00
Author
Owner
Copy Link

@x2358473 commented on GitHub (Apr 16, 2024):

我认为您升级到了错误的版本。 189 是以前的版本，应该是 1.14.x 。对于次要版本，不会有数据库版本更改。

WechatIMG1481
Uploading WechatIMG1482.jpg…
[https://zx-wechat.oss-cn-hangzhou.aliyuncs.com/admin_img/WechatIMG1482.jpg](url)
图片上传失败。可以看url

@x2358473 commented on GitHub (Apr 16, 2024): > 我认为您升级到了错误的版本。 189 是以前的版本，应该是 1.14.x 。对于次要版本，不会有数据库版本更改。 ![WechatIMG1481](https://github.com/go-gitea/gitea/assets/26506220/76fa332e-c7df-460a-a1e2-b82ce79e0856) ![Uploading WechatIMG1482.jpg…]() [[https://zx-wechat.oss-cn-hangzhou.aliyuncs.com/admin_img/WechatIMG1482.jpg](https://github.com/go-gitea/gitea/issues/url)](url) 图片上传失败。可以看url
GiteaMirror commented 2025-11-02 10:23:07 -06:00
Author
Owner
Copy Link

@x2358473 commented on GitHub (Apr 16, 2024):

https://zx-wechat.oss-cn-hangzhou.aliyuncs.com/admin_img/WechatIMG1482.jpg

@x2358473 commented on GitHub (Apr 16, 2024): [https://zx-wechat.oss-cn-hangzhou.aliyuncs.com/admin_img/WechatIMG1482.jpg](url)
GiteaMirror commented 2025-11-02 10:23:07 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Apr 16, 2024):

You are running wrong docker. It's OK for me.
image

@lunny commented on GitHub (Apr 16, 2024): You are running wrong docker. It's OK for me. <img width="1504" alt="image" src="https://github.com/go-gitea/gitea/assets/81045/fb8c2dac-9dd5-48f1-8811-e8cd3e821c23">
GiteaMirror commented 2025-11-02 10:23:08 -06:00
Author
Owner
Copy Link

@x2358473 commented on GitHub (Apr 16, 2024):

你运行了错误的docker。对我来说还好。 图像

dockerHub上拉取的latest居然是1.16的版本。是dockerHub的问题吗。

@x2358473 commented on GitHub (Apr 16, 2024): > 你运行了错误的docker。对我来说还好。 <img alt="图像" width="1504" src="https://private-user-images.githubusercontent.com/81045/322761797-fb8c2dac-9dd5-48f1-8811-e8cd3e821c23.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTMyNTYyOTcsIm5iZiI6MTcxMzI1NTk5NywicGF0aCI6Ii84MTA0NS8zMjI3NjE3OTctZmI4YzJkYWMtOWRkNS00OGYxLTg4MTEtZThjZDNlODIxYzIzLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA0MTYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNDE2VDA4MjYzN1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTNjNTZlZTI2Y2IyNjhkNjM1OWNiODQzNWY0ODVlYTNhOWJhZDEzOGVhYWYxNzVjYmUwMDhmOTQxNDY5ZmFlYTEmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.DW0AEl9SPy4pa6t2Xkh9jRg3hvZsuMjN_d6raCghdDA"> dockerHub上拉取的latest居然是1.16的版本。是dockerHub的问题吗。
GiteaMirror commented 2025-11-02 10:23:08 -06:00
Author
Owner
Copy Link

@x2358473 commented on GitHub (Apr 16, 2024):

你运行了错误的docker。对我来说还好。 图像

我可能知道原因了。我使用了registry-mirrors 到aliyuncs,可能他的latest没有同步。所以是旧的

@x2358473 commented on GitHub (Apr 16, 2024): > 你运行了错误的docker。对我来说还好。 <img alt="图像" width="1504" src="https://private-user-images.githubusercontent.com/81045/322761797-fb8c2dac-9dd5-48f1-8811-e8cd3e821c23.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTMyNTgxMTIsIm5iZiI6MTcxMzI1NzgxMiwicGF0aCI6Ii84MTA0NS8zMjI3NjE3OTctZmI4YzJkYWMtOWRkNS00OGYxLTg4MTEtZThjZDNlODIxYzIzLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA0MTYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNDE2VDA4NTY1MlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWFjNTQ2NjYxY2ViZWRkNTFiMzljYWIxMTBkYzIyMzM4MGRkYmZhOTVmMzQzZmQ4MTU3ZjRmMGU2ZmM3MGVlMWUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.IxnUFCKrc6NODy3EYez-q7CYIIgSPCEye-6uqPpiRmo"> 我可能知道原因了。我使用了registry-mirrors 到aliyuncs,可能他的latest没有同步。所以是旧的
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 issue/needs-feedback
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#12856
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?