filter Alpine registry assets by brach/arch in web ui #13450

New Issue

GiteaMirror · 2025-11-02T10:42:45-06:00

GiteaMirror commented

2025-11-02 10:42:45 -06:00

Originally created by @nephatrine on GitHub (Sep 3, 2024).

Feature Description

I build Alpine APKs using standard APKBUILD files and the abuild tool. In Alpine. When uploading them into my Gitea package repository, it is impossible to determine which arch and/or branch the individual asset is for when manually downloading the APK files. Even hovering over the files doesn't show the Alpine-style path information, but just a generic path with a file identifier so the Assets list in gitea is pretty much useless. If adding the registry as an Alpine repo, of course, everything works great - this is only an issue if you wanted to download an APK manually through the web ui.

It would be nice to have some way to differentiate those Assets for manual downloaders. It's not a big deal or anything. It just looks real silly how it is right now when building for many architectures and Alpine versions.

Screenshots

Originally created by @nephatrine on GitHub (Sep 3, 2024). ### Feature Description I build Alpine APKs using standard APKBUILD files and the abuild tool. In Alpine. When uploading them into my Gitea package repository, it is impossible to determine which arch and/or branch the individual asset is for when manually downloading the APK files. Even hovering over the files doesn't show the Alpine-style path information, but just a generic path with a file identifier so the `Assets` list in gitea is pretty much useless. If adding the registry as an Alpine repo, of course, everything works great - this is only an issue if you wanted to download an APK manually through the web ui. It would be nice to have some way to differentiate those Assets for manual downloaders. It's not a big deal or anything. It just looks real silly how it is right now when building for many architectures and Alpine versions. ### Screenshots ![image](https://github.com/user-attachments/assets/82e9cfff-d92f-4be7-a69f-629a6fca0cd3)

GiteaMirror added the topic/packages type/proposal labels 2025-11-02 10:42:45 -06:00

GiteaMirror commented

2025-11-02 10:42:45 -06:00

@nephatrine commented on GitHub (Sep 12, 2024):

I have found that this is also the case for some of the other package registries. For instance if you upload .deb packages for Ubuntu Jammy and Debian Bookworm, the UI tells you both distributions are there, but there isn't a way to determine which is which when downloading via the web UI.

@nephatrine commented on GitHub (Sep 12, 2024): I have found that this is also the case for some of the other package registries. For instance if you upload .deb packages for Ubuntu Jammy and Debian Bookworm, the UI tells you both distributions are there, but there isn't a way to determine which is which when downloading via the web UI.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#13450