Package: release.debian.org
Severity: normal
User: release.debian....@packages.debian.org
Usertags: unblock
Please unblock package duc
The duc tarball builds two Debian packages: duc and duc-nox.
The difference between version 1.4.3-1 (Testing) and
version 1.4.3-2 (Sid) is:
- the manpage for duc-nox is generated at build time.
(upstream manpage).
- I removed the manpage I made.
To do that I add a package on 'Depends' in debian/control and
edited debian/rules.
The debdiff is attached.
unblock duc/1.4.3-2
Regards,
Herbert
-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=pt_BR.utf8, LC_CTYPE=pt_BR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru duc-1.4.3/debian/changelog duc-1.4.3/debian/changelog
--- duc-1.4.3/debian/changelog 2017-01-13 11:03:20.000000000 -0200
+++ duc-1.4.3/debian/changelog 2017-02-01 17:28:00.000000000 -0200
@@ -1,3 +1,15 @@
+duc (1.4.3-2) unstable; urgency=medium
+
+ * debian/control:
+ - Add ruby-ronn to Build-Depends
+ * debian/duc-nox.manpages:
+ - Upstream manpage generated at build time.
+ * debian/man removed.
+ * debian/rules:
+ - generate duc-nox manpage
+
+ -- Herbert Parentes Fortes Neto <h...@debian.org> Wed, 01 Feb 2017 17:28:00
-0200
+
duc (1.4.3-1) unstable; urgency=low
* New upstream release.
diff -Nru duc-1.4.3/debian/control duc-1.4.3/debian/control
--- duc-1.4.3/debian/control 2016-11-05 12:24:07.000000000 -0200
+++ duc-1.4.3/debian/control 2017-02-01 17:28:00.000000000 -0200
@@ -8,6 +8,7 @@
libncursesw5-dev,
libpango1.0-dev,
libtokyocabinet-dev,
+ ruby-ronn,
txt2man
Standards-Version: 3.9.8
Homepage: http://duc.zevv.nl/
diff -Nru duc-1.4.3/debian/copyright duc-1.4.3/debian/copyright
--- duc-1.4.3/debian/copyright 2017-01-13 11:03:20.000000000 -0200
+++ duc-1.4.3/debian/copyright 2017-02-01 17:28:00.000000000 -0200
@@ -25,10 +25,6 @@
Copyright: 2015-2017 Herbert Parentes Fortes Neto <h...@debian.org>
License: GPL-2+
-Files: debian/man/genallman.sh
-Copyright: 2014 João Eriberto Mota Filho <eribe...@debian.org>
-License: BSD-3-clause or GPL-2+
-
License: GPL-2 or GPL-2+
This package is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
@@ -65,31 +61,6 @@
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-License: BSD-3-clause
- Redistribution and use in source and binary forms, with or without
- modification, are permitted provided that the following conditions
- are met:
- 1. Redistributions of source code must retain the above copyright
- notice, this list of conditions and the following disclaimer.
- 2. Redistributions in binary form must reproduce the above copyright
- notice, this list of conditions and the following disclaimer in the
- documentation and/or other materials provided with the distribution.
- 3. Neither the name of the copyright holder nor the names of contributors
- may be used to endorse or promote products derived from this software
- without specific prior written permission.
- .
- THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTOR(S) ``AS IS'' AND
- ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
- IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
- ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTOR(S) BE LIABLE
- FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
- DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
- OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
- HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
- LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
- OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
- SUCH DAMAGE.
-
License: other
The authors renounce all claim of copyright to this code and dedicate
this code to the public domain. In place of legal notice, here is
diff -Nru duc-1.4.3/debian/duc-nox.manpages duc-1.4.3/debian/duc-nox.manpages
--- duc-1.4.3/debian/duc-nox.manpages 2016-06-19 16:53:43.000000000 -0300
+++ duc-1.4.3/debian/duc-nox.manpages 2017-02-01 17:28:00.000000000 -0200
@@ -1 +1 @@
-debian/man/duc-nox.1
+debian/build-nox/doc/duc-nox.1
diff -Nru duc-1.4.3/debian/man/duc-nox.1 duc-1.4.3/debian/man/duc-nox.1
--- duc-1.4.3/debian/man/duc-nox.1 2017-01-13 11:03:20.000000000 -0200
+++ duc-1.4.3/debian/man/duc-nox.1 1969-12-31 21:00:00.000000000 -0300
@@ -1,508 +0,0 @@
-.TH duc-nox "1" "Jan 2017" "DUC-NOX 1.4.3" "high-performance disk usage
analyzer"
-.\" Text automatically generated by txt2man
-.SH NAME
-\fBduc\[hy]nox \- index, query and graph disk usage
-.SH SYNOPSIS
-.nf
-.fam C
- duc\[hy]nox <subcommand> [\fIoptions\fP]
-.fam T
-.fi
-.fam T
-.fi
-.SH DESCRIPTION
-Duc is a collection of tools for inspecting and visualizing disk usage.
-.PP
-Duc maintains an indexed database of accumulated sizes of directories of your
-file system, and allows you to query this database with some tools, or create
-graphs to show you where your bytes are.
-.PP
-Duc scales quite well, it has been tested on systems with more then 500 million
-files and several petabytes of storage.
-.SH USAGE
-Duc comes with a command line tool called `duc\[hy]nox`, which is used to
create,
-.TP
-.B
-maintain and query the disk usage database.
-run `duc\[hy]nox help` to get a list of
-available commands. `duc\[hy]nox help <subcommand>` describes the usage of a
specific
-subcommand. Run `duc\[hy]nox help \[hy]\[hy]all` for an extensive list of all
commands and
-their \fIoptions\fP.
-.PP
-Duc allows any option to be placed either on the command line or in a
-configuration file. Options on the command line are preceded by a
-double-leading-dash (`\[hy]\[hy]option`), some \fIoptions\fP have a
corresponding
-short option which can be used as well with a single leading dash. (`\[hy]o`)
-.PP
-At startup duc tries to read its configuration from three locations in this
-particular order: `/etc/ducrc`, `~/\.config/duc/ducrc`, `~/.ducrc` and
`./.ducrc`.
-.PP
-A configuration file consists of sections and parameters. The section names
-correspond to the duc\[hy]nox subcommands for which the parameters in that
-section apply. A section begins with the name of the section in square
-brackets and continues until the next section begins.Sections contain
-parameters, one per line, which consist of a single option name for boolean
-flags, or a option name and a value for \fIoptions\fP which take a value. See
the
-EXAMPLES section for an example of the configuration file format.
-.SH CREATING THE INDEX
-Duc needs an index file of the file system before it is able to show any
-.TP
-.B
-information.
-To create the index, run the `duc\[hy]nox index` command. For
-example, to create an index of your home directory run `duc\[hy]nox index ~`
-.PP
-.nf
-.fam C
- $ duc\[hy]nox index /usr
- Skipping lost+found: Permission denied
- Indexed 333823 files and 48200 directories, (35.0GB total)
- in 1 seconds
-
-.fam T
-.fi
-The default location of the database is `$HOME/.duc.db`. To use a different
-database location, use the DUC_DATABASE environment variable or specify the
-database location with the \[hy]\[hy]database argument.
-.PP
-You can run `duc\[hy] index` at any time later to rebuild the index.
-.PP
-By default Duc indexes all directories it encounters during file system
-traversal, including special file systems like /proc and /sys, and
-network file systems like NFS or Samba mounts. There are a few \fIoptions\fP to
-select what parts of your filesystem you want to include or exclude from the
-scan, check the documentation below for \[hy]\[hy]one\[hy]file\[hy]system,
-\[hy]\[hy]exclude, \[hy]\[hy]fs\[hy]exclude and \[hy]\[hy]fs\[hy]include for
-more details.
-.SH QUERYING THE INDEX
-Duc has various subcommands for querying or exploring the index:
-.IP \(bu 3
-`duc\[hy]nox info` shows a list of available directory trees in the
-database, and the time and date of the last scan.
-.IP \(bu 3
-`duc\[hy]nox ls` lists all files and directories under the given path on
-the console.
-.IP \(bu 3
-`duc\[hy]nox ui` runs a ncurses based console user interface for exploring
-the file system usage
-.SH OPTIONS
-This section list all available subcommands and describes their usage and
-\fIoptions\fP.
-Global \fIoptions\fP
-These \fIoptions\fP apply to all Duc subcommands:
-.RS
-.IP \(bu 3
-\[hy]\[hy]debug:
-increase verbosity to debug level
-.IP \(bu 3
-\[hy]h, \[hy]\[hy]help:
-show help
-.IP \(bu 3
-\[hy]q, \[hy]\[hy]quiet:
-quiet mode, do not print any warning
-.IP \(bu 3
-\[hy]v, \[hy]\[hy]verbose:
-increase verbosity
-.IP \(bu 3
-\[hy]\[hy]version:
-output version information and exit
-.RE
-.RE
-.PP
-duc\[hy]nox help
-Options for command `duc\[hy]nox help [\fIoptions\fP]`:
-.RS
-.IP \(bu 3
-\[hy]a, \[hy]\[hy]all:
-show complete help for all commands
-.RE
-.PP
-duc\[hy] index
-The 'index' subcommand performs a recursive scan of the given paths on the
-filesystem and calculates the inclusive size of all directories. The results
-are written to the index, and can later be queried by one of the other
-duc\[hy]nox tools.
-.RS
-.PP
-Options for command `duc\[hy]nox index [\fIoptions\fP] PATH \.\.\.`:
-.RS
-.IP \(bu 3
-\[hy]b, \[hy]\[hy]bytes:
-show file size in exact number of bytes
-.IP \(bu 3
-\[hy]d, \[hy]\[hy]database=VAL:
-use database file VAL
-.IP \(bu 3
-\[hy]e, \[hy]\[hy]exclude=VAL:
-exclude files matching VAL
-.IP \(bu 3
-\[hy]H, \[hy]\[hy]check\[hy]hard\[hy]links:
-count hard links only once. if two or more hard links point to the same
-file, only one of the hard links is displayed and counted
-.IP \(bu 3
-\[hy]f, \[hy]\[hy]force:
-force writing in case of corrupted db
-.IP \(bu 3
-\[hy]\[hy]fs\[hy]exclude=VAL
-exclude file system type VAL during indexing. VAL is a comma separated list
-of file system types as found in your systems fstab, for example ext3,
-ext4,dosfs
-.IP \(bu 3
-\[hy]\[hy]fs\[hy]include=VAL
-include file system type VAL during indexing. VAL is a comma separated
-list of file system types as found in your systems fstab, for example
-ext3,ext4,dosfs
-.IP \(bu 3
-\[hy]\[hy]hide\[hy]file\[hy]names:
-hide file names in index (privacy). the names of directories will be
-preserved, but the names of the individual files will be hidden
-.IP \(bu 3
-\[hy]m, \[hy]\[hy]max\[hy]depth=VAL:
-limit directory names to given depth. when this option is given
-duc\[hy]nox will traverse the complete file system, but will only the
-first VAL levels of directories in the database to reduce the size of the
-index
-.IP \(bu 3
-\[hy]x, \[hy]\[hy]one\[hy]file\[hy]system:
-skip directories on different file systems
-.IP \(bu 3
-\[hy]p, \[hy]\[hy]progress:
-show progress during indexing
-.IP \(bu 3
-\[hy]\[hy]dry\[hy]run:
-do not update database, just crawl
-.IP \(bu 3
-\[hy]\[hy]uncompressed:
-do not use compression for database. Duc enables compression if the
-underlying database supports this. This reduces index size at the cost of
-slightly longer indexing time
-.RE
-.RE
-.PP
-duc\[hy]nox info
-Options for command `duc\[hy]nox info [\fIoptions\fP]`:
-.RS
-.IP \(bu 3
-\[hy]a, \[hy]\[hy]apparent:
-show apparent instead of actual file size
-.IP \(bu 3
-\[hy]b, \[hy]\[hy]bytes:
-show file size in exact number of bytes
-.IP \(bu 3
-\[hy]d, \[hy]\[hy]database=VAL:
-select database file to use [~/.duc.db]
-.RE
-.PP
-duc\[hy]nox ls
-The 'ls' subcommand queries the duc database and lists the inclusive size of
-all files and directories on the given path. If no path is given the current
-working directory is listed.
-.RS
-.PP
-Options for command `duc\[hy]nox ls [\fIoptions\fP] [PATH]`:
-.RS
-.IP \(bu 3
-\[hy]a, \[hy]\[hy]apparent:
-show apparent instead of actual file size
-.IP \(bu 3
-\[hy]\[hy]ascii:
-use ASCII characters instead of UTF-8 to draw tree
-.IP \(bu 3
-\[hy]b, \[hy]\[hy]bytes:
-show file size in exact number of bytes
-.IP \(bu 3
-\[hy]F, \[hy]\[hy]classify:
-append file type indicator (one of */) to entries
-.IP \(bu 3
-\[hy]c, \[hy]\[hy]color:
-colorize output (only on ttys)
-.IP \(bu 3
-\[hy]\[hy]count
-show number of files instead of file size
-.IP \(bu 3
-\[hy]d, \[hy]\[hy]database=VAL:
-select database file to use [~/.duc.db]
-.IP \(bu 3
-\[hy]\[hy]dirs\[hy]only:
-list only directories, skip individual files
-.IP \(bu 3
-\[hy]\[hy]full\[hy]path
-show full path instead of tree in recursive view
-.IP \(bu 3
-\[hy]l, \[hy]\[hy]levels=VAL:
-traverse up to ARG levels deep [4]
-.IP \(bu 3
-\[hy]n, \[hy]\[hy]name\[hy]sort
-sort output by name instead of by size
-.IP \(bu 3
-\[hy]R, \[hy]\[hy]recursive:
-recursively list subdirectories
-.RE
-.RE
-.PP
-duc\[hy]nox xml
-Options for command `duc\[hy]nox xml [\fIoptions\fP] [PATH]`:
-.RS
-.IP \(bu 3
-\[hy]d, \[hy]\[hy]database=VAL:
-select database file to use [~/.duc.db]
-.IP \(bu 3
-\[hy]x, \[hy]\[hy]exclude\[hy]files:
-exclude file from xml output, only include directories
-.IP \(bu 3
-\[hy]s, \[hy]\[hy]min_size=VAL:
-specify min size for files or directories
-.RE
-.PP
-duc\[hy]nox cgi
-Options for command `duc\[hy]nox cgi [\fIoptions\fP] [PATH]`:
-.RS
-.IP \(bu 3
-\[hy]a, \[hy]\[hy]apparent:
-Show apparent instead of actual file size
-.IP \(bu 3
-\[hy]b, \[hy]\[hy]bytes:
-show file size in exact number of bytes
-.IP \(bu 3
-\[hy]\[hy]count
-show number of files instead of file size
-.IP \(bu 3
-\[hy]d, \[hy]\[hy]database=VAL:
-select database file to use [~/.duc.db]
-.IP \(bu 3
-\[hy]l, \[hy]\[hy]levels=VAL:
-draw up to ARG levels deep [4]
-.IP \(bu 3
-\[hy]\[hy]list:
-generate table with file list
-.RE
-.PP
-duc\[hy]nox ui
-The 'ui' subcommand queries the duc database and runs an interactive ncurses
-utility for exploring the disk usage of the given path. If no path is given the
-current working directory is explored.
-.RS
-.PP
-The following keys can be used to navigate and alter the file system:
-.PP
-.nf
-.fam C
- up, pgup, j: move cursor up
- down, pgdn, k: move cursor down
- home, 0: move cursor to top
- end, $: move cursor to bottom
- left, backspace: go up to parent directory (..)
- right, enter: descent into selected directory
- a: toggle between actual and apparent disk usage
- b: toggle between exact and abbreviated sizes
- c: toggle between file size and file count
- h: show help. press 'q' to return to the main
- screen
- n: toggle sort order between 'size' and 'name'
- q, escape: quit
-
-
-.fam T
-.fi
-Options for command `duc\[hy]nox ui [\fIoptions\fP] [PATH]`:
-.RS
-.IP \(bu 3
-\[hy]a, \[hy]\[hy]apparent:
-show apparent instead of actual file size
-.IP \(bu 3
-\[hy]b, \[hy]\[hy]bytes:
-show file size in exact number of bytes
-.IP \(bu 3
-\[hy]\[hy]count
-show number of files instead of file size
-.IP \(bu 3
-\[hy]c, \[hy]\[hy]color:
-colorize output
-.IP \(bu 3
-\[hy]\[hy]no\[hy]color
-do not use colors on terminal output
-.IP \(bu 3
-\[hy]d, \[hy]\[hy]database=VAL:
-select database file to use [~/.duc.db]
-.IP \(bu 3
-\[hy]\fB-n\fP, \[hy]\[hy]name\[hy]sort
-sort output by name instead of by size
-.IP \(bu 3
-\[hy]\[hy]no\[hy]color
-do not use colors on terminal output
-.SH CGI INTERFACING
-The `duc\[hy]nox` binary has support for a rudimentary CGI interface,
-.TP
-.B
-currently only tested with apache.
-The CGI interface generates a simple HTML
-page with a list of indexed directories. If the option `\[hy]\[hy]list` is
-given, a list of top sized files/dirs is written.
-.PP
-Configuration is done by creating a simple shell script as .cgi in a directory
-which is configured for CGI execution by your web server (usually
-`/usr/lib/cgi-bin`). The shell script should simply start duc\[hy]nox, and
-pass the location of the database to navigate.
-.PP
-An example duc.cgi script would be
-.PP
-.nf
-.fam C
- #!/bin/sh
- /usr/bin/duc\[hy]nox cgi -d /home/jenny/.duc.db
-
- * Make sure the database file is readable by the user (usually
- www\[hy]data)
- * Debugging is best done by inspecting the web server's error log
- * Make sure the .cgi script has execute permissions
- (`chmod +x duc.cgi`)
-
-.fam T
-.fi
-Some notes:
-.RS
-.IP \(bu 3
-The HTML page is generated with a simple embedded CSS style sheet. If the
-style is not to your liking you can provide an external CSS url with the
-\[hy]\[hy]css\[hy]url option which will then be used instead of the
-embedded style definition.
-.IP \(bu 3
-Add the option \[hy]\[hy]list to generate a table of top sized files and
-directories in the HTML page.
-.IP \(bu 3
-The \fIoptions\fP \[hy]\[hy]header and \[hy]\[hy]footer allow you to insert
your
-own HTML code before and after the main.
-.RE
-.PP
-The current CGI configuration is not very flexible, nor secure. It is not
-advised to run the CGI from public reachable web servers, use at your own risk.
-.SH A NOTE ON FILE SIZE AND DISK USAGE
-The concepts of 'file size' and 'disk usage' can be a bit confusing. Files on
-disk have an apparent size, which indicates how much bytes are in the file from
-the users point of view; this is the size reported by tools like `ls \[hy]l`.
-.TP
-.B
-The apparent size can be any number, from 0 bytes up to several TB.
-The
-actual number of bytes which are used on the filesystem to store the file can
-differ from this apparent size for a number of reasons: disks store data in
-blocks, which cause files to always take up a multiple of the block size,
-files can have holes ('sparse' files), and other technical reasons. This
-number is always a multiple of 512, which means that the actual size used for
-a file is almost always a bit more then its apparent size.
-.PP
-Duc has two modes for counting file sizes:
-.PP
-\[hy] `apparent size`: this is the size as reported by `ls`. This number
-indicates the file length, which is usually smaller then the actual disk
-usage.
-.PP
-\[hy] `actual size`: this is the size as reported by `du` and `df`. The
-actual file size tells you how much disk is actually used by a file, and is
-always a multiple of 512 bytes.
-.PP
-The default mode used by duc\[hy]nox is to use the 'actual size'. Most
-duc\[hy]nox commands to report disk usage (`duc\[hy]nox ls`, etc) have an
-option to change between these two modes (usually the `\[hy]a`).
-.SH EXAMPLES
-Index the /usr directory, writing to the default database location ~/.duc.db:
-.PP
-.nf
-.fam C
- $ duc\[hy]nox index /usr
-
-.fam T
-.fi
-List all files and directories under /usr/local, showing relative file sizes
-in a graph:
-.PP
-.nf
-.fam C
- $ duc\[hy]nox ls \[hy]Fg /usr/local
- 4.7G lib/ [+++++++++++++++++++++++++++++++++++++]
- 3.1G share/ [+++++++++++++++++++++++++ ]
- 2.7G src/ [+++++++++++++++++++++ ]
- 814.9M bin/ [++++ ]
- 196.6M include/ [+ ]
- 66.6M x86_64-w64-mingw32/ [ ]
- 59.9M local/ [ ]
- 38.8M i686-w64-mingw32/ [ ]
- 20.3M sbin/ [ ]
- 13.6M lib32/ [ ]
- 13.3M libx32/ [ ]
-
-.fam T
-.fi
-.TP
-.B
-or use the \[hy]R
-\fIoptions\fP for the tree view:
-.PP
-.nf
-.fam C
- $ duc\[hy]nox ls \[hy]RF /etc/logcheck
- 24.0K `+\[hy] ignore.d.server/
- 4.0K | `+\[hy] hddtemp
- 4.0K | |\[hy] ntpdate
- 4.0K | |\[hy] lirc
- 4.0K | |\[hy] rsyslog
- 4.0K | `\[hy] libsasl2\[hy]modules
- 8.0K |\[hy] ignore.d.workstation/
- 4.0K | `\[hy] lirc
- 8.0K `\[hy] ignore.d.paranoid/
- 4.0K `\[hy] lirc
-
-.fam T
-.fi
-The following sample configuration file defines default parameters for the
-`duc\[hy]nox ls` command and defines a global option to configure the
-database path which is used by all subcommands
-.PP
-.nf
-.fam C
- [global]
- database /var/cache/duc.db
-
- [ls]
- recursive
- classify
- color
-
- [ui]
- color
-.fam T
-.fi
-.SH FREQUENTLY ASKED QUESTIONS
-What does the error \'Database version mismatch mean?
-.PP
-The layout of the index database sometimes changes when new features are
implemented\. When you get this error you have probably upgraded to a newer
version\. Just remove the old database file and rebuild the index.
-.PP
-Duc crashes with a segmentation fault, is it that buggy?
-.PP
-By default Duc uses the Tokyocabinet database backend\. Tokyocabinet is pretty
fast, stores the database in a single file and has nice compression support to
keep the database small\. Unfortunately, it is not always robust and sometimes
chokes on corrupt database files\. Try to remove the database and rebuild the
index\. If the error persists contact the authors.
-.SH FILES
-At startup duc\[hy]nox tries to read its configuration from three locations
-in this particular order: `/etc/ducrc`, `~/\.config/duc/ducrc`, `~/.ducrc`
-and `./.ducrc`.
-.PP
-Duc mainains an index of scanned directories, which defaults to ~/.duc.db.
-All tools take the \[hy]d/\[hy]\[hy]database option to override the database
-path.
-.SH AUTHORS
-.IP \(bu 3
-Ico Doornekamp <d...@zevv.nl>
-.IP \(bu 3
-John Stoffel <j...@stoffel.org>
-.PP
-Other contributors can be found in the Git log at GitHub.
-.PP
-This manual page was adapt by Herbert Parentes Fortes Neto
-<h...@debian.org> from the duc manpage of the duc project for
-duc-nox package of the Debian project (but may be used by others)
-.SH LICENSE
-Duc is free software; you can redistribute it and/or modify it under the terms
-of the GNU General Public License as published by the Free Software Foundation;
-version 2 dated June, 1991. Duc is distributed in the hope that it will be
-useful, but WITHOUT ANY WARRANTY; without even the implied warranty of
-MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public
-License for more details.
diff -Nru duc-1.4.3/debian/man/duc-nox.header
duc-1.4.3/debian/man/duc-nox.header
--- duc-1.4.3/debian/man/duc-nox.header 2017-01-13 11:03:20.000000000 -0200
+++ duc-1.4.3/debian/man/duc-nox.header 1969-12-31 21:00:00.000000000 -0300
@@ -1 +0,0 @@
-.TH duc-nox "1" "Jan 2017" "DUC-NOX 1.4.3" "high-performance disk usage
analyzer"
diff -Nru duc-1.4.3/debian/man/duc-nox.txt duc-1.4.3/debian/man/duc-nox.txt
--- duc-1.4.3/debian/man/duc-nox.txt 2017-01-13 11:03:20.000000000 -0200
+++ duc-1.4.3/debian/man/duc-nox.txt 1969-12-31 21:00:00.000000000 -0300
@@ -1,438 +0,0 @@
-NAME
- duc\[hy]nox \- index, query and graph disk usage
-SYNOPSIS
- duc\[hy]nox <subcommand> [options]
-DESCRIPTION
- Duc is a collection of tools for inspecting and visualizing disk usage.
-
- Duc maintains an indexed database of accumulated sizes of directories of your
- file system, and allows you to query this database with some tools, or create
- graphs to show you where your bytes are.
-
- Duc scales quite well, it has been tested on systems with more then 500
million
- files and several petabytes of storage.
-USAGE
- Duc comes with a command line tool called `duc\[hy]nox`, which is used to
create,
- maintain and query the disk usage database. run `duc\[hy]nox help` to get a
list of
- available commands. `duc\[hy]nox help <subcommand>` describes the usage of a
specific
- subcommand. Run `duc\[hy]nox help \[hy]\[hy]all` for an extensive list of all
commands and
- their options.
-
- Duc allows any option to be placed either on the command line or in a
- configuration file. Options on the command line are preceded by a
- double-leading-dash (`\[hy]\[hy]option`), some options have a corresponding
- short option which can be used as well with a single leading dash. (`\[hy]o`)
-
- At startup duc tries to read its configuration from three locations in this
- particular order: `/etc/ducrc`, `~/\.config/duc/ducrc`, `~/.ducrc` and
`./.ducrc`.
-
- A configuration file consists of sections and parameters. The section names
- correspond to the duc\[hy]nox subcommands for which the parameters in that
- section apply. A section begins with the name of the section in square
- brackets and continues until the next section begins.Sections contain
- parameters, one per line, which consist of a single option name for boolean
- flags, or a option name and a value for options which take a value. See the
- EXAMPLES section for an example of the configuration file format.
-CREATING THE INDEX
- Duc needs an index file of the file system before it is able to show any
- information. To create the index, run the `duc\[hy]nox index` command. For
- example, to create an index of your home directory run `duc\[hy]nox index ~`
-
- $ duc\[hy]nox index /usr
- Skipping lost+found: Permission denied
- Indexed 333823 files and 48200 directories, (35.0GB total)
- in 1 seconds
-
- The default location of the database is `$HOME/.duc.db`. To use a different
- database location, use the DUC_DATABASE environment variable or specify the
- database location with the \[hy]\[hy]database argument.
-
- You can run `duc\[hy] index` at any time later to rebuild the index.
-
- By default Duc indexes all directories it encounters during file system
- traversal, including special file systems like /proc and /sys, and
- network file systems like NFS or Samba mounts. There are a few options to
- select what parts of your filesystem you want to include or exclude from the
- scan, check the documentation below for \[hy]\[hy]one\[hy]file\[hy]system,
- \[hy]\[hy]exclude, \[hy]\[hy]fs\[hy]exclude and \[hy]\[hy]fs\[hy]include for
- more details.
-QUERYING THE INDEX
- Duc has various subcommands for querying or exploring the index:
-
- * `duc\[hy]nox info` shows a list of available directory trees in the
- database, and the time and date of the last scan.
-
- * `duc\[hy]nox ls` lists all files and directories under the given path on
- the console.
-
- * `duc\[hy]nox ui` runs a ncurses based console user interface for exploring
- the file system usage
-OPTIONS
- This section list all available subcommands and describes their usage and
- options.
-Global options
- These options apply to all Duc subcommands:
-
- * \[hy]\[hy]debug:
- increase verbosity to debug level
-
- * \[hy]h, \[hy]\[hy]help:
- show help
-
- * \[hy]q, \[hy]\[hy]quiet:
- quiet mode, do not print any warning
-
- * \[hy]v, \[hy]\[hy]verbose:
- increase verbosity
-
- * \[hy]\[hy]version:
- output version information and exit
-
-duc\[hy]nox help
- Options for command `duc\[hy]nox help [options]`:
-
- * \[hy]a, \[hy]\[hy]all:
- show complete help for all commands
-
-duc\[hy] index
- The 'index' subcommand performs a recursive scan of the given paths on the
- filesystem and calculates the inclusive size of all directories. The results
- are written to the index, and can later be queried by one of the other
- duc\[hy]nox tools.
-
- Options for command `duc\[hy]nox index [options] PATH ...`:
-
- * \[hy]b, \[hy]\[hy]bytes:
- show file size in exact number of bytes
-
- * \[hy]d, \[hy]\[hy]database=VAL:
- use database file VAL
-
- * \[hy]e, \[hy]\[hy]exclude=VAL:
- exclude files matching VAL
-
- * \[hy]H, \[hy]\[hy]check\[hy]hard\[hy]links:
- count hard links only once. if two or more hard links point to the same
- file, only one of the hard links is displayed and counted
-
- * \[hy]f, \[hy]\[hy]force:
- force writing in case of corrupted db
-
- * \[hy]\[hy]fs\[hy]exclude=VAL
- exclude file system type VAL during indexing. VAL is a comma separated list
- of file system types as found in your systems fstab, for example ext3,
- ext4,dosfs
-
- * \[hy]\[hy]fs\[hy]include=VAL
- include file system type VAL during indexing. VAL is a comma separated
- list of file system types as found in your systems fstab, for example
- ext3,ext4,dosfs
-
- * \[hy]\[hy]hide\[hy]file\[hy]names:
- hide file names in index (privacy). the names of directories will be
- preserved, but the names of the individual files will be hidden
-
- * \[hy]m, \[hy]\[hy]max\[hy]depth=VAL:
- limit directory names to given depth. when this option is given
- duc\[hy]nox will traverse the complete file system, but will only the
- first VAL levels of directories in the database to reduce the size of the
- index
-
- * \[hy]x, \[hy]\[hy]one\[hy]file\[hy]system:
- skip directories on different file systems
-
- * \[hy]p, \[hy]\[hy]progress:
- show progress during indexing
-
- * \[hy]\[hy]dry\[hy]run:
- do not update database, just crawl
-
- * \[hy]\[hy]uncompressed:
- do not use compression for database. Duc enables compression if the
- underlying database supports this. This reduces index size at the cost of
- slightly longer indexing time
-
-duc\[hy]nox info
- Options for command `duc\[hy]nox info [options]`:
-
- * \[hy]a, \[hy]\[hy]apparent:
- show apparent instead of actual file size
-
- * \[hy]b, \[hy]\[hy]bytes:
- show file size in exact number of bytes
-
- * \[hy]d, \[hy]\[hy]database=VAL:
- select database file to use [~/.duc.db]
-
-duc\[hy]nox ls
- The 'ls' subcommand queries the duc database and lists the inclusive size of
- all files and directories on the given path. If no path is given the current
- working directory is listed.
-
- Options for command `duc\[hy]nox ls [options] [PATH]`:
-
- * \[hy]a, \[hy]\[hy]apparent:
- show apparent instead of actual file size
-
- * \[hy]\[hy]ascii:
- use ASCII characters instead of UTF-8 to draw tree
-
- * \[hy]b, \[hy]\[hy]bytes:
- show file size in exact number of bytes
-
- * \[hy]F, \[hy]\[hy]classify:
- append file type indicator (one of */) to entries
-
- * \[hy]c, \[hy]\[hy]color:
- colorize output (only on ttys)
-
- * \[hy]\[hy]count
- show number of files instead of file size
-
- * \[hy]d, \[hy]\[hy]database=VAL:
- select database file to use [~/.duc.db]
-
- * \[hy]\[hy]dirs\[hy]only:
- list only directories, skip individual files
-
- * \[hy]\[hy]full\[hy]path
- show full path instead of tree in recursive view
-
- * \[hy]l, \[hy]\[hy]levels=VAL:
- traverse up to ARG levels deep [4]
-
- * \[hy]n, \[hy]\[hy]name\[hy]sort
- sort output by name instead of by size
-
- * \[hy]R, \[hy]\[hy]recursive:
- recursively list subdirectories
-
-duc\[hy]nox xml
- Options for command `duc\[hy]nox xml [options] [PATH]`:
-
- * \[hy]d, \[hy]\[hy]database=VAL:
- select database file to use [~/.duc.db]
-
- * \[hy]x, \[hy]\[hy]exclude\[hy]files:
- exclude file from xml output, only include directories
-
- * \[hy]s, \[hy]\[hy]min_size=VAL:
- specify min size for files or directories
-
-duc\[hy]nox cgi
- Options for command `duc\[hy]nox cgi [options] [PATH]`:
-
- * \[hy]a, \[hy]\[hy]apparent:
- Show apparent instead of actual file size
-
- * \[hy]b, \[hy]\[hy]bytes:
- show file size in exact number of bytes
-
- * \[hy]\[hy]count
- show number of files instead of file size
-
- * \[hy]d, \[hy]\[hy]database=VAL:
- select database file to use [~/.duc.db]
-
- * \[hy]l, \[hy]\[hy]levels=VAL:
- draw up to ARG levels deep [4]
-
- * \[hy]\[hy]list:
- generate table with file list
-
-duc\[hy]nox ui
- The 'ui' subcommand queries the duc database and runs an interactive ncurses
- utility for exploring the disk usage of the given path. If no path is given
the
- current working directory is explored.
-
- The following keys can be used to navigate and alter the file system:
-
- up, pgup, j: move cursor up
- down, pgdn, k: move cursor down
- home, 0: move cursor to top
- end, $: move cursor to bottom
- left, backspace: go up to parent directory (..)
- right, enter: descent into selected directory
- a: toggle between actual and apparent disk usage
- b: toggle between exact and abbreviated sizes
- c: toggle between file size and file count
- h: show help. press 'q' to return to the main
- screen
- n: toggle sort order between 'size' and 'name'
- q, escape: quit
-
-
- Options for command `duc\[hy]nox ui [options] [PATH]`:
-
- * \[hy]a, \[hy]\[hy]apparent:
- show apparent instead of actual file size
-
- * \[hy]b, \[hy]\[hy]bytes:
- show file size in exact number of bytes
-
- * \[hy]\[hy]count
- show number of files instead of file size
-
- * \[hy]c, \[hy]\[hy]color:
- colorize output
-
- * \[hy]\[hy]no\[hy]color
- do not use colors on terminal output
-
- * \[hy]d, \[hy]\[hy]database=VAL:
- select database file to use [~/.duc.db]
-
- * \[hy]-n, \[hy]\[hy]name\[hy]sort
- sort output by name instead of by size
-
- * \[hy]\[hy]no\[hy]color
- do not use colors on terminal output
-
-CGI INTERFACING
- The `duc\[hy]nox` binary has support for a rudimentary CGI interface,
- currently only tested with apache. The CGI interface generates a simple HTML
- page with a list of indexed directories. If the option `\[hy]\[hy]list` is
- given, a list of top sized files/dirs is written.
-
- Configuration is done by creating a simple shell script as .cgi in a directory
- which is configured for CGI execution by your web server (usually
- `/usr/lib/cgi-bin`). The shell script should simply start duc\[hy]nox, and
- pass the location of the database to navigate.
-
- An example duc.cgi script would be
-
- #!/bin/sh
- /usr/bin/duc\[hy]nox cgi -d /home/jenny/.duc.db
-
- * Make sure the database file is readable by the user (usually
- www\[hy]data)
- * Debugging is best done by inspecting the web server's error log
- * Make sure the .cgi script has execute permissions
- (`chmod +x duc.cgi`)
-
- Some notes:
-
- * The HTML page is generated with a simple embedded CSS style sheet. If the
- style is not to your liking you can provide an external CSS url with the
- \[hy]\[hy]css\[hy]url option which will then be used instead of the
- embedded style definition.
-
- * Add the option \[hy]\[hy]list to generate a table of top sized files and
- directories in the HTML page.
-
- * The options \[hy]\[hy]header and \[hy]\[hy]footer allow you to insert
your
- own HTML code before and after the main.
-
- The current CGI configuration is not very flexible, nor secure. It is not
- advised to run the CGI from public reachable web servers, use at your own
risk.
-
-A NOTE ON FILE SIZE AND DISK USAGE
- The concepts of 'file size' and 'disk usage' can be a bit confusing. Files on
- disk have an apparent size, which indicates how much bytes are in the file
from
- the users point of view; this is the size reported by tools like `ls \[hy]l`.
- The apparent size can be any number, from 0 bytes up to several TB. The
- actual number of bytes which are used on the filesystem to store the file can
- differ from this apparent size for a number of reasons: disks store data in
- blocks, which cause files to always take up a multiple of the block size,
- files can have holes ('sparse' files), and other technical reasons. This
- number is always a multiple of 512, which means that the actual size used for
- a file is almost always a bit more then its apparent size.
-
- Duc has two modes for counting file sizes:
-
- \[hy] `apparent size`: this is the size as reported by `ls`. This number
- indicates the file length, which is usually smaller then the actual disk
- usage.
-
- \[hy] `actual size`: this is the size as reported by `du` and `df`. The
- actual file size tells you how much disk is actually used by a file, and is
- always a multiple of 512 bytes.
-
- The default mode used by duc\[hy]nox is to use the 'actual size'. Most
- duc\[hy]nox commands to report disk usage (`duc\[hy]nox ls`, etc) have an
- option to change between these two modes (usually the `\[hy]a`).
-
-EXAMPLES
- Index the /usr directory, writing to the default database location ~/.duc.db:
-
- $ duc\[hy]nox index /usr
-
- List all files and directories under /usr/local, showing relative file sizes
- in a graph:
-
- $ duc\[hy]nox ls \[hy]Fg /usr/local
- 4.7G lib/ [+++++++++++++++++++++++++++++++++++++]
- 3.1G share/ [+++++++++++++++++++++++++ ]
- 2.7G src/ [+++++++++++++++++++++ ]
- 814.9M bin/ [++++ ]
- 196.6M include/ [+ ]
- 66.6M x86_64-w64-mingw32/ [ ]
- 59.9M local/ [ ]
- 38.8M i686-w64-mingw32/ [ ]
- 20.3M sbin/ [ ]
- 13.6M lib32/ [ ]
- 13.3M libx32/ [ ]
-
- or use the \[hy]R options for the tree view:
-
- $ duc\[hy]nox ls \[hy]RF /etc/logcheck
- 24.0K `+\[hy] ignore.d.server/
- 4.0K | `+\[hy] hddtemp
- 4.0K | |\[hy] ntpdate
- 4.0K | |\[hy] lirc
- 4.0K | |\[hy] rsyslog
- 4.0K | `\[hy] libsasl2\[hy]modules
- 8.0K |\[hy] ignore.d.workstation/
- 4.0K | `\[hy] lirc
- 8.0K `\[hy] ignore.d.paranoid/
- 4.0K `\[hy] lirc
-
- The following sample configuration file defines default parameters for the
- `duc\[hy]nox ls` command and defines a global option to configure the
- database path which is used by all subcommands
-
- [global]
- database /var/cache/duc.db
-
- [ls]
- recursive
- classify
- color
-
- [ui]
- color
-FREQUENTLY ASKED QUESTIONS
- What does the error \'Database version mismatch mean?
-
- The layout of the index database sometimes changes when new features are
implemented\. When you get this error you have probably upgraded to a newer
version\. Just remove the old database file and rebuild the index.
-
- Duc crashes with a segmentation fault, is it that buggy?
-
- By default Duc uses the Tokyocabinet database backend\. Tokyocabinet is
pretty fast, stores the database in a single file and has nice compression
support to keep the database small\. Unfortunately, it is not always robust and
sometimes chokes on corrupt database files\. Try to remove the database and
rebuild the index\. If the error persists contact the authors.
-
-FILES
- At startup duc\[hy]nox tries to read its configuration from three locations
- in this particular order: `/etc/ducrc`, `~/\.config/duc/ducrc`, `~/.ducrc`
- and `./.ducrc`.
-
- Duc mainains an index of scanned directories, which defaults to ~/.duc.db.
- All tools take the \[hy]d/\[hy]\[hy]database option to override the database
- path.
-
-AUTHORS
- * Ico Doornekamp <d...@zevv.nl>
- * John Stoffel <j...@stoffel.org>
-
- Other contributors can be found in the Git log at GitHub.
-
- This manual page was adapt by Herbert Parentes Fortes Neto
- <h...@debian.org> from the duc manpage of the duc project for
- duc-nox package of the Debian project (but may be used by others)
-
-LICENSE
- Duc is free software; you can redistribute it and/or modify it under the terms
- of the GNU General Public License as published by the Free Software
Foundation;
- version 2 dated June, 1991. Duc is distributed in the hope that it will be
- useful, but WITHOUT ANY WARRANTY; without even the implied warranty of
- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General
Public
- License for more details.
diff -Nru duc-1.4.3/debian/man/genallman.sh duc-1.4.3/debian/man/genallman.sh
--- duc-1.4.3/debian/man/genallman.sh 2015-07-26 12:00:56.000000000 -0300
+++ duc-1.4.3/debian/man/genallman.sh 1969-12-31 21:00:00.000000000 -0300
@@ -1,27 +0,0 @@
-#!/bin/bash
-
-# Generate several manpages at the same time.
-# C 2014 Joao Eriberto Mota Filho <eribe...@debian.org>
-#
-# You can use this code in the same terms of the BSD-3-clause license or,
-# optionally, in the same terms of the license used in debian/ directory
-# in this Debian package. Please, to the last option, refer the package
-# name when using.
-#
-# This script uses txt2man. You need 2 files: program_name.txt and
-# program_name.header.
-#
-# The program_name.header must be use this structure:
-#
-# .TH <program_name> "<manpage_level>" "<date>" "<program_name_upper_case>
<program_version>" "<program_description>"
-#
-# Example:
-#
-# .TH mac-robber "1" "May 2013" "MAC-ROBBER 1.02" "collects data about
allocated files in mounted filesystems"
-
-for NAME in $(ls | grep header | cut -d'.' -f1)
-do
- LEVEL=$(cat $NAME.header | cut -d" " -f3 | tr -d '"')
- cat $NAME.header > $NAME.$LEVEL
- txt2man $NAME.txt | grep -v '^.TH ' >> $NAME.$LEVEL
-done
diff -Nru duc-1.4.3/debian/rules duc-1.4.3/debian/rules
--- duc-1.4.3/debian/rules 2016-11-26 08:46:56.000000000 -0200
+++ duc-1.4.3/debian/rules 2017-02-01 17:28:00.000000000 -0200
@@ -35,6 +35,10 @@
override_dh_auto_install:
$(MAKE) -C $(BUILDDIR) install DESTDIR=$(BUILDDIR).inst
$(MAKE) -C $(BUILDDIR_NOX) install DESTDIR=$(BUILDDIR_NOX).inst
+ cp -r doc $(BUILDDIR_NOX)/
+ rm -f $(BUILDDIR_NOX)/doc/duc.1
+ $(MAKE) -C $(BUILDDIR_NOX)/doc
+ mv $(BUILDDIR_NOX)/doc/duc.1 $(BUILDDIR_NOX)/doc/duc-nox.1
mv $(BUILDDIR_NOX)/duc $(BUILDDIR_NOX)/duc-nox
override_dh_auto_clean:
