mirror of
https://codeberg.org/forgejo/forgejo
synced 2024-11-27 12:16:10 +01:00
6c133b9fe0
According to [Debian docs](https://wiki.debian.org/DebianRepository/UseThirdParty): > The certificate MUST NOT be placed in /etc/apt/trusted.gpg.d or loaded by apt-key add. > ... > If future updates to the certificate will be managed by an apt/dpkg package as recommended below, then it SHOULD be downloaded into /usr/share/keyrings using the same filename that will be provided by the package. If it will be managed locally , it SHOULD be downloaded into /etc/apt/keyrings instead. > ... > A sources.list entry SHOULD have the signed-by option set.
132 lines
4.4 KiB
Markdown
132 lines
4.4 KiB
Markdown
---
|
|
date: "2023-01-07T00:00:00+00:00"
|
|
title: "Debian Package Registry"
|
|
slug: "debian"
|
|
draft: false
|
|
toc: false
|
|
menu:
|
|
sidebar:
|
|
parent: "packages"
|
|
name: "Debian"
|
|
sidebar_position: 35
|
|
identifier: "debian"
|
|
---
|
|
|
|
# Debian Package Registry
|
|
|
|
Publish [Debian](https://www.debian.org/distrib/packages) packages for your user or organization.
|
|
|
|
## Requirements
|
|
|
|
To work with the Debian registry, you need to use a HTTP client like `curl` to upload and a package manager like `apt` to consume packages.
|
|
|
|
The following examples use `apt`.
|
|
|
|
## Configuring the package registry
|
|
|
|
To register the Debian registry add the url to the list of known apt sources:
|
|
|
|
```shell
|
|
echo "deb [signed-by=/etc/apt/keyrings/gitea-{owner}.asc] https://gitea.example.com/api/packages/{owner}/debian {distribution} {component}" | sudo tee -a /etc/apt/sources.list.d/gitea.list
|
|
```
|
|
|
|
| Placeholder | Description |
|
|
| -------------- | ----------- |
|
|
| `owner` | The owner of the package. |
|
|
| `distribution` | The distribution to use. |
|
|
| `component` | The component to use. |
|
|
|
|
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
|
|
echo "deb [signed-by=/etc/apt/keyrings/gitea-{owner}.asc] https://{username}:{your_password_or_token}@gitea.example.com/api/packages/{owner}/debian {distribution} {component}" | sudo tee -a /etc/apt/sources.list.d/gitea.list
|
|
```
|
|
|
|
The Debian registry files are signed with a PGP key which must be known to apt:
|
|
|
|
```shell
|
|
sudo curl https://gitea.example.com/api/packages/{owner}/debian/repository.key -o /etc/apt/keyrings/gitea-{owner}.asc
|
|
```
|
|
|
|
Afterwards update the local package index:
|
|
|
|
```shell
|
|
apt update
|
|
```
|
|
|
|
## Publish a package
|
|
|
|
To publish a Debian package (`*.deb`), perform a HTTP `PUT` operation with the package content in the request body.
|
|
|
|
```
|
|
PUT https://gitea.example.com/api/packages/{owner}/debian/pool/{distribution}/{component}/upload
|
|
```
|
|
|
|
| Parameter | Description |
|
|
| -------------- | ----------- |
|
|
| `owner` | The owner of the package. |
|
|
| `distribution` | The distribution may match the release name of the OS, ex: `bionic`. |
|
|
| `component` | The component can be used to group packages or just `main` or similar. |
|
|
|
|
Example request using HTTP Basic authentication:
|
|
|
|
```shell
|
|
curl --user your_username:your_password_or_token \
|
|
--upload-file path/to/file.deb \
|
|
https://gitea.example.com/api/packages/testuser/debian/pool/bionic/main/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 package if a package of the same name, version, distribution, component and architecture already exists. You must delete the existing package 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 exists already. |
|
|
|
|
## Delete a package
|
|
|
|
To delete a Debian 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}/debian/pool/{distribution}/{component}/{package_name}/{package_version}/{architecture}
|
|
```
|
|
|
|
| Parameter | Description |
|
|
| ----------------- | ----------- |
|
|
| `owner` | The owner of the package. |
|
|
| `package_name` | The package name. |
|
|
| `package_version` | The package version. |
|
|
| `distribution` | The package distribution. |
|
|
| `component` | The package component. |
|
|
| `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/debian/pools/bionic/main/test-package/1.0.0/amd64
|
|
```
|
|
|
|
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 Debian registry, execute the following commands:
|
|
|
|
```shell
|
|
# use latest version
|
|
apt install {package_name}
|
|
# use specific version
|
|
apt install {package_name}={package_version}
|
|
```
|