Project

repo-mgr

0.0
Low commit activity in last 3 years
No release in over a year
repo-mgrmr-staker/repo-mgrHomepageDocumentationSource CodeBug TrackerWiki
deb and rpm repository manager
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Popularity
Downloads
8,542
Stars
1
Forks
0
Watchers
2
 Releases
Current version
0.3.1
Total releases
6
First release
2021-04-17
Latest release
2023-04-10
 Issues
Open Issues
1
Closed Issues
1
Total Issues
2
Issue Closure Rate
50%
 Pull Requests
Open Pull Requests
3
Closed Pull Requests
5
Merged Pull Requests
2
Pull Request Acceptance Rate
20%
 Development
Primary Language
Ruby
Licenses
MIT
Average date of last 50 commits
2021-09-16
Reverse Dependencies
0

 Dependencies

Development

pry
>= 0
rake
= 13.0.3
rubocop
>= 0
juwelier
>= 0

Runtime

colored
~> 1.2
gpgme
~> 2.0
terminal-table
~> 3.0
thor
~> 1.1
git
~> 1.8.1
faraday
~> 1.9.3
nokogiri
~> 1.13.3
 Project Readme

About

deb and rpm repository management tool. Essentially, this is a frontend for a suite of tools provided by various distribution maintainers.

repo-mgr provides a unified and consistent way for managing various repositories (deb, rpm).

Features:

  • Create/update deb/rpm repositories.
  • Add/remove packages to these repositories and automatically sign packages using GPG.
  • Repository metadata/manifest signing using GPG.
  • Publish to remote via git.

To simplify things:

  • aptly (which, kind of obviously, manages deb repositories) uses "stable" as distribution and "main" as component.
  • The git publisher uses the main branch for sync only.

The requred aptly version is 1.4.0+ which may be installed from aptly's deb repository. The version available in Ubuntu 20.04 (1.3.0) doesn't support gpg2.

Install

# RubyGems
gem install repo-mgr

# from source
rake install

As repo-mgr is a frontend for other tools, there are dependencies which must be installed separately. It is not compulsory to install all dependencies, only those needed for a particular use case. The purpose for each tool is explained by check-depends.

To check which dependencies are required based on use case and their status:

repo-mgr check-depends
+------------+--------+-----------------------+
| Binary     | Status | Purpose               |
+------------+--------+-----------------------+
| aptly      | ✔      | Manage apt repository |
| dpkg-sig   | ✔      | Sign deb packages     |
| createrepo | ✔      | Manage rpm repository |
| rpm        | ✔      | Sign rpm packages     |
| git        | ✔      | Use git publisher     |
+------------+--------+-----------------------+

For managing deb repositories:

sudo apt install aptly dpkg-sig

For managing rpm repositories:

sudo apt install createrepo rpm

For using the git publisher:

sudo apt install git
n.b `createrepo` is not normally available for Debian and derrivates (including Ubuntu). This tool
has been used to bootstrap a deb repository which includes a `createrepo` build for Ubuntu 20.04,
therefore creating a dependency upon itself for setting up rpm repositories.

You can get our build of createrepo from our deb repository.

Pro tip: if the pkg signing fails because gpg can't open the output device, add this to your shell config:

export GPG_TTY=$(tty)

How to use

# to get you started
repo-mgr help

# create repo
## --path => a local directory where the repository is published - no remote support at the moment
## GPGKEYID is expected as log keyid i.e 16 hex chars
## --publisher - is optional i.e you can still manually publish a local repository
repo-mgr upsert-repo --name foo --type deb --path path/to/foo --keyid GPGKEYID --publisher git

# sign package, add to repository, and update local repo (includes sign repo release manifest)
# the local repo is exported to the path indicated in upsert-repo
# the git publisher also commits the changes as the path for upsert-repo is expected to be
# a git repository
repo-mgr add-pkg --repo foo --path path/to/bar_0.0.1_amd64.deb

# publish the repository to a remote - for git publisher this means doing git push
repo-mgr sync --repo foo

# download repo from remote e.g when changing development machines
# repo-mgr upsert-repo (...) # needed only once if the machine is brand new
## --url must point to the root of the remote repository
## i.e where the pool and dists directories can be found for deb repos
## --keyring is required for deb repositories; it is a file from
## /usr/share/keyrings - the base path is automatically prepended
## WARNING: the packages are not signed when imported via this method!
repo-mgr dl-repo --repo foo --type deb --url https://apt.example.com --keyring foo-keyring.gpg

## --arch must be specified as each rpm repo arch is self-contained
## the remote repository gpg key must be imported into the user's keyring and trusted
## prior to starting the import process from remote rpm repo
repo-mgr dl-repo --repo foo --type rpm --url https://rpm.example.com --arch x86_64

Migrating from v0.1

The package list is stored into a structure that's prone to lose the list upon re-running upsert-repo for v0.1.x of this gem. For this reason, the package list data structure has been redesigned within repo-mgr's config file.

So, to migrate from this earlier version, you must run, for every repo:

repo-mgr rebuild-pkg-list --repo foo

This rebuilds the data structure in the new config location.