uvalde: yum repository management tool

Uvalde is a simple CLI tool for managing yum repositories. There is no daemon and no web interface, just a directory of yum repositories and a small sqlite database to remember what RPMs were built from the same SRPM.

Usage

Before running the application, create a config file to define the repositories you want to manage. The base directory doesn't need to exist yet, uvalde will create it if needed.

~/.config/uvalde/repos.ini

[my-repo]
base = /home/me/my-repo
architectures = i686, x86_64

[my-other-repo]
base = /home/me/my-other-repo
architectures = i686, x86_64

Now you can add RPM files and they will be placed at the appropriate locations relative to your repository base. Repository metadata will also be generated.

$ uvalde add --repo my-repo cello-*.rpm
adding RPMs
generating repodata

$ tree my-repo
my-repo
├── i686
│   ├── debug
│   │   ├── packages
│   │   │   └── c
│   │   │       ├── cello-debuginfo-1.0-1.i686.rpm
│   │   │       └── cello-debugsource-1.0-1.i686.rpm
│   │   └── repodata
│   │       ├── filelists.xml.gz
│   │       ├── other.xml.gz
│   │       ├── primary.xml.gz
│   │       └── repomd.xml
│   ├── packages
│   │   └── c
│   │       ├── cello-1.0-1.i686.rpm
│   │       └── cello-extra-1.0-1.noarch.rpm
│   └── repodata
│       ├── filelists.xml.gz
│       ├── other.xml.gz
│       ├── primary.xml.gz
│       └── repomd.xml
├── src
│   ├── packages
│   │   └── c
│   │       └── cello-1.0-1.src.rpm
│   └── repodata
│       ├── filelists.xml.gz
│       ├── other.xml.gz
│       ├── primary.xml.gz
│       └── repomd.xml
└── x86_64
    ├── debug
    │   ├── packages
    │   │   └── c
    │   │       ├── cello-debuginfo-1.0-1.x86_64.rpm
    │   │       └── cello-debugsource-1.0-1.x86_64.rpm
    │   └── repodata
    │       ├── filelists.xml.gz
    │       ├── other.xml.gz
    │       ├── primary.xml.gz
    │       └── repomd.xml
    ├── packages
    │   └── c
    │       ├── cello-1.0-1.x86_64.rpm
    │       └── cello-extra-1.0-1.noarch.rpm
    └── repodata
        ├── filelists.xml.gz
        ├── other.xml.gz
        ├── primary.xml.gz
        └── repomd.xml

20 directories, 29 files

The relationships between RPMs and SRPMs are stored in an sqlite database so that you can manage the files collectively, referencing them by the NVR (name-version-release) string. When RPMs are moved the repository metadata will be regenerated as needed.

$ uvalde list
my-repo
  cello-1.0-1
my-other-repo

$ uvalde move --from my-repo --to my-other-repo cello-1.0-1
moving RPMs
generating repodata

$ uvalde list
my-repo
my-other-repo
  cello-1.0-1

$ uvalde remove --repo my-other-repo cello-1.0-1
removing RPMs
generating repodata

$ uvalde list
my-repo
my-other-repo

If you migrate the repo directory to a new system, you don't have to copy over the sqlite database. Just copy the repo directory and your config, then you can regenerate the database.

$ uvalde index my-repo
indexing repo my-repo

Configuration Settings

~/.config/uvalde/repos.ini

[my-repo]

# The base and architectures determine the filesystem paths for your yum
# repositories.  These are required settings.
base = /home/me/my-repo
architectures = i686, x86_64

# The prefix setting controls the directory layout for RPM files in a
# repository.  It uses PEP 3101 string formatting, and is passed an argument of
# the RPM filename.  It is optional.  The default value is 'packages/{:.1}',
# which means use a packages directory with a subdirectory of the first letter
# of the RPM filename.
prefix = packages/{:.1}

# The hidden setting controls if this repo is shown in the default
# `uvalde list` output.  Hidden repos can still be shown with the `--all` flag,
# or by asking for them by name with the `--repo` flag.  It is optional, and
# defaults to no.
hidden = no