Your message dated Tue, 25 Jul 2006 23:04:45 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: debhelper
Version: 5.0.32
Severity: minor
dh_builddeb manual page reads:
DESCRIPTION
dh_builddeb simply calls dpkg-deb(8) to build a debian package or pack-
ages.
Please improve the documentation by providing information on:
- How the dh_builddeb determines and contructs the proper command line
options for dpkg-deb.
- Give an example of debian/control file and debian/changelog (if it
uses these files) and demonstrate how the package creation process
works. What information dh_builddeb uses from these files?
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/dash
Kernel: Linux 2.6.16-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ISO-8859-1) (ignored: LC_ALL set to en_US)
Versions of packages debhelper depends on:
ii binutils 2.16.1cvs20060413-1 The GNU assembler, linker and bina
ii coreutils [fileutils 5.94-1 The GNU core utilities
ii dpkg-dev 1.13.18 package building tools for Debian
ii file 4.17-1 Determines file type using "magic"
ii html2text 1.3.2a-3 An advanced HTML to text converter
ii perl 5.8.8-4 Larry Wall's Practical Extraction
ii po-debconf 1.0 manage translated Debconf template
debhelper recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
The debhelper(7) man page explains in detail how debhelper commands
generally work. This allows for the individual man pages for commands to
only document the things relevant for learning how to use that command
when you already understand how a debhelper command generally works.
After reading debhelper(7), it should be clear how debhelper uses the
control file, what temporary directory the package is built from, etc.
--
see shy jo
signature.asc
Description: Digital signature
--- End Message ---
