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

gitea-1.21.2 is not compatible with Windows 7 #12591

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

Originally created by @znsoooo on GitHub (Mar 4, 2024).

Description

After testing in all patch versions between v1.20.0 and v1.21.7 (including both gogit and non-gogit versions), I found that all versions<=v1.21.1 are running normally on Windows 7, and all versions>=v1.21.2 are crashed on Windows 7. (there even isn't any logs print out)

Run program in CMD:
The highest supported version of Gitea for Windows 7 is v1.21.1

As we all know Windows 7 is no longer supported by Microsoft, but the compatibility bug occurred only between the patch version v1.21.1 and v1.21.2. So I suspected that a minor change might have caused this compatibility issue.

If possible, it is hoped that this issue can be solved in future releases.

Gitea Version

1.21.2

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

2.34.0.windows.1

Operating System

windows 7

How are you running Gitea?

Download Windows EXE file from: https://dl.gitea.com/gitea/

Database

None

Originally created by @znsoooo on GitHub (Mar 4, 2024). ### Description After testing in all patch versions between v1.20.0 and v1.21.7 (including both gogit and non-gogit versions), I found that all versions<=v1.21.1 are running normally on Windows 7, and all versions>=v1.21.2 are crashed on Windows 7. (there even isn't any logs print out) Run program in CMD: ![The highest supported version of Gitea for Windows 7 is v1.21.1](https://github.com/go-gitea/gitea/assets/34830785/2d0cdd89-1725-448b-a538-d5d8d2b01522) As we all know Windows 7 is no longer supported by Microsoft, but the compatibility bug occurred only between the patch version v1.21.1 and v1.21.2. So I suspected that a minor change might have caused this compatibility issue. If possible, it is hoped that this issue can be solved in future releases. ### Gitea Version 1.21.2 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version 2.34.0.windows.1 ### Operating System windows 7 ### How are you running Gitea? Download Windows EXE file from: https://dl.gitea.com/gitea/ ### Database None
GiteaMirror added the issue/needs-feedback label 2025-11-02 10:15:28 -06:00
GiteaMirror commented 2025-11-02 10:15:29 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Mar 4, 2024):

Because Gitea 1.21 was built by Golang 1.21 which have dropped support for windows 7. https://tip.golang.org/doc/go1.21#windows

@lunny commented on GitHub (Mar 4, 2024): Because Gitea 1.21 was built by Golang 1.21 which have dropped support for windows 7. https://tip.golang.org/doc/go1.21#windows
GiteaMirror commented 2025-11-02 10:15:29 -06:00
Author
Owner
Copy Link

@algora-pbc[bot] commented on GitHub (Mar 4, 2024):

