// ReleaseTransitions "/srv/dak/web/transitions.yaml";
//// KeyAutoFetch (optional): boolean (default: false), which if set (and
- //// not overriden by explicit argument to check_signature()) will enable
+ //// not overridden by explicit argument to check_signature()) will enable
//// auto key retrieval. Requires KeyServer variable be
//// set. NB: you should only enable this variable on production systems
//// if you have strict control of your upload queue.
//// Queue (required): This sub-tree defines important directories for the
//// incoming queue. The following variables have to be set: Byhand, New
//// NewStage, Reject, Unchecked. An explanation of the function of
- //// these directores can be found in README.new-incoming.
+ //// these directories can be found in README.new-incoming.
Queue
{
Byhand "/srv/dak/queue/byhand/";
// There are three mapping types:
//
// (1) map <source> <dest>
-// Any target suite of '<source>' is unconditionally overriden to '<dest>'.
+// Any target suite of '<source>' is unconditionally overridden to '<dest>'.
// (2) map-unreleased <source> <dest>
// Any upload targeted for suite '<source>' will be mapped to '<dest>' iff it
// contains uploads for an architecture that is not part of '<source>'.
Generic and useful, but only for those with existing archives
-------------------------------------------------------------
-o dak init-archive - initializes a projectb database from an exisiting archive
+o dak init-archive - initializes a projectb database from an existing archive
Generic but not overly useful (in normal use)
---------------------------------------------
o dak cruft-report - check for obsolete or duplicated packages
o dak init-dirs - directory creation in the initial setup of an archive
o dak check-archive - various sanity checks of the database and archive
-o dak control-overrides - manpiulates/list override entries
+o dak control-overrides - manipulates/lists override entries
o dak control-suite - removes/adds/lists package(s) from/to/for a suite
o dak stats - produces various statistics
o dak find-null-maintainers - checks for users with no packages in the archive
o dak doesn't recognise binonlyNMUs correctly in terms of telling
who their source is; source-must-exist does, but the info is not
- propogated down.
+ propagated down.
o maintainers file needs overrides
o morgue needs auto-cleaning (?)
- o dak stats: two modes, all included, seperate
+ o dak stats: two modes, all included, separate
o dak stats: add non-US
o dak stats: add ability to control components, architectures, archives, suites
o dak stats: add key to expand header
o Do a checkpc(1)-a-like which sanitizes a config files.
o fix parse_changes()/build_file_list() to sanity check filenames
- o saftey check and/or rename debs so they match what they should be
+ o safety check and/or rename debs so they match what they should be
o Improve 'dak compare-suites'.
o Need to optimize all the queries by using EXAMINE and building some INDEXs.
o archive needs md5sum'ed regularly, but takes too long to do all
in one go; make progressive or weekly.
o test sig checking stuff in test/ (stupid thing is not modularized due to global abuse)
- o when encountering suspicous things (e.g. file tainting) do something more drastic
+ o when encountering suspicious things (e.g. file tainting) do something more drastic
* Easy:
o 'dak rm' should update the stable changelog [joey]
o update tagdb.dia
- * Bizzare/uncertain:
+ * Bizzarre/uncertain:
o drop rather dubious currval stuff (?)
o rationalize os.path.join() usage
1. Little "Howto Use it"
------------------------
-The input file is in YAML format. Do bnot bother with comments, they
+The input file is in YAML format. Do not bother with comments, they
will be removed.
-The format: Dont use tabs for indentation, use spaces.
+The format: Don't use tabs for indentation, use spaces.
Strings should be within "", but normally work without.
Exception: Version-numbers with an epoch really do want to be in
-"". YES, THEY WANT TO (or they get interpreted in a way you dont expect
+"". YES, THEY WANT TO (or they get interpreted in a way you don't expect
it).
Keys (The order of them does not matter, only the indentation):
------------------------------------------------------------------------
-For completness, change the transition to (exact existing version):
+For completeness, change the transition to (exact existing version):
lintian_funtest:
reason: "Testing a new feature"
source: lintian
- lintian
- python-syck
bar_breaks_it:
- reason: We dont want bar to break it
+ reason: We don't want bar to break it
source: bar
new: "9:99"
rm: Ganneff
Source: bar
New Version: 9:99
Responsible: Ganneff
- Description: We dont want bar to break it
+ Description: We don't want bar to break it
Blocked Packages (total: 3): kdelibs, qt4-x11, libqt-perl
Transition source bar not in testing, transition still ongoing.
Source: bar
New Version: 9:99
Responsible: Ganneff
- Description: We dont want bar to break it
+ Description: We don't want bar to break it
Blocked Packages (total: 3): kdelibs, qt4-x11, libqt-perl
Transition source bar not in testing, transition still ongoing.