Repository stuck in unreadable state after rename timeout — cannot read, delete, or recreate #2620

skeptiker commented 2026年05月12日 22:52:19 +02:00

Comment

I attempted to rename my private repository https://codeberg.org/skeptiker/keel to https://codeberg.org/skeptiker/dusk. The operation returned a gateway timeout (504). After the timeout:

1. The original repository skeptiker/keel now shows: "The Git data underlying this repository cannot be read. Contact the administrator of this instance or delete this
   repository."
2. Attempting to delete skeptiker/keel also fails.
3. Creating a new repository named dusk fails with "name already used" — but no repository named dusk is visible in my account.
4. Prior to the rename attempt, I had also tried creating a new private repo named dusk, which also returned a gateway timeout.

It appears the rename partially committed — the name dusk is reserved in the database, but the underlying git data was not moved. Both the old and new names are now unusable.

What I need

• Remove the orphaned dusk repo record so the name is available again
• Either restore keel to a readable state or fully delete it so I can push fresh

No data loss concern — I have the full repository locally.

### Comment I attempted to rename my private repository https://codeberg.org/skeptiker/keel to https://codeberg.org/skeptiker/dusk. The operation returned a gateway timeout (504). After the timeout: 1. The original repository skeptiker/keel now shows: "The Git data underlying this repository cannot be read. Contact the administrator of this instance or delete this repository." 2. Attempting to delete skeptiker/keel also fails. 3. Creating a new repository named dusk fails with "name already used" — but no repository named dusk is visible in my account. 4. Prior to the rename attempt, I had also tried creating a new private repo named dusk, which also returned a gateway timeout. It appears the rename partially committed — the name dusk is reserved in the database, but the underlying git data was not moved. Both the old and new names are now unusable. What I need - Remove the orphaned dusk repo record so the name is available again - Either restore keel to a readable state or fully delete it so I can push fresh No data loss concern — I have the full repository locally.

ryanoatmeal commented 2026年05月13日 00:42:51 +02:00

I have experienced the same issue. This is also being tracked here: #2615

I have experienced the same issue. This is also being tracked here: https://codeberg.org/Codeberg/Community/issues/2615

skeptiker commented 2026年05月14日 21:09:46 +02:00

I managed to delete https://codeberg.org/skeptiker/keel but still cannot create https://codeberg.org/skeptiker/dusk.

I managed to delete https://codeberg.org/skeptiker/keel but still cannot create https://codeberg.org/skeptiker/dusk.

Gusted commented 2026年06月03日 01:57:31 +02:00

@skeptiker wrote in #2620 (comment):

Remove the orphaned dusk repo record so the name is available again

This is now done.

@skeptiker wrote in https://codeberg.org/Codeberg/Community/issues/2620#issue-5004528: > Remove the orphaned dusk repo record so the name is available again This is now done.

tuxick commented 2026年06月09日 13:09:48 +02:00

@Gusted wrote in #2620 (comment):

@skeptiker wrote in #2620 (comment):

Remove the orphaned dusk repo record so the name is available again

This is now done.

How? Where to find it?

@Gusted wrote in https://codeberg.org/Codeberg/Community/issues/2620#issuecomment-16413665: > @skeptiker wrote in #2620 (comment): > > > Remove the orphaned dusk repo record so the name is available again > > This is now done. How? Where to find it?