In this repository we keep our Debian packages, some are backports, some are special built and some are own packages. Since we build only for our own needs, packages are usually not available for all architectures.
You are using this repository and it's contents on your own responsibility. We are not deliberately distributing any harmfull software here, but software allways contains a certain amount of bugs that might harm your system and/or data, so again: Any use is on your own risk.
The repository can be accessed by the usual way. Simply putt lines like this in your /etc/apt/source.list:
deb http://ftp.architektur.tu-darmstadt.de/debian/ stable main contrib non-free deb-src http://ftp.architektur.tu-darmstadt.de/debian/ stable main contrib non-free
Alternatively you can create a list file in /etc/apt/source.list.d/
containing the repository lines.
Of course you may need to change stable to fit your needs.
Distribution names also work (i.e. sarge, etch, lenny, squeeze, wheezy, sid).
Currenty we have squeeze, squeeze-backports and wheezy in our perository.
This repository accommodates self-signed packages uploaded to it. These
packages are verified against a whitelist of trusted uploaders using
OpenPGP (GnuPG, to be more precise).
The archive itself is signed by it's own key.
You can download the public key and add it to your apt keystore:
wget http://ftp.architektur.tu-darmstadt.de/debian/tud_fb15.asc apt-key add tud_fb15.asc apt-get update
or shorter:
wget -qO - http://ftp.architektur.tu-darmstadt.de/debian/tud_fb15.asc | apt-key add - && apt-get update
You can either browse the archive manually or you can view a automatically generated list of it.
Since we have a backports archive as well as some secial buit packages in our repository you might want do watch your pinning. Debian will usually pin unspecified repositorys with a priority of 500, but it's own backports only with 100. This way you might get accidentaly some packages from this repository you intended to install from the official backports repository.
Example:
apt-cache policy navit navit: Installed: 0.5.0~svn5337+dfsg.1-1~bpo60+1 Candidate: 0.5.0~svn5337+dfsg.1-1~bpo60+1 Version table: *** 0.5.0~svn5337+dfsg.1-1~bpo60+1 0 500 http://ftp.architektur.tu-darmstadt.de/debian/ squeeze-backports/main amd64 Packages 100 /var/lib/dpkg/status 0.5.0~svn4776+dfsg.1-1~bpo60+1 0 100 http://backports.debian.org/debian-backports/ squeeze-backports/main amd64 Packages 0.2.0~svn3501+dfsg.1-1 0 990 http://ftp.de.debian.org/debian/ squeeze/main amd64 Packages
As you can see in this example, the official squeeze-backports repository has a priority of 100 whereas this repository has 500. So either increase the priority of squeeze-backports, or lower the priority of this archive by creating a file /etc/apt/preferences.d/squeeze-backports:
Package: * Pin: origin "backports.debian.org" Pin-Priority: 600
or /etc/apt/preferences.d/tud-fb15:
Package: * Pin: origin "ftp.architektur.tu-darmstadt.de" Pin-Priority: 40
You can then pin a specific package to this source i.e. /etc/apt/preferences.d/navit
Package: navit navit-data navit-graphics-gtk-drawing-area navit-graphics-opengl navit-graphics-sdl navit-gui-internal navit-gui-gtk Pin: origin "ftp.architektur.tu-darmstadt.de" Pin-Priority: 999