mirror of
https://codeberg.org/forgejo/forgejo
synced 2024-11-30 05:46:09 +01:00
ba4d0b8ffb
The current rpm repository places all packages in the same repository, and different systems (el7,f34) may hit packages that do not belong to this distribution ( #25304 ) , which now supports grouping of rpm.  Fixes #25304 . Fixes #27056 . Refactor: [#25866](https://github.com/go-gitea/gitea/pull/25866)
118 lines
3.8 KiB
Markdown
118 lines
3.8 KiB
Markdown
---
|
|
date: "2023-03-08T00:00:00+00:00"
|
|
title: "RPM Package Registry"
|
|
slug: "rpm"
|
|
draft: false
|
|
toc: false
|
|
menu:
|
|
sidebar:
|
|
parent: "packages"
|
|
name: "RPM"
|
|
sidebar_position: 105
|
|
identifier: "rpm"
|
|
---
|
|
|
|
# RPM Package Registry
|
|
|
|
Publish [RPM](https://rpm.org/) packages for your user or organization.
|
|
|
|
## Requirements
|
|
|
|
To work with the RPM registry, you need to use a package manager like `yum`, `dnf` or `zypper` to consume packages.
|
|
|
|
The following examples use `dnf`.
|
|
|
|
## Configuring the package registry
|
|
|
|
To register the RPM registry add the url to the list of known apt sources:
|
|
|
|
```shell
|
|
dnf config-manager --add-repo https://gitea.example.com/api/packages/{owner}/rpm/{group}.repo
|
|
```
|
|
|
|
| Placeholder | Description |
|
|
| ----------- |----------------------------------------------------|
|
|
| `owner` | The owner of the package. |
|
|
| `group` | Everything, e.g. `el7`, `rocky/el9` , `test/fc38`.|
|
|
|
|
If the registry is private, provide credentials in the url. You can use a password or a [personal access token](development/api-usage.md#authentication):
|
|
|
|
```shell
|
|
dnf config-manager --add-repo https://{username}:{your_password_or_token}@gitea.example.com/api/packages/{owner}/rpm/{group}.repo
|
|
```
|
|
|
|
You have to add the credentials to the urls in the `rpm.repo` file in `/etc/yum.repos.d` too.
|
|
|
|
## Publish a package
|
|
|
|
To publish a RPM package (`*.rpm`), perform a HTTP PUT operation with the package content in the request body.
|
|
|
|
```
|
|
PUT https://gitea.example.com/api/packages/{owner}/rpm/{group}/upload
|
|
```
|
|
|
|
| Parameter | Description |
|
|
| --------- | ----------- |
|
|
| `owner` | The owner of the package. |
|
|
| `group` | Everything, e.g. `el7`, `rocky/el9` , `test/fc38`.|
|
|
|
|
Example request using HTTP Basic authentication:
|
|
|
|
```shell
|
|
curl --user your_username:your_password_or_token \
|
|
--upload-file path/to/file.rpm \
|
|
https://gitea.example.com/api/packages/testuser/rpm/centos/el7/upload
|
|
```
|
|
|
|
If you are using 2FA or OAuth use a [personal access token](development/api-usage.md#authentication) instead of the password.
|
|
You cannot publish a file with the same name twice to a package. You must delete the existing package version first.
|
|
|
|
The server responds with the following HTTP Status codes.
|
|
|
|
| HTTP Status Code | Meaning |
|
|
| ----------------- | ------- |
|
|
| `201 Created` | The package has been published. |
|
|
| `400 Bad Request` | The package is invalid. |
|
|
| `409 Conflict` | A package file with the same combination of parameters exist already in the package. |
|
|
|
|
## Delete a package
|
|
|
|
To delete an RPM package perform a HTTP DELETE operation. This will delete the package version too if there is no file left.
|
|
|
|
```
|
|
DELETE https://gitea.example.com/api/packages/{owner}/rpm/{group}/package/{package_name}/{package_version}/{architecture}
|
|
```
|
|
|
|
| Parameter | Description |
|
|
|-------------------|----------------------------|
|
|
| `owner` | The owner of the package. |
|
|
| `group` | The package group . |
|
|
| `package_name` | The package name. |
|
|
| `package_version` | The package version. |
|
|
| `architecture` | The package architecture. |
|
|
|
|
Example request using HTTP Basic authentication:
|
|
|
|
```shell
|
|
curl --user your_username:your_token_or_password -X DELETE \
|
|
https://gitea.example.com/api/packages/testuser/rpm/centos/el7/package/test-package/1.0.0/x86_64
|
|
```
|
|
|
|
The server responds with the following HTTP Status codes.
|
|
|
|
| HTTP Status Code | Meaning |
|
|
| ----------------- | ------- |
|
|
| `204 No Content` | Success |
|
|
| `404 Not Found` | The package or file was not found. |
|
|
|
|
## Install a package
|
|
|
|
To install a package from the RPM registry, execute the following commands:
|
|
|
|
```shell
|
|
# use latest version
|
|
dnf install {package_name}
|
|
# use specific version
|
|
dnf install {package_name}-{package_version}.{architecture}
|
|
```
|