configured properly will happily send them to lots of people who
probably didn't want those emails.
-o Don't use the debian dak.conf, apt.conf, cron.* etc. as starting
+o Don't use the debian dak.conf, cron.* etc. as starting
points for your own configuration files, they're highly Debian
specific. Start from scratch and refer to the security.debian.org
config files (-security) as they're a better example for a private
o To generate indices files:
- * dak make-suite-file-list - generates file lists for apt-ftparchive
- and removes obsolete packages from
- suites
+ * dak dominate - removes obsolete packages from suites
+ * dak generate-filelist - generates file lists for apt-ftparchive
* dak generate-releases - generates Release
o To clean things up:
* dak ls - shows information about package(s)
* dak queue-report - shows information about package(s) in queue/
* dak override - can show you individual override entries
+ * dak graph - creates some pretty graphs of queue sizes over time
Generic and useful, but only for those with existing archives
-------------------------------------------------------------
-o dak poolize - migrates packages from legacy locations to the pool
o dak init-archive - initializes a projectb database from an exisiting archive
Generic but not overly useful (in normal use)
----------------------------
o dak security-install - wrapper for Debian security team
-o dak clean-proposed-updates - removes obsolete .changes files from proposed-updates
-o dak check-proposed-updates - basic dependency checking for proposed-updates
-o dak reject-proposed-updates - manually reject packages from proposed-updates
o dak import-ldap-fingerprints - syncs fingerprint and uid information with a debian.org LDAP DB
Very Incomplete or otherwise not generally useful
--------------------------------
o dak examine-package - invoked by 'dak process-new' to "check" NEW packages
-o dak symlink-dists - invoked by 'dak poolize' to determine packages still in legacy locations
How do I get started?
=====================
[Very incomplete - FIXME]
-o Write your own dak.conf and apt.conf files. dak looks for those
- config files in /etc/dak/. /etc/dak/dak.conf can define
- alternative configuration files with Config::host::DakConfig and
- Config::host::AptConfig (where "host" is the fully qualified domain
- name of your machine).
+o Write your own dak.conf file. dak looks for this
+ config file in /etc/dak/. /etc/dak/dak.conf can define an
+ alternative configuration file with Config::host::DakConfig
+ (where "host" is the fully qualified domain name of your machine).
o Create a PostgreSQL database on the host given in dak.conf's DB::Host
with the name specified in DB::Name.
o Run 'dak init-dirs': this will create all directories which are specified in
- dak.conf and apt.conf.
+ dak.conf:
o If you have an existing archive:
* Run 'dak init-archive'
otherwise:
* Create the following groups in postgres: ftpmaster ftpteam ftptrainee
* Run 'dak update-db' to upgrade the database schema.
* Run 'dak init-db': it will populate your database with the values from
- dak.conf and apt.conf.
+ dak.conf
* Run 'psql <DB::Name> < add_constraints.sql'.
o Copy all templates from the "templates" directory to to the directory
specified in Dir::Templates, and adapt them to your distribution.