<command>cindy</command> is a cruft checker for overrides.
<command>dak check-overrides</command> is a cruft checker for overrides.
</PARA>
</REFSECT1>
...
...
@@ -48,11 +48,11 @@
<RefSect1><Title>Notes</>
<Para>cindy is not a good idea with New Incoming as she doesn't take into account queue/accepted. You can minimize the impact of this by running her immediately after kelly but that's still racy because lisa doesn't lock with elly. A better long term fix is the evil plan for accepted to be in the DB.</>
<Para>dak check-overrides is not a good idea with New Incoming as it doesn't take into account queue/accepted. You can minimize the impact of this by running it immediately after 'dak process-accepted' but that's still racy because 'dak process-new' doesn't lock with 'dak process-accepted'. A better long term fix is the evil plan for accepted to be in the DB.</>
<RefSect1><Title>Diagnostics</>
<para>
<command>cindy</command> returns zero on normal operation, non-zero on error.
<command>dak check-overrides</command> returns zero on normal operation, non-zero on error.
<command>rhona</command> is a utility clean out old packages. It will clean out any binary packages not referenced by a suite and any source packages not referenced by a suite and not referenced by any binary packages. Cleaning is not actual deletion, but rather, removal of packages from the pool to a 'morgue' directory. The 'morgue' directory is split into dated sub-directories to keep things sane in big archives.
<command>dak clean-suites</command> is a utility clean out old packages. It will clean out any binary packages not referenced by a suite and any source packages not referenced by a suite and not referenced by any binary packages. Cleaning is not actual deletion, but rather, removal of packages from the pool to a 'morgue' directory. The 'morgue' directory is split into dated sub-directories to keep things sane in big archives.
</PARA>
</REFSECT1>
...
...
@@ -54,16 +54,16 @@
<refsect1>
<title>Configuration</title>
<para><command>rhona</command> uses katie's configuration file. It follows the typical ISC configuration format as seen in ISC tools like bind 8 and dhcpd. Apart from being able to alter the defaults for command line options, the following configuration items are used:</para>
<para><command>dak clean-suites</command> uses dak's configuration file. It follows the typical ISC configuration format as seen in ISC tools like bind 8 and dhcpd. Apart from being able to alter the defaults for command line options, the following configuration items are used:</para>
<variablelist>
<varlistentry>
<term>Rhona::StayOfExecution</term>
<term>Clean-Suites::StayOfExecution</term>
<listitem>
<para>This is the number of seconds unreferenced packages are left before being cleaned.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Rhona::MorgueSubDir</term>
<term>Clean-Suites::MorgueSubDir</term>
<listitem>
<para>If not blank, this is the subdirectory in the morgue used to hold removed packages.</para>
</listitem>
...
...
@@ -73,7 +73,7 @@
<RefSect1><Title>Diagnostics</>
<para>
<command>rhona</command> returns zero on normal operation, non-zero on error.
<command>dak clean-suites</command> returns zero on normal operation, non-zero on error.
<command>heidi</command> is a utility to alter or display the contents of a suite. Input for alterations is taken either from filename(s) supplied or stdin. The format for both input and output is lines each with a whitespace separated list of: <literal>package</literal>, <literal>version</literal> and <literal>architecture</literal>.
<command>dak control-suite</command> is a utility to alter or display the contents of a suite. Input for alterations is taken either from filename(s) supplied or stdin. The format for both input and output is lines each with a whitespace separated list of: <literal>package</literal>, <literal>version</literal> and <literal>architecture</literal>.
</PARA>
</REFSECT1>
...
...
@@ -73,7 +73,7 @@
<RefSect1><Title>Diagnostics</>
<para>
<command>heidi</command> returns zero on normal operation, non-zero on error.
<command>dak control-suite</command> returns zero on normal operation, non-zero on error.
<command>julia</command> is a utility to sync PostgreSQL's user database with the system's users. It is designed to allow the use of 'peer sameuser' authentication. It simply adds any users in the password file into PostgreSQL's pg_user table if they are already not there. It will also warn you about users who are in the pg_user table but not in the password file.
<command>dak import-users-from-passwd</command> is a utility to sync PostgreSQL's user database with the system's users. It is designed to allow the use of 'peer sameuser' authentication. It simply adds any users in the password file into PostgreSQL's pg_user table if they are already not there. It will also warn you about users who are in the pg_user table but not in the password file.
</PARA>
</REFSECT1>
...
...
@@ -66,16 +66,16 @@
<refsect1>
<title>Configuration</title>
<para><command>julia</command> uses katie's configuration file. It follows the typical ISC configuration format as seen in ISC tools like bind 8 and dhcpd. Apart from being able to alter the defaults for command line options, the following configuration items are used:</para>
<para><command>dak import-users-from-passwd</command> uses dak's configuration file. It follows the typical ISC configuration format as seen in ISC tools like bind 8 and dhcpd. Apart from being able to alter the defaults for command line options, the following configuration items are used:</para>
<variablelist>
<varlistentry>
<term>Julia::ValidGID</term>
<term>Import-Users-From-Passwd::ValidGID</term>
<listitem>
<para>Each user's primary GID is compared with this, if it's not blank. If they match, the user will be processed, if they don't, the user will be skipped.</para>
The input format of extra files can either be in this form or in the old style which is similar, but lacking the version number, i.e.:
<literallayout>package maintainer</literallayout>
Charisma will auto-detect the type of layout of the extra file. If the extra file is in the old style format the records in it are assumed to supersed any that were seen earlier (i.e. either from earlier extra files or generated from the SQL).
dak Make-Maintainers will auto-detect the type of layout of the extra file. If the extra file is in the old style format the records in it are assumed to supersed any that were seen earlier (i.e. either from earlier extra files or generated from the SQL).
</Para>
<para>
Charisma determines the maintainer of a package by comparing suite priority (see 'Configuration') and then version number.
dak Make-Maintainers determines the maintainer of a package by comparing suite priority (see 'Configuration') and then version number.
</PARA>
</REFSECT1>
...
...
@@ -56,12 +56,12 @@
<refsect1>
<title>Configuration</title>
<para><command>charisma</command> uses katie's configuration file. It follows the typical ISC configuration format as seen in ISC tools like bind 8 and dhcpd. Apart from being able to alter the defaults for command line options, the following configuration items are used:</para>
<para><command>dak make-maintainers</command> uses dak's configuration file. It follows the typical ISC configuration format as seen in ISC tools like bind 8 and dhcpd. Apart from being able to alter the defaults for command line options, the following configuration items are used:</para>
<variablelist>
<varlistentry>
<term>Suite::<SUITE>::Priority</term>
<listitem>
<para>Suite priority overrides the version checks charisma does. A package in higher priority suite overrides versions in lower priority suites even if the version number in the higher priority suite is older.</para>
<para>Suite priority overrides the version checks dak make-maintainers does. A package in higher priority suite overrides versions in lower priority suites even if the version number in the higher priority suite is older.</para>
</listitem>
</varlistentry>
</variablelist>
...
...
@@ -76,7 +76,7 @@
<RefSect1><Title>Diagnostics</>
<para>
<command>charisma</command> returns zero on normal operation, non-zero on error.
<command>dak make-maintainers</command> returns zero on normal operation, non-zero on error.
<command>alicia</command> when invoked with only a package name will tell you what section and priority the given package has.
<command>dak override</command> when invoked with only a package name will tell you what section and priority the given package has.
</PARA>
<para>
<command>alicia</command> when invoked with a package and one or two other values will set the section and/or priority to the values given. You may use a single period ('.') to represent "do not change" or you can ommit the value you do not want to change.
<command>dak override</command> when invoked with a package and one or two other values will set the section and/or priority to the values given. You may use a single period ('.') to represent "do not change" or you can ommit the value you do not want to change.
</PARA>
</RefSect1>
<RefSect1><Title>Notes</>
<Para>alicia essentially lets you do what natalie does only on the microscopic scale rather than the macroscopic scale of natalie. Use with care.</>
<Para><command>dak override</command> essentially lets you do what <command>dak control-overrides</command> does only on the microscopic scale rather than the macroscopic scale of <command>dak control-overrides</command>. Use with care.</>
<RefSect1><Title>Diagnostics</>
<para>
<command>alicia</command> returns zero on normal operation, non-zero on error.
<command>dak override</command> returns zero on normal operation, non-zero on error.
<command>kelly</command> is the program which installs packages from the accepted directory into the distribution.
<command>dak process-accepted</command> is the program which installs packages from the accepted directory into the distribution.
</PARA></REFSECT1>
<RefSect1><Title>Options</>
...
...
@@ -86,13 +86,13 @@
<RefSect1><Title>Diagnostics</>
<para>
<command>kelly</command> returns zero on normal operation, non-zero on error.
<command>dak process-accepted</command> returns zero on normal operation, non-zero on error.
</PARA>
</RefSect1>
<refsect1>
<title>Acknowledgements</title>
<para>kelly is based very heavily on dinstall, written by Guy Maor <email>maor@debian.org</email>; in fact it started out life as a dinstall clone.</para>
<para>dak process-accepted is based very heavily on dinstall, written by Guy Maor <email>maor@debian.org</email>; in fact it started out life as a dinstall clone.</para>
<command>melanie</command> is the command line tool to add and remove package sets from suites with enforced logging, optional bug closing and override updates.
<command>dak rm</command> is the command line tool to add and remove package sets from suites with enforced logging, optional bug closing and override updates.
<Para>Check the reverse dependencies (and build-dependencies) of the packages that are to be removed and warn if anything will break.</literal></PARA>
<Para>Check the reverse dependencies (and build-dependencies) of the packages that are to be removed and warn if anything will break.</PARA>
</LISTITEM>
</VarListEntry>
...
...
@@ -125,7 +125,7 @@
<itemizedlist>
<listitem>
<para>Source + Binaries. (default)</para>
<para>In this mode <command>melanie</command> will assume each of the package(s) passed as arguments are source packages and will also remove any binary packages built from these source packages.</para>
<para>In this mode <command>dak rm</command> will assume each of the package(s) passed as arguments are source packages and will also remove any binary packages built from these source packages.</para>
</listitem>
<listitem>
<para>Binary only.</para>
...
...
@@ -141,18 +141,18 @@
<refsect1>
<title>Configuration</title>
<para><command>melanie</command> uses katie's configuration file. It follows the typical ISC configuration format as seen in ISC tools like bind 8 and dhcpd. Apart from being able to alter the defaults for command line options, the following configuration items are used:</para>
<para><command>dak rm</command> uses dak's configuration file. It follows the typical ISC configuration format as seen in ISC tools like bind 8 and dhcpd. Apart from being able to alter the defaults for command line options, the following configuration items are used:</para>
<variablelist>
<varlistentry>
<term>Melanie::MyEmailAddress</term>
<term>Rm::MyEmailAddress</term>
<listitem>
<para>This is used as the From: line for bug closing mails as per the -d/--done command line switch. It, obviously, must be a RFC-822 valid email address.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Melanie::LogFile</term>
<term>Rm::LogFile</term>
<listitem>
<para>This is the (absolute) file name of the logfile that melanie unconditionally writes too. This can not be empty or an invalid file.</para>
<para>This is the (absolute) file name of the logfile that dak rm unconditionally writes too. This can not be empty or an invalid file.</para>
</listitem>
</varlistentry>
</variablelist>
...
...
@@ -163,7 +163,7 @@
<para>The first example is of a source+binaries package removal.</para>
<informalexample>
<literallayout>
troup@auric| ~ $melanie -d 68136 -m "Requested by tbm@; confirmed with maintainer. Superseded by libgmp2" gmp1
$ dak rm -d 68136 -m "Requested by tbm@; confirmed with maintainer. Superseded by libgmp2" gmp1
Working... done.
Will remove the following packages from unstable:
...
...
@@ -177,13 +177,13 @@ Requested by tbm@; confirmed with maintainer. Superseded by libgmp2
Continue (y/N)? y
Deleting... done.
troup@auric| ~ $
$
</literallayout>
</informalexample>
<para>The second example is of a binary-only multi-package removal.</para>
