(Last updated: Jun 16, 2019)

I've using Arch Linux for awhile now, and this is my own Arch repo for various things which aren't in the main repos. Mostly these are packages taken from AUR and compiled by myself, but in some cases they're duplicates of official packages which have a bugfix patch or two applied.

Packages (and the repo itself) are signed with this key.

To enable the repo (not that anyone but myself is likely to ever want to do so), you'd follow the instructions found at the Arch wiki under unofficial_user_repositories and Package_signing#Adding_unofficial_keys. Briefly, though, add the following to /etc/pacman.conf:

[cj]
SigLevel = Required
Server = http://apocalyptech.com/linux/arch/cj

Then do one of the following:

  1. Grab cj_arch_signing_key.pub and run:

    pacman-key -a cj_arch_signing_key.pub
  2. Or just have pacman-key grab it from a keyserver:
    pacman-key -r 9E91E6BC8BF2B7028B77F6AE800A59499850590A
In either case, then run the following to sign the key:
pacman-key --lsign-key 9E91E6BC8BF2B7028B77F6AE800A59499850590A

"Source" packages are available as well, created with "makepkg -S". These files just contain PKGBUILD, for the most part, and any other support files which aren't the actual sourcecode packages themselves (which makepkg will fetch on its own when you make them).

Note: Pacman handles packages from multiple repos a little differently than you might expect, if you're more used to yum/dnf/apt/etc. Specifically, if you pacman -Sy packagename to install a package, it will stop looking for other versions of packagename once it finds one repo which provides the package. The upshot is that in the cases where I've uploaded a new version of an existing package (generally to address some bug which hasn't made it into an official release yet), if my own repo is specified lower in pacman.conf than the official repos, the "new" package will not be installed. So, you'd have to install it with a pacman -Sy cj/packagename, explicitly setting the repo.

Alternatively, of course, you could list this repo higher in the conf file than the official ones, but the problem with that is that future runs of pacman -Syu won't update the package anymore. Since my general use case for packages with the same name is that I'm just patching for things which will be in the next official release, that's probably not what you want. Best to keep it defined below the official repos, and "manually" install the patched version by specifying the repo name.

The Repo

What's in here, anyway?

Back to Linux pages

Changelog

Jun 16, 2019
  • rebuilds/upgrades of various Perl libraries, for new Perl version
  • removed perl-mp4-info and perl-ogg-vorbis-header-pureperl
  • added perl-test-useallmodules, a new requirement of perl-net-netmask
Apr 23, 2019
  • minecraft-launcher
Mar 20, 2019
  • hfsprogs
Feb 7, 2019
  • dolphin-emu-git and dolphin-emu-nogui-git
Jan 21, 2019
  • citra-git and citra-qt-git
Jan 15, 2019
  • updated dosbox 0.74.2-2 with r4177 fix
Jan 10, 2019
  • python-pygdbmi and pince-git
Sep 20, 2018
  • rebuild of python-mysqlclient for Python 3.7
Sep 19, 2018
  • rebuild of various Perl libraries, for new Perl version
Aug 4, 2018
  • motion rebuild
Mar 10, 2018
  • motion
Jan 2, 2018
  • logstalgia rebuild
Nov 12, 2017
  • cvs2svn
Oct 11, 2017
  • gargoyle-git and grotz
Oct 4, 2017
  • perl-musicbrainz-discid and perl-webservice-musicbrainz0
June 2017
  • Frotz and Fizmo
?
  • Initial post