@algora-pbc[bot] commented on GitHub (Mar 4, 2024): [![](https://console.algora.io/api/og/tip.png?amount=2000)](https://console.algora.io/api/org/go-gitea/tip?solver_id=34830785&task_id=cltcz9gqp0000jv0ficxq2f3v&org=go-gitea&amount=2000&currency=USD&url=https%3A%2F%2Fgithub.com%2Fgo-gitea%2Fgitea%2Fissues%2F29586) [![](https://console.algora.io/api/og/tip.png?amount=5000)](https://console.algora.io/api/org/go-gitea/tip?solver_id=34830785&task_id=cltcz9gqp0000jv0ficxq2f3v&org=go-gitea&amount=5000&currency=USD&url=https%3A%2F%2Fgithub.com%2Fgo-gitea%2Fgitea%2Fissues%2F29586) [![](https://console.algora.io/api/og/tip.png?amount=10000)](https://console.algora.io/api/org/go-gitea/tip?solver_id=34830785&task_id=cltcz9gqp0000jv0ficxq2f3v&org=go-gitea&amount=10000&currency=USD&url=https%3A%2F%2Fgithub.com%2Fgo-gitea%2Fgitea%2Fissues%2F29586) [![](https://console.algora.io/api/og/tip.png)](#new_comment_field)
GiteaMirror commented 2025-11-02 10:15:30 -06:00
Author
Owner
Copy Link

@znsoooo commented on GitHub (Mar 4, 2024):

Because Gitea 1.21 was built by Golang 1.21 which have dropped support for windows 7. https://tip.golang.org/doc/go1.21#windows

@lunny But why v1.21 and v1.21.0 and v1.21.1 can work well?

@znsoooo commented on GitHub (Mar 4, 2024): > Because Gitea 1.21 was built by Golang 1.21 which have dropped support for windows 7. https://tip.golang.org/doc/go1.21#windows @lunny But why v1.21 and v1.21.0 and v1.21.1 can work well?
GiteaMirror commented 2025-11-02 10:15:30 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Mar 4, 2024):

Because Gitea 1.21 was built by Golang 1.21 which have dropped support for windows 7. https://tip.golang.org/doc/go1.21#windows

@lunny But why v1.21 and v1.21.0 and v1.21.1 can work well?

It's wired. Maybe it's related to Golang's minor version? I have no idea.

@lunny commented on GitHub (Mar 4, 2024): > > Because Gitea 1.21 was built by Golang 1.21 which have dropped support for windows 7. https://tip.golang.org/doc/go1.21#windows > > @lunny But why v1.21 and v1.21.0 and v1.21.1 can work well? It's wired. Maybe it's related to Golang's minor version? I have no idea.
GiteaMirror commented 2025-11-02 10:15:30 -06:00
Author
Owner
Copy Link

@KN4CK3R commented on GitHub (Mar 4, 2024):

Can confirm but I get an error message:

> gitea-1.21.7-windows-4.0-386.exe
Exception 0xc0000005 0x8 0x0 0x0
PC=0x0

runtime.asmstdcall()
        /usr/local/go/src/runtime/sys_windows_386.s:35 +0x25 fp=0x22fdb8 sp=0x22fdb4 pc=0x4780f5

And that's expected behaviour https://github.com/golang/go/issues/64602

The fact that your program built with 1.21.4 was running without problems may have been luck.

Should be the same in our case.

@KN4CK3R commented on GitHub (Mar 4, 2024): Can confirm but I get an error message: ``` > gitea-1.21.7-windows-4.0-386.exe Exception 0xc0000005 0x8 0x0 0x0 PC=0x0 runtime.asmstdcall() /usr/local/go/src/runtime/sys_windows_386.s:35 +0x25 fp=0x22fdb8 sp=0x22fdb4 pc=0x4780f5 ``` And that's expected behaviour https://github.com/golang/go/issues/64602 > The fact that your program built with 1.21.4 was running without problems may have been luck. Should be the same in our case.
GiteaMirror commented 2025-11-02 10:15:30 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Mar 4, 2024):

Hi @znsoooo, sorry for the comment from algora above. There was a bug where it detected a trigger word from the golang URL posted. If you wish I can also refund the tip you provided.

Sadly, the project itself is unable to support older versions of Golang as Gitea does use features from newer versions of golang. So this error is expected as it is related to Golang's supported OSes. However, if you are interested in an extended support release that is built with a lower version of Golang please reach out to me and I can help you with that.

I will now close this issue.

@techknowlogick commented on GitHub (Mar 4, 2024): Hi @znsoooo, sorry for the comment from algora above. There was a bug where it detected a trigger word from the golang URL posted. If you wish I can also refund the tip you provided. Sadly, the project itself is unable to support older versions of Golang as Gitea does use features from newer versions of golang. So this error is expected as it is related to Golang's supported OSes. However, if you are interested in an extended support release that is built with a lower version of Golang please reach out to me and I can help you with that. I will now close this issue.
GiteaMirror commented 2025-11-02 10:15:31 -06:00
Author
Owner
Copy Link

@znsoooo commented on GitHub (Mar 4, 2024):

@KN4CK3R @techknowlogick Thank you for your answers!

@znsoooo commented on GitHub (Mar 4, 2024): @KN4CK3R @techknowlogick Thank you for your answers!
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#12591
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?