ARM64 binary from dl.gitea.com missing Debian package backend (no backend initialization, routes 404) #36745
Description
Description
I’m running Gitea 1.25.4 on a Raspberry Pi 4 (ARM64) using the official binary from https://dl.gitea.com/gitea/1.25.4/gitea-1.25.4-linux-arm64. The binary is confirmed to be ARM64 (ELF 64-bit LSB executable, ARM aarch64, statically linked). Despite having the following configuration in /etc/gitea/app.ini:
Code
[packages]
ENABLED = true
[packages.debian]
ENABLED = true
the Debian package backend never initializes. There are no Debian-related log entries, no Debian routes in Swagger, and all Debian API endpoints return 404 (for example: PUT /api/packages//debian/enqueue). Startup logs show initialization for attachments, avatars, LFS, repo archives, and actions, but nothing for Debian packages. Running strings on the binary shows no Debian-related symbols, which suggests the Debian backend may not be compiled into the ARM64 release binary.
Environment:
- Raspberry Pi 4 (ARM64)
- Gitea 1.25.4
- Binary: gitea-1.25.4-linux-arm64
/usr/local/bin/gitea: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), statically linked, BuildID[sha1]=4b170766cb35d49383c0320e7b60df88c23bd4d0, for GNU/Linux 3.7.0, stripped
Gitea Version
gitea version 1.25.4 built with GNU Make 4.3, go1.25.6 : bindata, sqlite, sqlite_unlock_notify
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
https://gist.github.com/jamesBrosnahan/fff5ea1e701841254e23df0c8dc5b795
Screenshots
Git Version
git version 2.51.0
Operating System
Ubuntu 25.10
How are you running Gitea?
I’m running Gitea as a systemd-managed service on a Raspberry Pi 4 using the official ARM64 binary placed at /usr/local/bin/gitea. The service uses /etc/gitea/app.ini as its configuration file and /var/lib/gitea as its working directory, following the standard Linux installation layout. Gitea is started and supervised by systemd via gitea.service, and the logs I’ve provided come directly from journalctl -u gitea.
Database
SQLite