[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#420540: marked as done (should document how to create -dbg packages)

Your message dated Thu, 28 Feb 2008 11:47:03 +0000
with message-id <E1JUhE7-00078h-6c@ries.debian.org>
and subject line Bug#420540: fixed in developers-reference 3.3.9
has caused the Debian Bug report #420540,
regarding should document how to create -dbg packages
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
420540: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=420540
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: developers-reference
Version: 3.3.8
Severity: normal

The document is missing anything about -dbg packages. Here's some text
you can include if you like it:

Debug packages

A debug package is a package with a name ending in "-dbg", that contains
additional information that gdb can use. Since Debian binaries are
stripped by default, debugging information, including function names and
line numbersm is not available when running gdb on Debian binaries. Debug
packages allow users who need this additional debugging information to
install it, without bloating a regular system with the information.

It is up to a package's maintainer whether to create a debug package or
not. Maintainers are encouraged to create debug packages for library
packages, since this can aid in debugging many programs linked to a
library. In general, debug packages do not need to be added for all
programs; doing so would bloat the archive. But if a maintainer finds
that users often need a debugging version of a program, it can be
worthwhile to make a debug package for it. Programs that are core
infrastructure, such as apache and the X server are also good candidates
for debug packages.

Some debug packages may contain an entire special debugging build of a
library or other binary, but most of them can save space and build time
by instead containing separated debugging symbols that gdb can find and
load on the fly when debugging a program or library. The convention in
Debian is to keep these symbols in /usr/lib/debug/<path>, where <path>
is the path to the executable or library. For example, debugging symbols
for /usr/bin/foo go in /usr/lib/debug/usr/bin/foo, and debugging symbols
for /usr/lib/libfoo.so.1 go in /usr/lib/debug/usr/lib/libfoo.so.1 .

The debugging symbols can be extracted from an object file using 
"objcopy --only-keep-debug". Then the object file can be stripped, and
"objcopy --add-gnu-debuglink" used to specify the path to the debugging
symbol file. The man page for objcopy(1) explains in detail how this
works.

The dh_strip command in debhelper supports creating debug packages, and
can take care of using objcopy to separate out the debugging symbols for
you. If your package uses debhelper, all you need to do is call 
"dh_strip --dbg-package=libfoo-dbg", and add an entry to debian/control
for the debug package.

Note that the Debian package should depend on the package that it
provides debugging symbols for, and this dependency should be versioned.
For example:

Depends: libfoo-dbg (= ${binary:Version})


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.20-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

developers-reference depends on no packages.

Versions of packages developers-reference recommends:
ii  debian-policy                 3.7.2.2    Debian Policy Manual and related d

-- no debconf information

-- 
see shy jo

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message --- 
Source: developers-reference
Source-Version: 3.3.9

We believe that the bug you reported is fixed in the latest version of
developers-reference, which is due to be installed in the Debian FTP archive:

developers-reference-fr_3.3.9_all.deb
  to pool/main/d/developers-reference/developers-reference-fr_3.3.9_all.deb
developers-reference_3.3.9.dsc
  to pool/main/d/developers-reference/developers-reference_3.3.9.dsc
developers-reference_3.3.9.tar.gz
  to pool/main/d/developers-reference/developers-reference_3.3.9.tar.gz
developers-reference_3.3.9_all.deb
  to pool/main/d/developers-reference/developers-reference_3.3.9_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 420540@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
W. Martin Borgert <debacle@debian.org> (supplier of updated developers-reference package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Thu, 28 Feb 2008 10:16:40 +0000
Source: developers-reference
Binary: developers-reference developers-reference-fr
Architecture: source all
Version: 3.3.9
Distribution: unstable
Urgency: low
Maintainer: Debian Documentation Project <debian-doc@lists.debian.org>
Changed-By: W. Martin Borgert <debacle@debian.org>
Description: 
 developers-reference - guidelines and information for Debian developers
 developers-reference-fr - guidelines and information for Debian developers, in French
Closes: 356720 373816 374220 384178 391023 401415 405453 405818 410159 412757 413320 414291 419507 420540 422750 427832 428846 445642
Changes: 
 developers-reference (3.3.9) unstable; urgency=low
 .
   [ Andreas Barth ]
   * Packaging changes:
     - bump standards-version to 3.7.3 (no change)
     - fix debian/copyright
     - move debhelper to Build-Depends.
     - add pdf for French version.
   * Document changes to stable release management. Closes: #414291
   * Debconf error templates no longer discouraged. Thanks,
     Christian Perrier. Closes: #427832
   * Keyring now uses RT. Closes: #428846
   * Document -dbg-packages within BPs. Thanks, Joey Hess. Closes: #420540
   * NMUs now also close bugs. Thanks, Lucas Nussbaum. Closes: #419507
   * Fix documentation about gender neutral. Closes: #384178
   * Fix typo. Closes: #405453
   * More details on how to write documentation. Thanks, Josh Triplett.
     Closes: #422750
   * Add XS-Vcs-*. Thanks to Stefano Zacchiroli. Closes: #391023
   * Small brushup to debconf description. Thanks, Thomas Huriaux.
     Closes: #401415
   * Document Team-Maintainence better. Thanks, Lucas Nussbaum.
     Closes: #410159
   * Add link to more removal ressources. Thanks, Adam D. Barratt,
     Justin Pryzby. Closes: #412757, #356720
   * Repacking source packages need to be documented in copyright.
     Thanks, Russ Allbery. Closes: #413320
   * Better describe version of debian native packages NMUs. Closes: #405818
   * Source, HTML and text are now encoded in UTF-8. Thanks, Jörg Sommer.
     Closes: #373816
   * Source is now DocBook XML instead of debiandoc. Closes: #374220
 .
   [ Raphael Hertzog ]
   * Add a link to enrico's excellent Debian Community Guidelines.
   * Recommend the use of DSA's request tracker instead of mailing them.
   * Remove reference to #debian-sf, #debian-bsd which don't exist anymore. Put
     a reference to #debian-dpkg instead.
   * Remove all stuff concerning non-US.
   * Update information concerning Alioth.
   * Update information concerning the Package Tracking System.
   * Mention Alioth as the main resource for VCS repositories and deprecate
     cvs.debian.org.
   * Remove XS- prefix for Vcs-* fields since dpkg now supports them.
   * Document the Homepage field. Thanks, Christian Perrier. Closes:
     #445642
   * Add Vcs-Svn and Vcs-Browser fields pointing to the new SVN
     repository.
Files: 
 f3b140613997b6255f00cff2e0652485 866 doc optional developers-reference_3.3.9.dsc
 feb746b3608063b4994472866f39709e 871922 doc optional developers-reference_3.3.9.tar.gz
 4f4292fe8246f1338115266a7ff61349 660596 doc optional developers-reference_3.3.9_all.deb
 72e49ae1cd934ebaaf411beb7852214d 663386 doc optional developers-reference-fr_3.3.9_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHxpwF+xM0OFfj6IgRAqdfAJwNNiihs+QYn2KuGIFWNz4UbU0rYACZATqP
VNJKCAzzbxObVoiWSiSsPDY=
=9TZe
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: