API Endpoint to link a package to a git repo #12883

New Issue

GiteaMirror · 2025-11-02T10:23:47-06:00

GiteaMirror commented

2025-11-02 10:23:47 -06:00

Originally created by @Infinoid on GitHub (Apr 19, 2024).

Originally assigned to: @puni9869 on GitHub.

Feature Description

It would be useful to have an API endpoint to assign a repo to a newly uploaded package.

Currently, whenever a package with a new name is uploaded, it is not associated with a git repo, and must be linked manually. There is an item in the Package Registry related ToDo list, "Set repository link from package metadata". This sounds great, but may not be possible in all cases.

I'd like an API endpoint to link a package to a git repo manually.

Use case: self-built kernel .deb packages. Debian packages for linux kernels include the version number in the name, so that users can decide for themselves when to delete an older kernel. But this means the name of the package varies and doesn't match the repo name, so automatic links may not be possible.

To illustrate this, say I have a linux machine named foo, and set up custom kernel builds for it. I would build and upload two packages:

linux-image-6.6.6-foo (version 6.6.6-1), a custom build of the 6.6.6 kernel for foo
linux-image-foo (version 6.6.6-1), an empty package which depends on linux-image-6.6.6-foo

This package naming convention matches the way distro packages work.

I'd configure foo to use gitea as an apt repo, and I'd apt install linux-image-foo to install the custom kernel. So far so good.

Then later on, I build a newer kernel version:

linux-image-6.6.7-foo (version 6.6.7-1), a custom build of the 6.6.7 kernel for foo
linux-image-foo (version 6.6.7-1), an empty package which depends on linux-image-6.6.7-foo

The new linux-image-foo package updates the previous one, but linux-image-6.6.7-foo appears in the gitea UI as a new package and is not linked to the gitea repo.

I do not believe it would be possible to automatically link packages in this case. So I would like a way for buildbots to set the link directly. Does an endpoint already exist to do this? I wasn't able to find one... but I suspect some endpoints may be missing from the swagger docs (see #30597).

This is largely cosmetic; the apt repo works fine, the only problem is navigation in the gitea UI.

Screenshots

No response

Originally created by @Infinoid on GitHub (Apr 19, 2024). Originally assigned to: @puni9869 on GitHub. ### Feature Description It would be useful to have an API endpoint to assign a repo to a newly uploaded package. Currently, whenever a package with a new name is uploaded, it is not associated with a git repo, and must be linked manually. There is an item in the [Package Registry related ToDo list](https://github.com/go-gitea/gitea/issues/19270), "Set repository link from package metadata". This sounds great, but may not be possible in all cases. I'd like an API endpoint to link a package to a git repo manually. Use case: self-built kernel .deb packages. Debian packages for linux kernels include the version number in the name, so that users can decide for themselves when to delete an older kernel. But this means the name of the package varies and doesn't match the repo name, so automatic links may not be possible. To illustrate this, say I have a linux machine named `foo`, and set up custom kernel builds for it. I would build and upload two packages: * linux-image-6.6.6-foo (version 6.6.6-1), a custom build of the 6.6.6 kernel for foo * linux-image-foo (version 6.6.6-1), an empty package which depends on linux-image-6.6.6-foo This package naming convention matches the way [distro](https://packages.debian.org/search?keywords=linux-image) [packages](https://packages.ubuntu.com/search?keywords=linux-image) work. I'd configure foo to use gitea as an apt repo, and I'd `apt install linux-image-foo` to install the custom kernel. So far so good. Then later on, I build a newer kernel version: * linux-image-6.6.7-foo (version 6.6.7-1), a custom build of the 6.6.7 kernel for foo * linux-image-foo (version 6.6.7-1), an empty package which depends on linux-image-6.6.7-foo The new linux-image-foo package updates the previous one, but linux-image-6.6.7-foo appears in the gitea UI as a new package and is not linked to the gitea repo. I do not believe it would be possible to automatically link packages in this case. So I would like a way for buildbots to set the link directly. Does an endpoint already exist to do this? I wasn't able to find one... but I suspect some endpoints may be missing from the swagger docs (see #30597). This is largely cosmetic; the apt repo works fine, the only problem is navigation in the gitea UI. ### Screenshots _No response_

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

GiteaMirror closed this issue

2025-11-02 10:23:47 -06:00

GiteaMirror commented

2025-11-02 10:23:48 -06:00

@vjm commented on GitHub (Jun 22, 2024):

Hi -- is there any news on this? I would also like to leverage this feature for automation in CI pipeline.

@vjm commented on GitHub (Jun 22, 2024): Hi -- is there any news on this? I would also like to leverage this feature for automation in CI pipeline.

GiteaMirror commented

2025-11-02 10:23:48 -06:00

@KoltesDigital commented on GitHub (Sep 17, 2024):

Duplicate of #21062.

@KoltesDigital commented on GitHub (Sep 17, 2024): Duplicate of #21062.

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#12883