1
0
mirror of https://github.com/go-gitea/gitea.git synced 2024-11-04 08:17:24 -05:00
gitea/docs/content/doc/usage/packages/debian.en-us.md
KN4CK3R bf77e2163b
Add Debian package registry (#22854)
Co-authored-by: @awkwardbunny

This PR adds a Debian package registry. You can follow [this
tutorial](https://www.baeldung.com/linux/create-debian-package) to build
a *.deb package for testing. Source packages are not supported at the
moment and I did not find documentation of the architecture "all" and
how these packages should be treated.

---------

Co-authored-by: Brian Hong <brian@hongs.me>
Co-authored-by: techknowlogick <techknowlogick@gitea.io>
2023-04-28 17:51:36 -04:00

4.4 KiB

date title slug draft toc menu
2023-01-07T00:00:00+00:00 Debian Packages Repository packages/debian false false
sidebar
parent name weight identifier
packages Debian 35 debian

Debian Packages Repository

Publish Debian packages for your user or organization.

Table of Contents

{{< toc >}}

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:

echo "deb 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]({{< relref "doc/development/api-usage.en-us.md#authentication" >}}):

echo "deb 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:

sudo curl https://gitea.example.com/api/packages/{owner}/debian/repository.key -o /etc/apt/trusted.gpg.d/gitea-{owner}.asc

Afterwards update the local package index:

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:

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]({{< relref "doc/development/api-usage.en-us.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 reponds with the following HTTP Status codes.

HTTP Status Code Meaning
201 Created The package has been published.
400 Bad Request The package name, version, distribution, component or architecture are invalid.
409 Conflict A package file with the same combination of parameters exist already in the package.

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:

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 reponds 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:

# use latest version
apt install {package_name}
# use specific version
apt install {package_name}={package_version}