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

Bug#907665: marked as done (developers-reference: Section 6.7.9 about dbg packages outdated)

Your message dated Sun, 27 Jan 2019 16:51:48 +0000
with message-id <E1gnneu-0007uO-Rz@fasolo.debian.org>
and subject line Bug#907665: fixed in developers-reference 3.4.22
has caused the Debian Bug report #907665,
regarding developers-reference: Section 6.7.9 about dbg packages outdated
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

907665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907665
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: developers-reference
Severity: normal
Tags: patch

As we now have Automatic Debug Symbol package, I think most of the
section could be deleted and replaced to the references on the Wiki.

The attached patch does that…


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.17.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff --git a/best-pkging-practices.dbk b/best-pkging-practices.dbk
index 6f05ece..6a85f23 100644
--- a/best-pkging-practices.dbk
+++ b/best-pkging-practices.dbk
@@ -1795,58 +1795,32 @@ it in its official location).
 <section id="bpp-dbg">
 <title>Best practices for debug packages</title>
-A debug package is a package with a name ending in -dbg, that contains
-additional information that <command>gdb</command> can use.  Since Debian binaries are stripped by
-default, debugging information, including function names and line numbers, is
-otherwise not available when running <command>gdb</command> 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 <command>gdb</command> can find and load on the fly
-when debugging a program or library.  The convention in Debian is to keep these
-symbols in <filename>/usr/lib/debug/<replaceable>path</replaceable></filename>, where
-<replaceable>path</replaceable> is the path to the executable or library.  For
-example, debugging symbols for <filename>/usr/bin/foo</filename> go in
-<filename>/usr/lib/debug/usr/bin/foo</filename>, and debugging symbols for
-<filename>/usr/lib/libfoo.so.1</filename> go in
-The debugging symbols can be extracted from an object file using 
-<command>objcopy --only-keep-debug</command>.  Then the object file can be stripped,
-and <command>objcopy --add-gnu-debuglink</command> used to specify the path
-to the debugging symbol file. 
-<citerefentry> <refentrytitle>objcopy</refentrytitle> <manvolnum>1</manvolnum>
-</citerefentry> explains in detail how this works.
-The <command>dh_strip</command> command in <systemitem role="package">debhelper</systemitem> supports creating debug
-packages, and can take care of using <command>objcopy</command> to separate
-out the debugging symbols for you.  If your package uses <systemitem role="package">debhelper</systemitem>, all you
-need to do is call <command>dh_strip --dbg-package=libfoo-dbg</command>, and
-add an entry to <filename>debian/control</filename> for the debug package.
+A debug package is a package that contains additional information that
+<command>gdb</command> can use.  Since Debian binaries are stripped by
+default, debugging information, including function names and line
+numbers, is otherwise not available when running <command>gdb</command>
+on Debian binaries.  Debug packages allow users who need this additional
+debugging information to install it, without bloating a regular system
+with the information.
-Note that the debug package should depend on the package that it provides
-debugging symbols for, and this dependency should be versioned.  For example:
+Previously is was up to a package's maintainer whether to create a debug
+package or not. You can still find those manually generated debug
+packages, whose package names generally ended with -dbg.
+However, since end of 2015 manually generating dbg packages are
+depreciated and has been replaced largely by automatic debug symbol
+generation, which will generate packages with names ending with -dbgsym.
+If you want to migrate your legacy -dbg package, please read
+<ulink url="https://wiki.debian.org/AutomaticDebugPackages";> here </ulink>,
+if you want to use the dbgsym packages, you can find instructions
+<ulink url="https://wiki.debian.org/HowToGetABacktrace";> here </ulink>.
-Depends: libfoo (= ${binary:Version})
 <section id="bpp-meta">
 <title>Best practices for meta-packages</title>

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

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.

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

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

Debian distribution maintenance software
Holger Levsen <holger@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@ftp-master.debian.org)

Hash: SHA512

Format: 1.8
Date: Sun, 27 Jan 2019 17:32:03 +0100
Source: developers-reference
Architecture: source
Version: 3.4.22
Distribution: unstable
Urgency: medium
Maintainer: Developers Reference Maintainers <debian-policy@lists.debian.org>
Changed-By: Holger Levsen <holger@debian.org>
Closes: 690750 818850 843966 905930 907665 907915 908291 908890 912724 915310
 developers-reference (3.4.22) unstable; urgency=medium
   [ Holger Wansing ]
   * Fix codename of Debian 11. (Closes: #905930)
   * Fix links to translations (making them one link pointing to the
     doc section on Debian website). Closes: #690750, #912724.
   [ Tobias Frost ]
   * Join the two chapters about the 'default' field (Closes: #818850).
   * Switch Alioth references in the dev-ref text to Salsa. (Closes: #908890)
   [ Jean-Paul Guillonneau ]
   * Update of French translation. Closes: #843966.
   [ Tobias Frost ]
   * Rewriting section about debug packages .(Closes: #907665)
   * Join the two chapters about the 'default' field .(Closes: #818850)
   * German translation for the package salvaging process.
   [ Joseph Herlant ]
   * Add a note on versioning scheme when reverting an NMU. (Closes: #908291)
   [ Holger Levsen ]
   * comment.ent:
     - add url-openpgp-best-practices-fr and use that in fr.po.
     - point url-buildd-p-a-s to https://wiki.debian.org/PackagesArchSpecific
       as alioth is gone. Closes: #915310
   * Improve language in manual, thanks to Paul Hardy for the patch.
     Closes: #907915
   * d/control:
     - upgrade to use debhelper-compat(=11), drop d/compat.
     - add "Rules-Requires-Root: no" to support building as non-root.
     - remove Build-Depends on dpkg-dev as it's part of build-essential and the
       required version is present in wheezy.
     - remove versions (fulfilled pre-squeeze) for Build-Depends-Indep of
       docbook-xsl and dblatex.
     - bump standards version to 4.3.0, no changes needed.
     - sort and wrap Build-Depends-Indep.
     - add myself to uploaders.
   [ Ondřej Nový ]
   * d/changelog: Remove trailing whitespaces.
 c0e7c80183ab122fe6c6f62d544fd990bd74dfa1 2398 developers-reference_3.4.22.dsc
 46bd729ef368aeeb432370c201731d4ba36e899e 671308 developers-reference_3.4.22.tar.xz
 4567e7518eff2cbd7639ef772ed00d7b92eae5cf 5199 developers-reference_3.4.22_source.buildinfo
 32caa0599339f67467497cc069befd74e4d95a9d7d21509b5e6cf02fcfa68b24 2398 developers-reference_3.4.22.dsc
 bc598c8f7a072198a49dfd11c760b7417cd4f72050fef749be517c1daa999947 671308 developers-reference_3.4.22.tar.xz
 da255d205bdbc6b2a80dcf09764753620e38a06b541265658d4f5cddc54ba5df 5199 developers-reference_3.4.22_source.buildinfo
 3bbedc689e80798d21bd75fd2c6eddd6 2398 doc optional developers-reference_3.4.22.dsc
 469ca9a880dacf560a109425d4f895cc 671308 doc optional developers-reference_3.4.22.tar.xz
 a758cc466bbfa35c5d0f08f2b59bd085 5199 doc optional developers-reference_3.4.22_source.buildinfo



--- End Message ---

Reply to: