I use Arch Linux as my primary desktop and server operating system, and I use a lot of packages that are not in the public repositories. They cover a wide range of features, but most of them are developer tools or Dev Ops-related in some way. Also, there are various packages that are either:
- not kept up-to-date in a timely manner by their maintainers, or
- out of sync with the requirements of packages that depend on them.
community/gitlab is constantly being updated in the repository, but
gitlab-workhorse, which are both dependencies, are often times left behind. When this happens, I will usually have the current build within an hour of finding out. Also, when things are in sync, you should use the official packages and thus my repo won't contain that package.
Note this is not a complaint: The maintainers do a great job, and I like doing this anyway :)
Currently, I host packages for:
- 32-Bit Intel (i686)
- 64-Bit Intel x86 (x86_64)
- Arch on Raspberry Pi 2/3 (armv7h)
- ODROID-C2 (aarch64) Currently on hold due lack of hardware
Please note that package availability may vary by platform.
Using the Repository
To use my binary packages, add the following to your
Server = https://repo.robisonweb.net/arch/$arch
Server = https://repo-west.robisonweb.net/arch/$arch
As you can see, there are two mirrors: The main mirror (repo.robisonweb.net) is hosted at Linode in Newark, NJ. The West Region mirror is hosted by Digital Ocean. Packages are uploaded first to the Linode mirror, then rsync'ed to the West mirror using Watchman, so things should be in sync pretty quickly after an update.
Verifying Package Integrity
You should also install the
robisonweb-keyring package to verify the integrity of my packages. If you can't install the package after a
pacman -Syu, you may need to do this manually: Download the keyring package file, alternate signature file (the package is signed with my primary key as well as the archive key), and verify the package:
wget -O robisonweb-keyring-20170319-1-any.pkg.tar.xz.sig https://repo.robisonweb.net/arch/robisonweb-keyring/robisonweb-keyring-20170319-1-any.pkg.tar.xz.alt.sig
gpg --keyserver hkp://keys.gnupg.net --recv-keys 72D60484257207CD5DC538A8C1EFAFBBCD325738
gpg --verify robisonweb-keyring-20170319-1-any.pkg.tar.xz.sig
Then, if you get a
Good signature message, install the package:
sudo pacman -U robisonweb-keyring-20170319-1-any.pkg.tar.xz
After this step, you can delete the .sig and .pkg.tar.xz files, as the package will be managed by my repo from then on.
One final step, if you haven't initialized your Arch keyring, you'll need to do this before my keyring will populate. Usually this is done during Arch installation, but I have seen rare cases where it is not (VM images come to mind). My package will tell you how to do this if it needs to be done.
There are some packages that have been updated, but I'm not quite ready to include the new version in my main repository yet. For these, I have set up a staging repository. If you want to live on the edge and test out these updates and new packages, you can add these lines BEFORE the
[robisonweb] entry above:
Server = https://repo.robisonweb.net/arch/staging/$arch
Server = https://repo-west.robisonweb.net/arch/staging/$arch
All architectures are supported in staging as well as the standard repository, but there may not be any packages at any given time.
Some of the packages I host are built unmodified from the Arch User Repository, and thus I do not provide source code unless I modify the package in some way. For packages with modifications, or that haven't been upgraded in the AUR, or my own packages, please refer to my GitLab Arch Linux group.
For a list of available packages, please see the Package Index. Please note, though, that it is populated manually and thus may not have the latest updates.