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

GPG-Keys don't get deleted when deleting an account #2544

New Issue
Closed
opened 2025-11-02 04:39:57 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-02 04:39:57 -06:00
Owner
Copy Link

Originally created by @je-s on GitHub (Nov 18, 2018).

  • Gitea version: 8733384
  • Git version: Not relevant
  • Operating system: Alpine Linux 3.7
  • Database:
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes
    • No
    • Not relevant

Description

When you delete a profile with an existing GPG-Key, you can't use this GPG-Key in a new account again. An error says "A public GPG key with same ID already exists.", and it can't be added.
Deleting a Key alone (not the whole account) and adding it again manually is no problem; My guess is that in the process of the account deletion, the GPG-Keys don't get deleted as well.

Screenshots

2018-11-18_223917

Originally created by @je-s on GitHub (Nov 18, 2018). - Gitea version: 8733384 - Git version: Not relevant - Operating system: Alpine Linux 3.7 - Database: - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] Yes - [ ] No - [ ] Not relevant ## Description When you delete a profile with an existing GPG-Key, you can't use this GPG-Key in a new account again. An error says "A public GPG key with same ID already exists.", and it can't be added. Deleting a Key alone (not the whole account) and adding it again manually is no problem; My guess is that in the process of the account deletion, the GPG-Keys don't get deleted as well. ## Screenshots ![2018-11-18_223917](https://user-images.githubusercontent.com/16293381/48678441-b71a5700-eb83-11e8-9c5d-e14e7d60ee4f.png)
GiteaMirror added the type/bug label 2025-11-02 04:39:57 -06:00
GiteaMirror commented 2025-11-02 04:39:58 -06:00
Author
Owner
Copy Link

@je-s commented on GitHub (Nov 18, 2018):

PR #5357 provided a quick fix for this problem.
We've already tested it successfully.

@je-s commented on GitHub (Nov 18, 2018): PR #5357 provided a quick fix for this problem. We've already tested it successfully.
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/bug
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#2544
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?