Debian Packages

Only wimps use tape backup: real men just upload their important stuff on ftp, and let the rest of the world mirror it.

Linus Torvalds

I maintain Debian packages for much of the software that I maintain, as well as for some other packages that I personally use. The packages of general interest I upload directly to Debian; they can be obtained from the current unstable or testing distribution. See also my Debian QA package overview, which includes considerable additional information for those packages in Debian proper, including the versions in each separate distribution, the current bug counts, lintian reports, package upload history, and quite a bit more. This is one of the nicest features of Debian.

I am a member of the Debian Policy team, one of the co-maintainers of lintian, and try to help with other teams as I have time (particularly the Perl packaging team and OpenLDAP). I unfortunately have a lot of demands on my time and can't do as much for Debian as I'd ideally like, but every once in a while I manage to help. Note that various Perl packages and some other co-maintained packages like OpenLDAP will show up in my QA summary even if I'm not particularly active in maintaining those at present.

Installing

For packages in Debian, you can download and install them like any other package in Debian. If you are running Debian stable and want to install one of the packages from unstable or testing, you may have to download and build the source with apt-get --build source. If there are any packages I maintain that are difficult to build on stable and for which you would particularly like to see a stable backport, let me know and I may upload a backport to backports.org.

For the other packages, the easiest way to install them is via apt-get or aptitude from my personal repository. Add the following line to your /etc/apt/sources.list file:

    deb http://archives.eyrie.org/debian unstable main non-free contrib

Change unstable to testing, stable, or whatever other distribution you're running. Most packages will be uploaded only to unstable, and normally testing (and its code name) will just be a link to unstable. During freezes, I'll split the testing repository off of unstable, and then will eventually promote it to the new stable, similar to how Debian does it.

My packages are (at least for the time being) only built on i386. If you have another platform, or if you just want to see the source packages, add:

    deb-src http://archives.eyrie.org/debian unstable main non-free contrib

with the same change of unstable to something else as appropriate. You can then build packages for your local architecture with apt-get --build source.

If you want to get to these .deb packages without using apt-get, you can also browse my repository via either HTTP or FTP and find the .deb files in the standard (not package pool) Debian archive locations.

Packages in Debian

The following packages for software I also maintain are uploaded directly to Debian:

I also maintain the following packages for Debian (although I don't maintain the upstream software):

The following OpenAFS- and Kerberos-related packages I co-maintain with Sam Hartman. I'm also an OpenAFS Gatekeeper and am involved in upstream development and maintenance of it.

Finally, I co-maintain the following packages as part of other teams, either formal or informal:

Packages Not in Debian

I maintain the following packages (but not the upstream software) and plan to get them included in Debian proper but haven't had a chance yet:

The blocking problem with libafs-perl is that OpenAFS doesn't produce usable shared libraries and therefore the current Debian package is built against static libraries with non-PIC code. This works on x86, but it violates Debian policy and doesn't work on other platforms.

The blocking problem for lbcd is that I need to package all of lbnamed as well (including its Perl dependencies) before lbcd is useful, and I've only gotten a small handful of requests.

The following packages for my software may or may not ever be uploaded to Debian proper, depending on how generally useful they seem to others, but will be maintained in my personal repository:

Stanford-Specific Packages

I also have the following packages in my personal repository and in some internal Stanford repositories. These packages won't be uploaded to Debian proper since they're very Stanford-specific, but may be of interest to other people running Debian at Stanford.