From de64fdc4737d7ff6b1813e8df6cb0ef46bc86dc9 Mon Sep 17 00:00:00 2001 From: Joerg Jaspert Date: Fri, 30 Oct 2009 23:41:29 +0100 Subject: [PATCH] remove a manpage. closes: 540170 remove a manpage Signed-off-by: Joerg Jaspert --- docs/manpages/check-overrides.1.sgml | 61 ---------------------------- 1 file changed, 61 deletions(-) delete mode 100644 docs/manpages/check-overrides.1.sgml diff --git a/docs/manpages/check-overrides.1.sgml b/docs/manpages/check-overrides.1.sgml deleted file mode 100644 index a4a7c146..00000000 --- a/docs/manpages/check-overrides.1.sgml +++ /dev/null @@ -1,61 +0,0 @@ - - -%dakent; - -]> - - - &dak-docinfo; - - - dak_check-overrides - 1 - - - - - dak check-overrides - Utility to alter or display the contents of a suite - - - - - - dak check-overrides - - - - - Description</> - <para> - <command>dak check-overrides</command> is a cruft checker for overrides. - </PARA> - </REFSECT1> - - <RefSect1><Title>Options</> - - <VariableList> - <VarListEntry><term><option>-h/--help</option></> - <ListItem> - <Para>Show help and then exit.</PARA> - </LISTITEM> - </VarListEntry> - - </VariableList> - </RefSect1> - - <RefSect1><Title>Notes</> - - <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>dak check-overrides</command> returns zero on normal operation, non-zero on error. - </PARA> - </RefSect1> - - &manauthor; - -</refentry> -- 2.39.2