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

Upgrade from windows 386 to amd64 #1898

New Issue
Closed
opened 2025-11-02 04:17:12 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-02 04:17:12 -06:00
Owner
Copy Link

Originally created by @T100D on GitHub (Jun 8, 2018).

  • Gitea version (or commit ref): 1.4.2
  • Git version: 2.17.1.windows.2
  • Operating system: Windows 10
  • Database:
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes

Description

Wen we replace the gitea-1.4.2-windows-4.0-386.exe file with the gitea-1.4.2-windows-4.0-amd64.exe file to from 32bit to 64 bit, the repository is empty and a new administration account is deployed.

The old data is not present anymore.

When we go back to the 32bit version of gitea, the repository and accounts are back again.

Is ther a way to upgrade to the 64 bit version without losing data?

Originally created by @T100D on GitHub (Jun 8, 2018). - Gitea version (or commit ref): 1.4.2 - Git version: 2.17.1.windows.2 - Operating system: Windows 10 - Database: - [X] SQLite - Can you reproduce the bug at https://try.gitea.io: - [X] Yes ## Description Wen we replace the gitea-1.4.2-windows-4.0-386.exe file with the gitea-1.4.2-windows-4.0-amd64.exe file to from 32bit to 64 bit, the repository is empty and a new administration account is deployed. The old data is not present anymore. When we go back to the 32bit version of gitea, the repository and accounts are back again. Is ther a way to upgrade to the 64 bit version without losing data?
GiteaMirror added the type/question label 2025-11-02 04:17:12 -06:00
GiteaMirror commented 2025-11-02 04:17:13 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Jun 8, 2018):

check that your data is not saved in system32 folder (32-bit vs 64-bit will have different (System32 vs SysWOW64). You need to reconfigure gitea to use other folders not system ones.

@lafriks commented on GitHub (Jun 8, 2018): check that your data is not saved in system32 folder (32-bit vs 64-bit will have different (System32 vs SysWOW64). You need to reconfigure gitea to use other folders not system ones.
GiteaMirror commented 2025-11-02 04:17:13 -06:00
Author
Owner
Copy Link

@T100D commented on GitHub (Jun 8, 2018):

Thank you @lafriks.
Thit solved the problem. Now the db is in c:\gitea\data, and we changed this in the config file.

@T100D commented on GitHub (Jun 8, 2018): Thank you @lafriks. Thit solved the problem. Now the db is in c:\gitea\data\, and we changed this in the config file.
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 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#1898
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?