Codeberg/Community
62
385
Fork
You've already forked Community
12

Arch-Repo DB broken after specific Package was uploaded via API but works on local Forgejo Instance #2647

Open
opened 2026年05月16日 18:49:00 +02:00 by Awalon · 2 comments

Comment

What happend:
Error message raised by pacman after having package added to Org, error was fixed after package was removed. Both using codeberg.org AP-calls.
This works on my own private Forgejo (v15) instance, where at least size of DB file went from about 2.7 KiB to 39.7 KiB after package was added. On codeberg.org the DB stays at 9.7 KiB (without package 2.7 KiB) after package was added.

Steps:

  1. build Arch package for icon theme sours-full-color-icon-theme-git (package contains bigger number of files) using git clone + mkpkg
  2. Upload new package (file size 2.5 MiB) with curl:
    curl -X PUT \
     https://codeberg.org/api/packages/GWC-AUR/arch/aur \
     --user git@awalon.de \
     --header "Content-Type: application/octet-stream" \
     --data-binary '@sours-full-color-icon-theme-git-2025年10月27日.a7027ca-1-any.pkg.tar.zst'
    
  3. Installation viaLC_ALL=en sudo pacman -Sy sours-full-color-icon-theme-git (same for other package) fails with (looks like broken DB file):
    error: could not parse package description file 'sours-full-color-icon-theme-git-2025年10月27日.a7027ca-1/files' from db 'gwc-aur.codeberg.org'
    error: failed to prepare transaction (invalid or corrupted database)
    
  4. Error can be fixed by removing package again:
    curl -X DELETE \
     https://codeberg.org/api/packages/GWC-AUR/arch/aur/sours-full-color-icon-theme-git/2025.10.27.a7027ca-1/any \
     --user git@awalon.de
    

Arch package is currently available in a brocken repo (different group):
https://codeberg.org/api/packages/GWC-AUR/arch/gwc/$arch

Expecation:
Option 1: If this package reached a ressource limit there should be an error message for upload API (like for invalid authorization)
Option 2: Arch repo DB file can be successfully processed by pacman

Btw. thank you very much for your efforts and this great service.

### Comment **What happend:** Error message raised by pacman after having package added to Org, error was fixed after package was removed. Both using codeberg.org AP-calls. This works on my own private Forgejo (v15) instance, where at least size of DB file went from about 2.7 KiB to **39.7 KiB** after package was added. On codeberg.org the DB stays at **9.7 KiB** (without package 2.7 KiB) after package was added. **Steps:** 1. build Arch package for icon theme [sours-full-color-icon-theme-git](https://codeberg.org/GWC-AUR/sours-full-color-icon-theme-git) (package contains bigger number of files) using git clone + mkpkg 2. Upload new package (file size 2.5 MiB) with curl: ```sh curl -X PUT \ https://codeberg.org/api/packages/GWC-AUR/arch/aur \ --user git@awalon.de \ --header "Content-Type: application/octet-stream" \ --data-binary '@sours-full-color-icon-theme-git-2025年10月27日.a7027ca-1-any.pkg.tar.zst' ``` 3. Installation via`LC_ALL=en sudo pacman -Sy sours-full-color-icon-theme-git` (same for other package) fails with (looks like broken DB file): ```text error: could not parse package description file 'sours-full-color-icon-theme-git-2025年10月27日.a7027ca-1/files' from db 'gwc-aur.codeberg.org' error: failed to prepare transaction (invalid or corrupted database) ``` 4. Error can be fixed by removing package again: ```sh curl -X DELETE \ https://codeberg.org/api/packages/GWC-AUR/arch/aur/sours-full-color-icon-theme-git/2025.10.27.a7027ca-1/any \ --user git@awalon.de ``` Arch package is currently available in a brocken repo (different group): [https://codeberg.org/api/packages/GWC-AUR/arch/gwc/$arch](https://codeberg.org/GWC-AUR/-/packages/arch/sours-full-color-icon-theme-git/2025.10.27.a7027ca-1) **Expecation:** Option 1: If this package reached a ressource limit there should be an error message for upload API (like for invalid authorization) Option 2: Arch repo DB file can be successfully processed by pacman Btw. thank you very much for your efforts and this great service.

Could you try to do this again, you might've been hit by Codeberg/Community#2596

Could you try to do this again, you might've been hit by Codeberg/Community#2596
Author
Copy link

Maybe (if there's an async process on server side, after upload, and error occurres after API response was sent) but already tried multiple times at different days, as there was another reported issue (but already fixed) related to "any" arch and my first ideas was that this could be related to version string and/or file name.
try 2026年05月18日 15:55:46 (CEST)
try 2026年05月18日 16:02:58 (CEST)

At least there's no 500- status for this call (from curl using --verbose parameter):

* upload completely sent off: 2623576 bytes
< HTTP/2 201
< content-length: 0

(cannot see any relevant difference comaprring curl output with my working local instance)

Maybe (if there's an async process on server side, after upload, and error occurres after API response was sent) but already tried multiple times at different days, as there was another [reported issue](https://codeberg.org/forgejo/forgejo/issues/5605) (but already fixed) related to "any" arch and my first ideas was that this could be related to version string and/or file name. ❌ try 2026年05月18日 15:55:46 (CEST) ❌ try 2026年05月18日 16:02:58 (CEST) At least there's no 500- status for this call (from curl using --verbose parameter): ``` * upload completely sent off: 2623576 bytes < HTTP/2 201 < content-length: 0 ``` (cannot see any relevant difference comaprring curl output with my working local instance)
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility
Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug
Something is not working the way it should. Does not concern outages.
bug
infrastructure
Errors evidently caused by infrastructure malfunctions or outages
Codeberg
This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome
Please join the discussion and consider contributing a PR!
docs
No bug, but an improvement to the docs or UI description will help
duplicate
This issue or pull request already exists
enhancement
New feature
infrastructure
Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal
An issue directly involving legal compliance
licence / ToS
involving questions about the ToS, especially licencing compliance
please chill
we are volunteers
Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations
Things related to Codeberg's external communication
question
More information is needed
question
user support
This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo
Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration
Migration related issues in Forgejo
s/Pages
Issues related to the Codeberg Pages feature
s/Weblate
Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker
Woodpecker CI related issue
security
involves improvements to the sites security
service
Add a new service to the Codeberg ecosystem (instead of implementing into Forgejo)
upstream
An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Forgejo, Weblate, etc.)
wontfix
Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#2647
Reference in a new issue
Codeberg/Community
No description provided.
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?