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

Backups don't run because of incorrect user #3434

New Issue
Closed
opened 2025-11-02 05:12:52 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-02 05:12:52 -06:00
Owner
Copy Link

Originally created by @dunestorm333 on GitHub (Jun 5, 2019).

  • Gitea version (or commit ref): 1.9.0+dev-325-g59e6a7b97
  • Git version: 2.20.1
  • Operating system: Linux
  • 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:
    ./app/gitea/gitea dump -f /data/backups/import.zip
    2019/06/05 21:03:39 ...s/setting/setting.go:828:NewContext() [F] Expect user 'git' but current user is: root

Description

Despite my username being "git" matching the one in app.ini, gitea dump misidentifies my user as being root:

bash-4.4# echo $USERNAME
git
bash-4.4# echo $USER
git

...

Screenshots

Originally created by @dunestorm333 on GitHub (Jun 5, 2019). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to 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. --> - Gitea version (or commit ref): 1.9.0+dev-325-g59e6a7b97 - Git version: 2.20.1 - Operating system: Linux - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: ./app/gitea/gitea dump -f /data/backups/import.zip 2019/06/05 21:03:39 ...s/setting/setting.go:828:NewContext() [F] Expect user 'git' but current user is: root ## Description Despite my username being "git" matching the one in app.ini, gitea dump misidentifies my user as being root: bash-4.4# echo $USERNAME git bash-4.4# echo $USER git ... ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror added the issue/stale label 2025-11-02 05:12:52 -06:00
GiteaMirror commented 2025-11-02 05:12:53 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Jun 6, 2019):

How are you running your backups? Is it via crontab?

@techknowlogick commented on GitHub (Jun 6, 2019): How are you running your backups? Is it via crontab?
GiteaMirror commented 2025-11-02 05:12:53 -06:00
Author
Owner
Copy Link

@dunestorm333 commented on GitHub (Jun 6, 2019):

@techknowlogick I'm running the backups manually, I haven't tried through crontab yet though it is running inside of a Docker container.

@dunestorm333 commented on GitHub (Jun 6, 2019): @techknowlogick I'm running the backups manually, I haven't tried through crontab yet though it is running inside of a Docker container.
GiteaMirror commented 2025-11-02 05:12:53 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Aug 5, 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 (Aug 5, 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:12:53 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Aug 19, 2019):

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

@stale[bot] commented on GitHub (Aug 19, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.
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/stale
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#3434
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?