-Explanation of configuration files options for katie
-====================================================
+Explanation of configuration files options for dak
+==================================================
DB
--
| };
Name (required): The name of the PostgreSQL database which has been created
-for katie.
+for dak.
Host (required): The name of the host on which the database is located. If
the database is local, Host should be blank.
| {
| Root "/org/ftp.debian.org/ftp/";
| Pool "/org/ftp.debian.org/ftp/pool/";
-| Templates "/org/ftp.debian.org/katie/templates/";
+| Templates "/org/ftp.debian.org/dak/templates/";
| PoolRoot "pool/";
| Override "/org/ftp.debian.org/scripts/override/";
| Lists "/org/ftp.debian.org/database/dists/";
Root (required): Specifies the path of the root of the FTP archive.
-Pool (required): This variable specifies the path of the pool directory.
-Debian packages will be placed in the pool by kelly after they have been
-accepted by jennifer.
+Pool (required): This variable specifies the path of the pool
+directory. Debian packages will be placed in the pool by 'dak
+process-accepted' after they have been accepted by dak
+process-unchecked.
-Templates (required): katie sends various mails and uses templates from
+Templates (required): dak sends various mails and uses templates from
this directory.
PoolRoot (required): This variable specifies the basename of the pool
directory.
Override (optional): This directory optionally stores override files (used
-by denise).
+by 'dak make-overrides').
Lists (optional): This directory holds file lists used by apt-ftparchive to
-generate Packages and Sources files (used by jenna).
+generate Packages and Sources files (used by 'dak make-suite-file-list').
Log (required): Log files are put in this directory.
Morgue (required): Removed files are moved there. The morgue has various
sub-directories, including (optionally) those defined by
-Shania::MorgueSubDir and Rhona::MorgueSubDir.
+Clean-Queues::MorgueSubDir and Clean-Suites::MorgueSubDir.
-MorgueReject (required): if katie cannot move a rejected package to
+MorgueReject (required): if dak cannot move a rejected package to
Dir::Queue::Reject, it will try to move it to the Dir::MorgueReject
directory located under Dir::Morgue.
are to be auto built, i.e. if Dinstall::QueueBuildSuites has any
values.
-UrgencyLog (optional): If this directory is specified, kelly will store the
-urgency value of each upload. This is mainly used for britney (the testing
-script).
+UrgencyLog (optional): If this directory is specified, 'dak
+process-accepted' will store the urgency value of each upload. This
+is mainly used for britney (the testing script).
Queue (required): This sub-tree defines important directories for the
incoming queue. The following variables have to be set: Accepted, Byhand
Announce (optional): controls where "Installed foo" mails are sent.
-CodeName, Origin and Description (optional): This settings are used by ziyi
-and put in the Release files.
+CodeName, Origin and Description (optional): This settings are used by
+'dak generate-releases' and put in the Release files.
-OverrideCodeName (optional): used by Denise.
+OverrideCodeName (optional): used by 'dak make-overrides'.
Priority (optional) determines which suite is used for the Maintainers file
-as generated by charisma/da_mkmaintainers (highest wins).
+as generated by 'dak make-maintainers' (highest wins).
CopyChanges (optional): if this variable is present it should be a path
into the archive (i.e. "Dir::RootDir"); any upload targeted for a suite
with this config option present will have the .changes file copied into
that path.
-CopyKatie (optional): if this is present it should be an absolute path; any
+CopyDotDak (optional): if this is present it should be an absolute path; any
upload targeted for a suite with this config option present will have the
-.katie file copied into that path. This option is similar to CopyChanges
+.dak file copied into that path. This option is similar to CopyChanges
and will most often be used with it; they're seperate because .changes
-files are mirrored and .katie files aren't, so the paths will usually be
+files are mirrored and .dak files aren't, so the paths will usually be
different.
There are more optional variables, such as VersionChecks. Please see
-katie.conf for examples.
+dak.conf for examples.
================================================================================
| BugServer "bugs.debian.org";
| PackagesServer "packages.debian.org";
| TrackingServer "packages.qa.debian.org";
-| LockFile "/org/ftp.debian.org/katie/lock";
+| LockFile "/org/ftp.debian.org/dak/lock";
| Bcc "archive@ftp-master.debian.org";
| GroupOverrideFilename "override.group-maint";
| FutureTimeTravelGrace 28800; // 8 hours
| };
PGPKeyring and GPGKeyring (required): filenames of the PGP and GnuPG
-keyrings to be used by katie respectively.
+keyrings to be used by dak respectively.
-SigningKeyring (optional): this is the private keyring used by ziyi.
+SigningKeyring (optional): this is the private keyring used by 'dak
+generate-releases'.
SendmailCommand (required): command to call the MTA.
MyAdminAddress (required): used as a contact address in mails.
MyDistribution (required): this variable is used in emails sent out by
-katie and others. It should indicate the name of the distribution.
+dak and others. It should indicate the name of the distribution.
-BugServer (required): is used by katie and melanie when closing bugs.
+BugServer (required): is used by 'dak process-unchecked' and 'dak rm'
+when closing bugs.
-PackagesServer (requried): used by melanie when carbon-copying a bug close
-mail to a package maintainer.
+PackagesServer (requried): used by 'dak rm' when carbon-copying a bug
+close mail to a package maintainer.
-TrackingServer (optional): used by katie and melanie to send messages for
-the maintainer also to an alias for people tracking a specific source
-package.
+TrackingServer (optional): used by 'dak process-unchecked' and 'dak
+rm' to send messages for the maintainer also to an alias for people
+tracking a specific source package.
LockFile (required): contains the filename of the lockfile used by dinstall
when in action mode (i.e. not using -n/--no-action).
BXANotify (optional): a boolean (default: no); if true (Debian-specific)
BXA notification is sent. The template for the BXA notification is located
-in Dir::Templates/lisa.bxa_notification and should be changed if this
+in Dir::Templates/process-new.bxa_notification and should be changed if this
option is set.
OverrideDisparityCheck (optional): a boolean (default: no); if true,
-jennifer compares an uploads section/priority with the overrides and whines
+dak process-unchecked compares an uploads section/priority with the overrides and whines
at the maintainer if they differ.
CloseBugs (optional): a boolean (default: no); if true the automated bug
Use with caution.
SkipTime (required): an integer value which is the number of seconds that a
-file must be older than (via it's last modified timestamp) before jennifer
+file must be older than (via it's last modified timestamp) before dak process-unchecked
will REJECT rather than SKIP the package.
================================================================================
| };
| };
-OriginServer and PrimaryMirror (required): used melanie's bug closing mail
+OriginServer and PrimaryMirror (required): used 'dak rm's bug closing mail
templates. The host name and it's OriginServer and Description are part of
the SQL database in the 'archive' table.
in Archive.
[Note: yes, this is horrible, it dates back to the original `import
- the existent archive into the SQL Database' script (neve) and
+ the existent archive into the SQL Database' script ('dak import-archive') and
isn't otherwise used. It should be revisted at some stage.]
================================================================================
uploaded with an urgency not listed here, it will be rejected.
================================================================================
-
---
-James Troup <james@nocrew.org>, Horsforth, Leeds
-Wed, 26 Sep 2001 03:20:39 +0100
Notes
=====
-o Please be careful: katie sends out lots of emails and if not
+o Please be careful: dak sends out lots of emails and if not
configured properly will happily send them to lots of people who
probably didn't want those emails.
-o Don't use katie.conf, apt.conf, cron.* etc. as starting points for
- your own configuration files, they're the configuration files for
- auric (aka ftp-master.debian.org) and are 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 archive.
-
-o Don't be put off by the names, see doc/README.names for a mapping of
- name -> what the script does.
+o Don't use the debian dak.conf, apt.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
+ archive.
What do all these scripts do?
=============================
o To process queue/:
- * jennifer - processes queue/unchecked
- * kelly - processes queue/accepted
- * lisa - processes queue/new and queue/byhand
+ * dak process-unchecked - processes queue/unchecked
+ * dak process-accepted - move files from queue/accepted into the pool (and database)
+ * dak process-new - allows ftp administrator to processes queue/new and queue/byhand
o To generate indices files:
- * jenna - generates file lists for apt-ftparchive and removes
- obsolete packages from suites
- * ziyi - generates Release
+ * dak make-suite-file-list - generates file lists for apt-ftparchive
+ and removes obsolete packages from
+ suites
+ * dak generate-releases - generates Release
o To clean things up:
- * rhona - to remove obsolete files from the pool
- * shania - to remove obsolete/stray files from the queue
- * melanie - to remove package(s) from suite(s)
- * alicia - to change individual override entries
+ * dak clean-suites - to remove obsolete files from the pool
+ * dak clean-queues - to remove obsolete/stray files from the queue
+ * dak rm - to remove package(s) from suite(s)
+ * dak override - to change individual override entries
o Information display:
- * madison - shows information about package(s)
- * helena - shows information about package(s) in queue/
- * alicia - can show you individual override entries
+ * 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
Generic and useful, but only for those with existing archives
-------------------------------------------------------------
-o catherine - migrates packages from legacy locations to the pool
-o neve - initializes a projectb database from an exisiting archive
+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 ashley - dumps info in .katie files
-o julia - sync PostgreSQL users with system users
-o rene - check for obsolete or duplicated packages
-o rose - directory creation in the initial setup of an archive
-o tea - various sanity checks of the database and archive
-o natalie - manpiulates/list override entries
-o heidi - removes/adds/lists package(s) from/to/for a suite
-o saffron - produces various statistics
-o rosamund - checks for users with no packages in the archive
+o dak dot-dak-decode - dumps info in .dak files
+o dak import-users-from-passwd - sync PostgreSQL users with system users
+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-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
Semi-generic
------------
To generate less-used indices files:
-o charisma - generates Maintainers file
-o denise - generates override.<foo> files
+o dak make-maintainers - generates Maintainers file used by, e.g. debbugs
+o dak make-overrides - generates override.<foo> files
Mostly Debian(.org) specific
----------------------------
-o amber - wrapper for Debian security team
-o halle - removes obsolete .changes files from proposed-updates
-o jeri - basic dependency checking for proposed-updates
-o emilie - syncs fingerprint and uid information with a debian.org LDAP DB
-o lauren - manually reject packages from proposed-updates
+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 alyson - currently only initializes a DB from a katie.conf config file
-o andrea - looks for version descrepancies that shouldn't exist in many
- archives
-o cindy - override cruft checker that doesn't work well with New Incoming
+o dak init-db - currently only initializes a DB from a dak.conf config file
+o dak compare-suites - looks for version descrepancies that shouldn't exist in many
+ archives
+o dak check-overrides - override cruft checker that doesn't work well with New Incoming
Scripts invoked by other scripts
--------------------------------
-o fernanda - invoked by lisa to "check" NEW packages
-o claire - invoked by catherine to determine packages still in legacy locations
-o katie - common code used by lisa, jennifer, kelly and others
+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 katie.conf and apt.conf files. katie looks for those
- config files in /etc/katie/. /etc/katie/katie.conf can define
- alternative configuration files with Config::host::KatieConfig and
+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 Create a PostgreSQL database on the host given in katie.conf's DB::Host
+o Create a PostgreSQL database on the host given in dak.conf's DB::Host
with the name specified in DB::Name.
-o Run rose: this will create all directories which are specified in
- katie.conf and apt.conf.
+o Run 'dak init-dirs': this will create all directories which are specified in
+ dak.conf and apt.conf.
o If you have an existing archive:
- * Run neve
+ * Run 'dak init-archive'
otherwise:
* Create the table structure. init_pool.sql contains all SQL statements
which are needed for this. After changing all occurences of "projectb"
to the name of your database (as defined in DB::Name) you can run:
psql <DB::Name> < init_pool.sql
- * Run alyson: it will populate your database with the values from
- katie.conf and apt.conf.
+ * Run 'dak init-db': it will populate your database with the values from
+ dak.conf and apt.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.
[NB: I use this as a thought record/scribble, not everything on here
makes sense and/or is actually ever going to get done, so IIWY I
- wouldn't use it as gospel for the future of katie or as a TODO
+ wouldn't use it as gospel for the future of dak or as a TODO
list for random hacking.]
================================================================================
Others
------
- o cindy should remove the src-only override when a binary+source override
- exists
+ o 'dak check-overrides' should remove the src-only override when a
+ binary+source override exists
o reject on > or < in a version constraint
-23:07 < aba> elmo: and, how about enhancing rene to spot half-dropped
+23:07 < aba> elmo: and, how about enhancing 'dak cruft-report' to spot half-dropped
binaries on one arch (i.e. package used to build A and B, but B is
no longer built on some archs)?
o ensure .dsc section/prio match .changes section/prio
- o rhona's kind of crap when asked to remove a lot of files (e.g. 2k
- or so).
+ o 'dak clean-suites' performance is kind of crap when asked to
+ remove a lot of files (e.g. 2k or so).
o we don't handle the case where an identical orig.tar.gz is
- mentioned in the .changes, but not in unchecked; but should we
- care?
+ mentioned in the .changes, but not in unchecked; but should we
+ care?
- o madison could do better sanity checking for -g/-G (e.g. not more
- than one suite, etc.)
+ o 'dak ls' could do better sanity checking for -g/-G (e.g. not more
+ than one suite, etc.)
o use python2.2-tarfile (once it's in stable?) to check orig.tar.gz
- timestamps too.
+ timestamps too.
o need to decide on whether we're tying for most errors at once.. if
so (probably) then make sure code doesn't assume variables exist and
either way do something about checking error code of check_dsc and
later functions so we skip later checks if they're bailing.
- o the .katie stuff is fundamentally braindamaged, it's not versioned
+ o the .dak stuff is fundamentally braindamaged, it's not versioned
so there's no way to change the format, yay me. need to fix.
probably by putting a version var as the first thing and checking
that.. auto-upgrade at least from original format would be good.
o reject sparc64 binaries in a non '*64*' package.
- o katie.py(source_exists): a) we take arguments as parameters that
- we could figure out for ourselves (we're part of the Katie class
+ o queue.py(source_exists): a) we take arguments as parameters that
+ we could figure out for ourselves (we're part of the Upload class
after all), b) we have this 3rd argument which defaults to "any"
but could in fact be dropped since no one uses it like that.
- o jennifer: doesn't handle bin-only NMUs of stuff still in NEW,
- BYHAND or ACCEPTED (but not the pool) - not a big deal, upload can
- be retried once the source is in the archive, but still.
+ o 'dak process-unchecked': doesn't handle bin-only NMUs of stuff
+ still in NEW, BYHAND or ACCEPTED (but not the pool) - not a big
+ deal, upload can be retried once the source is in the archive, but
+ still.
o security global mail overrides should special case buildd stuff so
- that buildds get ACCEPTED mails (or maybe amber (?)), that way
+ that buildds get ACCEPTED mails (or maybe 'dak security-install' (?)), that way
upload-security doesn't grow boundlessly.
- o amber should upload sourceful packages first, otherwise with big
- packages (e.g. X) and esp. when source is !i386, half the arches
- can be uploaded without source, get copied into queue/unaccepted
- and promptly rejected.
+ o 'dak security-install' should upload sourceful packages first,
+ otherwise with big packages (e.g. X) and esp. when source is !i386,
+ half the arches can be uploaded without source, get copied into
+ queue/unaccepted and promptly rejected.
- o rene's NVIU check doesn't catch cases where source package changed
- name, should check binaries too. [debian-devel@l.d.o, 2004-02-03]
+ o 'dak cruft-report's NVIU check doesn't catch cases where source
+ package changed name, should check binaries
+ too. [debian-devel@l.d.o, 2004-02-03]
- o cnf[melanie::logfile] is misnamed...
+ o cnf[Rm::logfile] is misnamed...
<aj> i'd be kinda inclined to go with insisting the .changes file take
the form ---- BEGIN PGP MESSAGE --- <non -- BEGIN/END lines> --
BEGIN PGP SIG -- END PGP MESSAGE -- with no lines before or after,
and rejecting .changes that didn't match that
- o rene should check for source packages not building any binaries
+ o 'dak cruft-report' should check for source packages not building any binaries
- o heidi should have a diff mode that accepts diff output!
+ o 'dak control-suite' should have a diff mode that accepts diff output!
- o halle doesn't deal with melanie'd packages, partial replacements
- etc. and more.
+ o 'dak clean-proposed-updates' doesn't deal with 'dak rm'-d
+ packages, partial replacements etc. and more.
- o lauren, the tramp, blindly deletes with no check that the delete
- failed which it might well given we only look for package/version,
- not package/version _in p-u_. duh.
+ o 'dak reject-proposed-updates' blindly deletes with no check that
+ the delete failed which it might well given we only look for
+ package/version, not package/version _in p-u_. duh.
- o melanie should remove obsolete changes when removing from p-u, or
- at least warn. or halle should handle it.
+ o 'dak rm' should remove obsolete changes when removing from p-u, or
+ at least warn. or 'dak reject-proposed-updates' should handle it.
o need a testsuite _badly_
- o lisa should have an Bitch-Then-Accept option
-
- o jennifer crashes if run as a user in -n mode when orig.tar.gz is
- in queue/new...
+ o 'dak process-unchecked' crashes if run as a user in -n mode when
+ orig.tar.gz is in queue/new...
<elmo_home> [<random>maybe I should reject debian packages with a non-Debian origin or bugs field</>]
<Kamion> [<random>agreed; dunno what origin does but non-Debian bugs fields would be bad]
- o rhona should make use of select..except select, temporary tables
- etc. rather than looping and calling SQL every time so we can do
- suite removal sanely (see potato-removal document)
+ o 'dak clean-suites' should make use of select..except select, temporary tables
+ etc. rather than looping and calling SQL every time so we can do
+ suite removal sanely (see potato-removal document)
- o melanie will happily include packages in the Cc list that aren't
+ o 'dak rm' will happily include packages in the Cc list that aren't
being removed...
- o melanie doesn't remove udebs when removing the source they build from
+ o 'dak rm' doesn't remove udebs when removing the source they build from
o check_dsc_against_db's "delete an entry from files while you're
not looking" habit is Evil and Bad.
- o lisa allows you to edit the section and change the component, but
- really shouldn't.
+ o 'dak process-new' allows you to edit the section and change the
+ component, but really shouldn't.
- o melanie needs to, when not sending bug close mails, promote Cc: to
+ o 'dak rm' needs to, when not sending bug close mails, promote Cc: to
To: and send the mail anyways.
o the lockfile (Archive_Maintenance_In_Progress) should probably be in a conf file
- o madison should cross-check the b.source field and if it's not null
- and s.name linked from it != the source given in
+ o 'dak ls' should cross-check the b.source field and if it's not
+ null and s.name linked from it != the source given in
-S/--source-and-binary ignore.
- o lauren sucks; she should a) only spam d-i for sourceful
- rejections, b) sort stuff so she rejects sourceful stuff first. the
- non-sourceful should probably get a form mail, c) automate the
- non-sourceful stuff (see b).
+ o 'dak reject-proposed-updates' sucks; it should a) only spam d-i
+ for sourceful rejections, b) sort stuff so it rejects sourceful
+ stuff first. the non-sourceful should probably get a form mail, c)
+ automate the non-sourceful stuff (see b).
- o jennifer should do q-d stuff for faster AA [ryan]
+ o 'dak process-unchecked' should do q-d stuff for faster AA [ryan]
o split the morgue into source and binary so binaries can be purged first!
o use postgres 7.2's built-in stat features to figure out how indices are used etc.
- o neve shouldn't be using location, she should run down suites instead
+ o 'dak init-archive' shouldn't be using location, it should run down suites instead
- o halle needs to know about udebs
+ o 'dak clean-proposed-updates' needs to know about udebs
- o by default hamstring katie's mail sending so that she won't send
- anything until someone edits a script; she's been used far too
+ o by default hamstring dak's mail sending so that it won't send
+ anything until someone edits a script; it's been used far too
much to send spam atm :(
- o $ftpdir/indices isn't created by rose because it's not in katie.conf
+ o $ftpdir/indices isn't created by 'dak init-dir' because it's not in dak.conf
o sanity check depends/recommends/suggests too? in fact for any
empty field?
-[minor] kelly's copychanges, copykatie handling sucks, the per-suite
- thing is static for all packages, so work out in advance dummy.
+[minor] 'dak process-accepted's copychanges, copydotdak handling
+ sucks, the per-suite thing is static for all packages, so work out
+ in advance dummy.
-[madison] # filenames ?
-[madison] # maintainer, component, install date (source only?), fingerprint?
+[dak ls] # filenames ?
+[dak ls] # maintainer, component, install date (source only?), fingerprint?
o UrgencyLog stuff should minimize it's bombing out(?)
o Log stuff should open the log file
- o helena should footnote the actual notes, and also * the versions
- with notes so we can see new versions since being noted...
+ o 'dak queue-report' should footnote the actual notes, and also *
+ the versions with notes so we can see new versions since being
+ noted...
- o helena should have alternative sorting options, including reverse
+ o 'dak queue-report' should have alternative sorting options, including reverse
and without or without differentiaion.
- o julia should sync debadmin and ftpmaster (?)
+ o 'dak import-users-from-passwd' should sync debadmin and ftpmaster (?)
o <drow> Can't read file.:
- /org/security.debian.org/queue/accepted/accepted/apache-perl_1.3.9-14.1-1.21.20000309-1_sparc.katie.
+ /org/security.debian.org/queue/accepted/accepted/apache-perl_1.3.9-14.1-1.21.20000309-1_sparc.dak.
You assume that the filenames are relative to accepted/, might want
to doc or fix that.
were pulled out in -2, and we end up with no orig in the archive
:(
- o SecurityQueueBuild doesn't handle the case of foo_3.3woody1
- with a new .orig.tar.gz followed by a foo_3.3potato1 with the same
- .orig.tar.gz; jennifer sees it and copes, but the AA code doesn't
- and can't really easily know so the potato AA dir is left with no
- .orig.tar.gz copy. doh.
+ o SecurityQueueBuild doesn't handle the case of foo_3.3woody1 with a
+ new .orig.tar.gz followed by a foo_3.3potato1 with the same
+ .orig.tar.gz; 'dak process-unchecked' sees it and copes, but the AA
+ code doesn't and can't really easily know so the potato AA dir is
+ left with no .orig.tar.gz copy. doh.
o orig.tar.gz in accepted not handled properly (?)
- o amber doesn't include .orig.tar.gz but it should
+ o 'dak security-install' doesn't include .orig.tar.gz but it should
o permissions (paranoia, group write, etc.) configurability and overhaul
- o remember duplicate copyrights in lisaand skip them, per package
+ o remember duplicate copyrights in 'dak process-new' and skip them, per package
- o <M>ove option for lisa byhand proecessing
+ o <M>ove option for 'dak process-new' byhand proecessing
- o rene could do with overrides
+ o 'dak cruft-report' could do with overrides
- o db_access.get_location_id should handle the lack of archive_id properly
+ o database.get_location_id should handle the lack of archive_id properly
o the whole versioncmp thing should be documented
- o lisa doesn't do the right thing with -2 and -1 uploads, as you can
+ o 'dak process-new' doesn't do the right thing with -2 and -1 uploads, as you can
end up with the .orig.tar.gz not in the pool
- o lisa exits if you check twice (aj)
+ o 'dak process-new' exits if you check twice (aj)
- o lisa doesn't trap signals from fernanda properly
+ o 'dak process-new' doesn't trap signals from 'dak examine-package' properly
o queued and/or perl on sparc stable sucks - reimplement it.
o aj's bin nmu changes
- o Lisa:
+ o 'dak process-new':
* priority >> optional
* arch != {any,all}
- * build-depends wrong (via andrea)
+ * build-depends wrong (via 'dak compare-suites')
* suid
* conflicts
* notification/stats to admin daily
- o trap fernanda exiting
+ o trap 'dak examine-package' exiting
o distinguish binary only versus others (neuro)
o cache changes parsed from ordering (careful tho: would be caching
.changes from world writable incoming, not holding)
- o katie doesn't recognise binonlyNMUs correctly in terms of telling
+ 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.
- o Fix BTS vs. katie sync issues by queueing(via BSMTP) BTS mail so
+ o Fix BTS vs. dak sync issues by queueing(via BSMTP) BTS mail so
that it can be released on deman (e.g. ETRN to exim).
o maintainers file needs overrides
[ change override.maintainer to override.maintainer-from +
override.maintainer-to and have them reference the maintainers
- table. Then fix charisma to use them and write some scripting
+ table. Then fix 'dak make-maintainers' to use them and write some scripting
to handle the Santiago situation. ]
o Validate Depends (et al.) [it should match \(\s*(<<|<|<=|=|>=|>|>>)\s*<VERSIONREGEXP>\)]
o morgue needs auto-cleaning (?)
- o saffron: two modes, all included, seperate
- o saffron: add non-US
- o saffron: add ability to control components, architectures, archives, suites
- o saffron: add key to expand header
+ o dak stats: two modes, all included, seperate
+ 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 change utils.copy to try rename() first
o [hard, long term] unchecked -> accepted should go into the db, not
- a suite, but similar. this would allow katie to get even faster,
- make madison more useful, decomplexify specialacceptedautobuild
+ a suite, but similar. this would allow dak to get even faster,
+ make 'dak ls' more useful, decomplexify specialacceptedautobuild
and generally be more sane. may even be helpful to have e.g. new
in the DB, so that we avoid corner cases like the .orig.tar.gz
disappearing 'cos the package has been entirely removed but was
still on stayofexecution when it entered new.
- o Logging [mostly done] (todo: rhona (hard), .. ?)
+ o Logging [mostly done] (todo: 'dak clean-suites' (hard), .. ?)
- o jennifer: the tar extractor class doesn't need to be redone for each package
+ o 'dak process-unchecked': the tar extractor class doesn't need to be redone for each package
o reverse of source-must-exist; i.e. binary-for-source-must-not-exist
- o REJECT reminders in shania.
- o fernanda should check for conflicts and warn about them visavis priority [rmurray]
+ o REJECT reminders in 'dak clean-queues'.
+ o 'dak examine-package' should check for conflicts and warn about them visavis priority [rmurray]
o store a list of removed/files versions; also compare against them.
[but be careful about scalability]
- o fernanda: print_copyright should be a lot more intelligent
+ o dak examine-package: print_copyright should be a lot more intelligent
@ handle copyright.gz
@ handle copyright.ja and copyright
@ handle (detect at least) symlinks to another package's doc directory
o [Hard] Need to merge non-non-US and non-US DBs.
- o experimental needs to auto clean (relative to unstable) [partial: rene warns about this]
+ o experimental needs to auto clean (relative to unstable) [partial:
+ 'dak cruft-report' warns about this]
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 Improve andrea.
+ o Improve 'dak compare-suites'.
o Need to optimize all the queries by using EXAMINE and building some INDEXs.
[postgresql 7.2 will help here]
o Need to enclose all the setting SQL stuff in transactions (mostly done).
- o Need to finish alyson (a way to sync katie.conf and the DB)
+ o Need to finish 'dak init-db' (a way to sync dak.conf and the DB)
o Need the ability to rebuild all other tables from dists _or_ pools (in the event of disaster) (?)
o Make the --help and --version options do stuff for all scripts
- o charisma can't handle whitespace-only lines (for the moment, this is feature)
+ o 'dak make-maintainers' can't handle whitespace-only lines (for the moment, this is feature)
o generic way of saying isabinary and isadsc. (?)
@ backup of report (?)
@ backup of changes.tgz (?)
- o --help doesn't work without /etc/katie/katie.conf (or similar) at
+ o --help doesn't work without /etc/dak/dak.conf (or similar) at
least existing.
- o rename andrea (clashes with existing andrea)...
+ o rename 'dak compare-suites' (clashes with existing 'dak compare-suites')...
* Harder:
- o interrupting of stracing jennifer causes exceptions errors from apt_inst calls
+ o interrupting of stracing 'dak process-unchecked' causes exceptions errors from apt_inst calls
o dependency checking (esp. stable) (partially done)
o override checks sucks; it needs to track changes made by the
maintainer and pass them onto ftpmaster instead of warning the
maintainer.
o need to do proper rfc822 escaping of from lines (as opposed to s/\.//g)
- o Revisit linking of binary->source in install() in katie.
+ o Revisit linking of binary->source in install() in dak.
o Fix component handling in overrides (aj)
o Fix lack of entires in source overrides (aj)
o direport misreports things as section 'devel' (? we don't use direport)
o check linking of .tar.gz's to .dsc's.. see proftpd 1.2.1 as an example
o archive needs md5sum'ed regularly, but takes too long to do all
in one go; make progressive or weekly.
- o katie/jenna/rhona/whatever needs to clear out .changes
- files from p-u when removing stuff superseded by newer versions.
- [but for now we have halle]
+ o something needs to clear out .changes files from p-u when
+ removing stuff superseded by newer versions. [but for now we have
+ 'dak clean-proposed-updates']
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 suite mapping and component mapping are parsed per changes file,
they should probably be stored in a dictionary created at startup.
o don't stat/md5sum files you have entries for in the DB, moron
- boy (Katie.check_source_blah_blah)
- o promote changes["changes"] to mandatory in katie.py(dump_vars)
- after a month or so (or all .katie files contain in the queue
+ boy (Dak.check_source_blah_blah)
+ o promote changes["changes"] to mandatory in dak.py(dump_vars)
+ after a month or so (or all .dak files contain in the queue
contain it).
- o melanie should behave better with -a and without -b; see
+ o 'dak rm' should behave better with -a and without -b; see
gcc-defaults removal for an example.
o Reject on misconfigured kernel-package uploads
o utils.extract_component_from_section: main/utils -> main/utils, main rather than utils, main
- o Fix jennier to warn if run when not in incoming or p-u
- o katie should validate multi-suite uploads; only possible valid one
+ o Fix 'dak process-unchecked' to warn if run when not in incoming or p-u
+ o dak should validate multi-suite uploads; only possible valid one
is "stable unstable"
o cron.daily* should change umask (aj sucks)
- o Rene doesn't look at debian-installer but should.
- o Rene needs to check for binary-less source packages.
- o Rene could accept a suite argument (?)
+ o 'dak cruft-report' doesn't look at debian-installer but should.
+ o 'dak cruft-report' needs to check for binary-less source packages.
+ o 'dak cruft-report' could accept a suite argument (?)
o byhand stuff should send notification
- o catherine should udpate db; move files, not the other way around [neuro]
- o melanie should update the stable changelog [joey]
+ o 'dak poolize' should udpate db; move files, not the other way around [neuro]
+ o 'dak rm' should update the stable changelog [joey]
o update tagdb.dia
* Bizzare/uncertain:
o drop rather dubious currval stuff (?)
o rationalize os.path.join() usage
- o Rene also doesn't seem to warn about missing binary packages (??)
+ o 'dak cruft-report' also doesn't seem to warn about missing binary packages (??)
o logging: hostname + pid ?
- o ANAIS should be done in katie (?)
- o Add an 'add' ability to melanie (? separate prog maybe)
+ o ANAIS should be done in dak (?)
+ o Add an 'add' ability to 'dak rm' (? separate prog maybe)
o Replicate old dinstall report stuff (? needed ?)
o Handle the case of 1:1.1 which would overwrite 1.1 (?)
- o maybe drop -r/--regex in madison, make it the default and
+ o maybe drop -r/--regex in 'dak ls', make it the default and
implement -e/--exact (a la joey's "elmo")
o dsc files are not checked for existence/perms (only an issue if
they're in the .dsc, but not the .changes.. possible?)
================================================================================
- --help manpage
+ --help manpage
-----------------------------------------------------------------------------
-alyson X
-amber X
-andrea X
-ashley X
-catherine X X
-charisma X X
-cindy X X
-claire X
-denise X
-fernanda X
-halle X
-heidi X X
-helena X
-jenna X
-jennifer X
-jeri X
-julia X X
-kelly X X
-lisa X X
-madison X X
-melanie X X
-natalie X X
-neve X
-rene X
-rose X
-rhona X X
-saffron X
-shania X
-tea X
-ziyi X
+check-archive X
+check-overrides X X
+check-proposed-updates X
+clean-proposed-updates X
+clean-queues X
+clean-suites X X
+compare-suites X
+control-overrides X X
+control-suite X X
+cruft-report X
+decode-dot-dak X
+examine-package X
+generate-releases X
+import-archive X
+import-users-from-passwd X X
+init-db X
+init-dirs X
+ls X X
+make-maintainers X X
+make-overrides X
+make-suite-file-list X
+poolize X X
+process-accepted X X
+process-new X X
+process-unchecked X
+queue-report X
+rm X X
+security-install X
+stats X
+symlink-dists X
================================================================================
projects / dak.git / commitdiff