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

Gitea doesn't find avatar after every server update #2569

New Issue
Closed
opened 2025-11-02 04:40:45 -06:00 by GiteaMirror · 6 comments
GiteaMirror commented 2025-11-02 04:40:45 -06:00
Owner
Copy Link

Originally created by @theAkito on GitHub (Nov 25, 2018).

  • Gitea version (or commit ref): 1.6.0+rc1-123-g3379141d8
  • Git version: git version 2.11.0
  • Operating system:
PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
NAME="Raspbian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=raspbian
ID_LIKE=debian
  • 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:

Description

Every time I update Gitea to the newest version, I have to upload my avatar to my profile again, because it is empty (i.e. shows Gitea logo) like I never had one in the first place.

P.S.: I'm not sure if this is realted to #4629, because my avatars folder is on a different HDD than Gitea is installed on.

Originally created by @theAkito on GitHub (Nov 25, 2018). <!-- 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 Discord server (https://discord.gg/NsatcWJ) 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.6.0+rc1-123-g3379141d8 - Git version: git version 2.11.0 - Operating system: ``` PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)" NAME="Raspbian GNU/Linux" VERSION_ID="9" VERSION="9 (stretch)" ID=raspbian ID_LIKE=debian ``` - Database (use `[x]`): - [x] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [x] No - [ ] Not relevant - Log gist: ## Description Every time I update Gitea to the newest version, I have to upload my avatar to my profile again, because it is empty (i.e. shows Gitea logo) like I never had one in the first place. P.S.: I'm not sure if this is realted to #4629, because my `avatars` folder is on a different HDD than Gitea is installed on.
GiteaMirror added the issue/stale label 2025-11-02 04:40:45 -06:00
GiteaMirror commented 2025-11-02 04:40:46 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Nov 26, 2018):

Did you install Gitea via docker?

@lunny commented on GitHub (Nov 26, 2018): Did you install Gitea via docker?
GiteaMirror commented 2025-11-02 04:40:46 -06:00
Author
Owner
Copy Link

@theAkito commented on GitHub (Nov 26, 2018):

Did you install Gitea via docker?

No.

@theAkito commented on GitHub (Nov 26, 2018): > > > Did you install Gitea via docker? No.
GiteaMirror commented 2025-11-02 04:40:46 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Nov 26, 2018):

Maybe you should ln the link again?

@lunny commented on GitHub (Nov 26, 2018): Maybe you should `ln` the link again?
GiteaMirror commented 2025-11-02 04:40:46 -06:00
Author
Owner
Copy Link

@Hyask commented on GitHub (Nov 29, 2018):

I've experienced the same issue after a Gogs migration, then upgrade to 1.6.0...
The avatars are still present in the data/avatars folder, but we can't have them in the web UI, nor in the API.

If you need more information, I'll be happy to help.

@Hyask commented on GitHub (Nov 29, 2018): I've experienced the same issue after a Gogs migration, then upgrade to 1.6.0... The avatars are still present in the `data/avatars` folder, but we can't have them in the web UI, nor in the API. If you need more information, I'll be happy to help.
GiteaMirror commented 2025-11-02 04:40:47 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Jan 28, 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 (Jan 28, 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 04:40:47 -06:00
Author
Owner
Copy Link

@theAkito commented on GitHub (Jan 28, 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.

For me the issue was fixed with a newer update. Therefore closing.

@theAkito commented on GitHub (Jan 28, 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. For me the issue was fixed with a newer update. Therefore closing.
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#2569
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?