This project has been archived by its maintainers, and is no longer receiving any updates.
Arch Linux Custom Repository Manager
This program is intended to manage an Arch Linux custom repository hosted on a server accessible through rsync
(for example, on a VPS or a NAS with a /path/to/www folder served over the web by a web server).
It works by synchronizing the remote repository on the local machine using rsync, and then mainly uses repo-add to
manage this repository to finally synchronizing back to the remote server.
It requires to run on an Arch Linux distribution, and simply behaves as a wrapper around some common programs:
| Program | From package | Used for |
|---|---|---|
| uname | core/coreutils | Detecting the architecture of the local machine |
| rsync | extra/rsync | Synchronizing the repository |
| tar | core/tar | Reading inside the repository database |
| GnuPG | core/gnupg | Signing the packages and the repository |
| repo-add | core/pacman | Managing the packages in the repository |
Global options
| Option | Short | Required | Description |
|---|---|---|---|
host |
H |
yes | Specify the host on which the repository is hosted |
remote_root |
r |
yes | The path to the repository, on the remote host |
user |
u |
no | The remote user who owns the repository Defaults to the current local user |
repository |
d |
no | The name of the repository Defaults to the name of the directory |
Commands
ls
List all the packages with their version in the repository.
acrm -H my_vps_or_nas -r /home/vps_user/path/to/my/repository ls
+------ repository ------+
| Package name | version |
+--------------+---------+
| acrm | 0.1.1-1 |
+--------------+---------+
add
Add a package to the repository.
acrm -H my_vps_or_nas -r /home/vps_user/path/to/my/repository add -k gpg@example.com acrm-0.1.1-1-x86_64.pgk.tar.zst
The -k key_identifier option allows to specify the gpg key used to sign the package and the repository.
If omitted, gpg will automatically choose a default one.
rm
Remove a package from the repository.
acrm -H my_vps_or_nas -r /home/vps_user/path/to/my/repository rm -k gpg@example.com acrm
dl
Download a package from the repository.
acrm -H my_vps_or_nas -r /home/vps_user/path/to/my/repository dl acrm
Metadata
Release files for acrm 0.1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| acrm-0.1.3.tar.gz | 7.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| acrm-0.1.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 15.7 kB
Release files / acrm-0.1.3.tar.gz
| Download URL | acrm-0.1.3.tar.gz |
|---|---|
| Size | 7.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c95943eaee88d7b974e989ab7824d473d6bc06bf953abce53ccef32ce71dc8c1
|
|
BLAKE2b-256 checksum How to use checksums |
a7499a7ce19433074933408a47d29e099f7270a38c661eae72630070e1e46e00
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 13, 2025.
Transparency logRelease files / acrm-0.1.3-py3-none-any.whl
| Download URL | acrm-0.1.3-py3-none-any.whl |
|---|---|
| Size | 8.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b62cd753a27893c8059b628a7e3ecb33322b6cce6bb096080ca49411afd4c03e
|
|
BLAKE2b-256 checksum How to use checksums |
70bbbe6c71b7b9ba9013c69518cde8d87f6a7b1f64b954a21230d16ac6ac900c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 13, 2025.
Transparency log