1 # SOME DESCRIPTIVE TITLE
2 # Copyright (C) 2007 Free Software Foundation, Inc.
9 "Project-Id-Version: PACKAGE VERSION\n"
10 "Report-Msgid-Bugs-To: \n"
11 "POT-Creation-Date: 2008-08-08 11:37-0300\n"
12 "PO-Revision-Date: 2007-07-01 23:19+0000\n"
13 "Last-Translator: <>\n"
16 "Content-Type: text/plain; charset=UTF-8\n"
17 "Content-Transfer-Encoding: \n"
19 # type: Content of: <appendix><title>
21 msgid "Overview of Debian Maintainer Tools"
22 msgstr "Aperçu des outils du responsable Debian"
24 # type: Content of: <appendix><para>
27 "This section contains a rough overview of the tools available to "
28 "maintainers. The following is by no means complete or definitive, but just "
29 "a guide to some of the more popular tools."
31 "Cette section contient un aperçu rapide des outils dont dispose "
32 "leresponsable. Cette liste n'est ni complète, ni définitive, il s'agitjuste "
33 "d'un guide des outils les plus utilisés."
35 # type: Content of: <appendix><para>
38 "Debian maintainer tools are meant to aid developers and free their time for "
39 "critical tasks. As Larry Wall says, there's more than one way to do it."
41 "Les outils du responsable Debian sont destinés à aider les responsableset "
42 "libérer leur temps pour des tâches plus cruciales. Comme le dit LarryWall, "
43 "il y a plus d'une manière de le faire."
45 # type: Content of: <appendix><para>
48 "Some people prefer to use high-level package maintenance tools and some do "
49 "not. Debian is officially agnostic on this issue; any tool which gets the "
50 "job done is fine. Therefore, this section is not meant to stipulate to "
51 "anyone which tools they should use or how they should go about their duties "
52 "of maintainership. Nor is it meant to endorse any particular tool to the "
53 "exclusion of a competing tool."
55 "Certaines personnes préfèrent utiliser des outils de haut niveau,d'autres "
56 "pas. Debian n'a pas de position officielle sur laquestion ; tout outil "
57 "conviendra du moment qu'il fait leboulot. C'est pourquoi cette section n'a "
58 "pas été conçue pour indiquer àchacun quel outil il doit utiliser ou comment "
59 "il devrait faire pourgérer sa charge de responsable Debian. Elle n'est pas "
60 "non plus destinéeà favoriser l'utilisation d'un outil aux dépens d'un autre."
62 # type: Content of: <appendix><para>
65 "Most of the descriptions of these packages come from the actual package "
66 "descriptions themselves. Further information can be found in the package "
67 "documentation itself. You can also see more info with the command "
68 "<command>apt-cache show <package-name></command>."
70 "La plupart des descriptions de ces outils proviennent des descriptionsde "
71 "leurs paquets. Vous trouverez plus d'informations dans lesdocumentations de "
72 "ces paquets. Vous pouvez aussi obtenir plusd'informations avec la commande "
73 "<literal>apt-cache show<nom_paquet></literal>."
75 # type: Content of: <appendix><section><title>
78 msgstr "Outils de base"
80 # type: Content of: <appendix><section><para>
82 msgid "The following tools are pretty much required for any maintainer."
83 msgstr "Les outils suivants sont pratiquement nécessaires à tout responsable."
85 # type: Content of: <appendix><section><section><title>
87 msgid "<systemitem role=\"package\">dpkg-dev</systemitem>"
90 # type: Content of: <appendix><section><section><para>
93 "<systemitem role=\"package\">dpkg-dev</systemitem> contains the tools "
94 "(including <command>dpkg-source</command>) required to unpack, build, and "
95 "upload Debian source packages. These utilities contain the fundamental, low-"
96 "level functionality required to create and manipulate packages; as such, "
97 "they are essential for any Debian maintainer."
100 # type: Content of: <appendix><section><section><title>
102 msgid "<systemitem role=\"package\">debconf</systemitem>"
105 # type: Content of: <appendix><section><section><para>
108 "<systemitem role=\"package\">debconf</systemitem> provides a consistent "
109 "interface to configuring packages interactively. It is user interface "
110 "independent, allowing end-users to configure packages with a text-only "
111 "interface, an HTML interface, or a dialog interface. New interfaces can be "
115 # type: Content of: <appendix><section><section><para>
118 "You can find documentation for this package in the <systemitem role=\"package"
119 "\">debconf-doc</systemitem> package."
122 # type: Content of: <appendix><section><section><para>
125 "Many feel that this system should be used for all packages which require "
126 "interactive configuration; see <xref linkend=\"bpp-config-mgmt\"/> . "
127 "<systemitem role=\"package\">debconf</systemitem> is not currently required "
128 "by Debian Policy, but that may change in the future."
131 # type: Content of: <appendix><section><section><title>
133 msgid "<systemitem role=\"package\">fakeroot</systemitem>"
136 # type: Content of: <appendix><section><section><para>
139 "<systemitem role=\"package\">fakeroot</systemitem> simulates root "
140 "privileges. This enables you to build packages without being root (packages "
141 "usually want to install files with root ownership). If you have <systemitem "
142 "role=\"package\">fakeroot</systemitem> installed, you can build packages as "
143 "a regular user: <literal>dpkg-buildpackage -rfakeroot</literal>."
146 # type: Content of: <appendix><section><title>
148 msgid "Package lint tools"
151 # type: Content of: <appendix><section><para>
154 "According to the Free On-line Dictionary of Computing (FOLDOC), `lint' is a "
155 "Unix C language processor which carries out more thorough checks on the code "
156 "than is usual with C compilers. Package lint tools help package maintainers "
157 "by automatically finding common problems and policy violations in their "
161 # type: Content of: <appendix><section><section><title>
163 msgid "<systemitem role=\"package\">lintian</systemitem>"
166 # type: Content of: <appendix><section><section><para>
169 "<systemitem role=\"package\">lintian</systemitem> dissects Debian packages "
170 "and emits information about bugs and policy violations. It contains "
171 "automated checks for many aspects of Debian policy as well as some checks "
175 # type: Content of: <appendix><section><section><para>
178 "You should periodically get the newest <systemitem role=\"package\">lintian</"
179 "systemitem> from <literal>unstable</literal> and check over all your "
180 "packages. Notice that the <literal>-i</literal> option provides detailed "
181 "explanations of what each error or warning means, what its basis in Policy "
182 "is, and commonly how you can fix the problem."
185 # type: Content of: <appendix><section><section><para>
188 "Refer to <xref linkend=\"sanitycheck\"/> for more information on how and "
189 "when to use Lintian."
192 # type: Content of: <appendix><section><section><para>
195 "You can also see a summary of all problems reported by Lintian on your "
196 "packages at <ulink url=\"&url-lintian;\"></ulink>. These reports contain "
197 "the latest <command>lintian</command> output for the whole development "
198 "distribution (<literal>unstable</literal>)."
201 # type: Content of: <appendix><section><section><title>
203 msgid "<systemitem role=\"package\">debdiff</systemitem>"
206 # type: Content of: <appendix><section><section><para>
209 "<command>debdiff</command> (from the <systemitem role=\"package"
210 "\">devscripts</systemitem> package, <xref linkend=\"devscripts\"/> ) "
211 "compares file lists and control files of two packages. It is a simple "
212 "regression test, as it will help you notice if the number of binary packages "
213 "has changed since the last upload, or if something has changed in the "
214 "control file. Of course, some of the changes it reports will be all right, "
215 "but it can help you prevent various accidents."
218 # type: Content of: <appendix><section><section><para>
220 msgid "You can run it over a pair of binary packages:"
223 # type: Content of: <appendix><section><section><screen>
228 "debdiff package_1-1_arch.deb package_2-1_arch.deb\n"
231 # type: Content of: <appendix><section><section><para>
233 msgid "Or even a pair of changes files:"
236 # type: Content of: <appendix><section><section><screen>
241 "debdiff package_1-1_arch.changes package_2-1_arch.changes\n"
244 # type: Content of: <appendix><section><section><para>
247 "For more information please see <citerefentry> <refentrytitle>debdiff</"
248 "refentrytitle> <manvolnum>1</manvolnum> </citerefentry>."
251 # type: Content of: <appendix><section><title>
253 msgid "Helpers for <filename>debian/rules</filename>"
256 # type: Content of: <appendix><section><para>
259 "Package building tools make the process of writing <filename>debian/rules</"
260 "filename> files easier. See <xref linkend=\"helper-scripts\"/> for more "
261 "information about why these might or might not be desired."
264 # type: Content of: <appendix><section><section><title>
266 msgid "<systemitem role=\"package\">debhelper</systemitem>"
269 # type: Content of: <appendix><section><section><para>
272 "<systemitem role=\"package\">debhelper</systemitem> is a collection of "
273 "programs which can be used in <filename>debian/rules</filename> to automate "
274 "common tasks related to building binary Debian packages. <systemitem role="
275 "\"package\">debhelper</systemitem> includes programs to install various "
276 "files into your package, compress files, fix file permissions, and integrate "
277 "your package with the Debian menu system."
280 # type: Content of: <appendix><section><section><para>
283 "Unlike some approaches, <systemitem role=\"package\">debhelper</systemitem> "
284 "is broken into several small, simple commands which act in a consistent "
285 "manner. As such, it allows more fine-grained control than some of the other "
286 "debian/rules tools."
289 # type: Content of: <appendix><section><section><para>
292 "There are a number of little <systemitem role=\"package\">debhelper</"
293 "systemitem> add-on packages, too transient to document. You can see the "
294 "list of most of them by doing <literal>apt-cache search ^dh-</literal>."
297 # type: Content of: <appendix><section><section><title>
299 msgid "<systemitem role=\"package\">debmake</systemitem>"
302 # type: Content of: <appendix><section><section><para>
305 "<systemitem role=\"package\">debmake</systemitem>, a precursor to "
306 "<systemitem role=\"package\">debhelper</systemitem>, is a more coarse-"
307 "grained <filename>debian/rules</filename> assistant. It includes two main "
308 "programs: <command>deb-make</command>, which can be used to help a "
309 "maintainer convert a regular (non-Debian) source archive into a Debian "
310 "source package; and <command>debstd</command>, which incorporates in one big "
311 "shot the same sort of automated functions that one finds in <systemitem role="
312 "\"package\">debhelper</systemitem>."
315 # type: Content of: <appendix><section><section><para>
318 "The consensus is that <systemitem role=\"package\">debmake</systemitem> is "
319 "now deprecated in favor of <systemitem role=\"package\">debhelper</"
320 "systemitem>. It is a bug to use <systemitem role=\"package\">debmake</"
321 "systemitem> in new packages. New packages using <systemitem role=\"package"
322 "\">debmake</systemitem> will be rejected from the archive."
325 # type: Content of: <appendix><section><section><title>
327 msgid "<systemitem role=\"package\">dh-make</systemitem>"
330 # type: Content of: <appendix><section><section><para>
333 "The <systemitem role=\"package\">dh-make</systemitem> package contains "
334 "<command>dh_make</command>, a program that creates a skeleton of files "
335 "necessary to build a Debian package out of a source tree. As the name "
336 "suggests, <command>dh_make</command> is a rewrite of <systemitem role="
337 "\"package\">debmake</systemitem> and its template files use dh_* programs "
338 "from <systemitem role=\"package\">debhelper</systemitem>."
341 # type: Content of: <appendix><section><section><para>
344 "While the rules files generated by <command>dh_make</command> are in general "
345 "a sufficient basis for a working package, they are still just the "
346 "groundwork: the burden still lies on the maintainer to finely tune the "
347 "generated files and make the package entirely functional and Policy-"
351 # type: Content of: <appendix><section><section><title>
353 msgid "<systemitem role=\"package\">yada</systemitem>"
356 # type: Content of: <appendix><section><section><para>
359 "<systemitem role=\"package\">yada</systemitem> is another packaging helper "
360 "tool. It uses a <filename>debian/packages</filename> file to auto-generate "
361 "<filename>debian/rules</filename> and other necessary files in the "
362 "<filename>debian/</filename> subdirectory. The <filename>debian/packages</"
363 "filename> file contains instruction to build packages and there is no need "
364 "to create any <filename>Makefile</filename> files. There is possibility to "
365 "use macro engine similar to the one used in SPECS files from RPM source "
369 # type: Content of: <appendix><section><section><para>
372 "For more informations see <literal><ulink url=\"http://yada.alioth.debian."
373 "org/\">YADA site</ulink></literal>."
376 # type: Content of: <appendix><section><section><title>
378 msgid "<systemitem role=\"package\">equivs</systemitem>"
381 # type: Content of: <appendix><section><section><para>
384 "<systemitem role=\"package\">equivs</systemitem> is another package for "
385 "making packages. It is often suggested for local use if you need to make a "
386 "package simply to fulfill dependencies. It is also sometimes used when "
387 "making ``meta-packages'', which are packages whose only purpose is to depend "
391 # type: Content of: <appendix><section><title>
393 msgid "Package builders"
396 # type: Content of: <appendix><section><para>
399 "The following packages help with the package building process, general "
400 "driving <command>dpkg-buildpackage</command> as well as handling supporting "
404 # type: Content of: <appendix><section><section><title>
406 msgid "<systemitem role=\"package\">cvs-buildpackage</systemitem>"
409 # type: Content of: <appendix><section><section><para>
412 "<systemitem role=\"package\">cvs-buildpackage</systemitem> provides the "
413 "capability to inject or import Debian source packages into a CVS repository, "
414 "build a Debian package from the CVS repository, and helps in integrating "
415 "upstream changes into the repository."
418 # type: Content of: <appendix><section><section><para>
421 "These utilities provide an infrastructure to facilitate the use of CVS by "
422 "Debian maintainers. This allows one to keep separate CVS branches of a "
423 "package for <literal>stable</literal>, <literal>unstable</literal> and "
424 "possibly <literal>experimental</literal> distributions, along with the other "
425 "benefits of a version control system."
428 # type: Content of: <appendix><section><section><title>
430 msgid "<systemitem role=\"package\">debootstrap</systemitem>"
433 # type: Content of: <appendix><section><section><para>
436 "The <systemitem role=\"package\">debootstrap</systemitem> package and script "
437 "allows you to bootstrap a Debian base system into any part of your "
438 "filesystem. By base system, we mean the bare minimum of packages required "
439 "to operate and install the rest of the system."
442 # type: Content of: <appendix><section><section><para>
445 "Having a system like this can be useful in many ways. For instance, you can "
446 "<command>chroot</command> into it if you want to test your build "
447 "dependencies. Or you can test how your package behaves when installed into "
448 "a bare base system. Chroot builders use this package; see below."
451 # type: Content of: <appendix><section><section><title>
453 msgid "<systemitem role=\"package\">pbuilder</systemitem>"
456 # type: Content of: <appendix><section><section><para>
459 "<systemitem role=\"package\">pbuilder</systemitem> constructs a chrooted "
460 "system, and builds a package inside the chroot. It is very useful to check "
461 "that a package's build-dependencies are correct, and to be sure that "
462 "unnecessary and wrong build dependencies will not exist in the resulting "
466 # type: Content of: <appendix><section><section><para>
469 "A related package is <systemitem role=\"package\">pbuilder-uml</systemitem>, "
470 "which goes even further by doing the build within a User Mode Linux "
474 # type: Content of: <appendix><section><section><title>
476 msgid "<systemitem role=\"package\">sbuild</systemitem>"
479 # type: Content of: <appendix><section><section><para>
482 "<systemitem role=\"package\">sbuild</systemitem> is another automated "
483 "builder. It can use chrooted environments as well. It can be used stand-"
484 "alone, or as part of a networked, distributed build environment. As the "
485 "latter, it is part of the system used by porters to build binary packages "
486 "for all the available architectures. See <xref linkend=\"wanna-build\"/> "
487 "for more information, and <ulink url=\"&url-buildd;\"></ulink> to see the "
491 # type: Content of: <appendix><section><title>
493 msgid "Package uploaders"
496 # type: Content of: <appendix><section><para>
499 "The following packages help automate or simplify the process of uploading "
500 "packages into the official archive."
503 # type: Content of: <appendix><section><section><title>
505 msgid "<systemitem role=\"package\">dupload</systemitem>"
508 # type: Content of: <appendix><section><section><para>
511 "<systemitem role=\"package\">dupload</systemitem> is a package and a script "
512 "to automatically upload Debian packages to the Debian archive, to log the "
513 "upload, and to send mail about the upload of a package. You can configure "
514 "it for new upload locations or methods."
517 # type: Content of: <appendix><section><section><title>
519 msgid "<systemitem role=\"package\">dput</systemitem>"
522 # type: Content of: <appendix><section><section><para>
525 "The <systemitem role=\"package\">dput</systemitem> package and script does "
526 "much the same thing as <systemitem role=\"package\">dupload</systemitem>, "
527 "but in a different way. It has some features over <systemitem role=\"package"
528 "\">dupload</systemitem>, such as the ability to check the GnuPG signature "
529 "and checksums before uploading, and the possibility of running "
530 "<command>dinstall</command> in dry-run mode after the upload."
533 # type: Content of: <appendix><section><section><title>
535 msgid "<systemitem role=\"package\">dcut</systemitem>"
538 # type: Content of: <appendix><section><section><para>
541 "The <systemitem role=\"package\">dcut</systemitem> script (part of the "
542 "package <xref linkend=\"dput\"/> ) helps in removing files from the ftp "
546 # type: Content of: <appendix><section><title>
548 msgid "Maintenance automation"
551 # type: Content of: <appendix><section><para>
554 "The following tools help automate different maintenance tasks, from adding "
555 "changelog entries or signature lines and looking up bugs in Emacs to making "
556 "use of the newest and official <filename>config.sub</filename>."
559 # type: Content of: <appendix><section><section><title>
561 msgid "<systemitem role=\"package\">devscripts</systemitem>"
564 # type: Content of: <appendix><section><section><para>
567 "<systemitem role=\"package\">devscripts</systemitem> is a package containing "
568 "wrappers and tools which are very helpful for maintaining your Debian "
569 "packages. Example scripts include <command>debchange</command> and "
570 "<command>dch</command>, which manipulate your <filename>debian/changelog</"
571 "filename> file from the command-line, and <command>debuild</command>, which "
572 "is a wrapper around <command>dpkg-buildpackage</command>. The <command>bts</"
573 "command> utility is also very helpful to update the state of bug reports on "
574 "the command line. <command>uscan</command> can be used to watch for new "
575 "upstream versions of your packages. <command>debrsign</command> can be used "
576 "to remotely sign a package prior to upload, which is nice when the machine "
577 "you build the package on is different from where your GPG keys are."
580 # type: Content of: <appendix><section><section><para>
583 "See the <citerefentry> <refentrytitle>devscripts</refentrytitle> "
584 "<manvolnum>1</manvolnum> </citerefentry> manual page for a complete list of "
588 # type: Content of: <appendix><section><section><title>
590 msgid "<systemitem role=\"package\">autotools-dev</systemitem>"
593 # type: Content of: <appendix><section><section><para>
596 "<systemitem role=\"package\">autotools-dev</systemitem> contains best "
597 "practices for people who maintain packages which use <command>autoconf</"
598 "command> and/or <command>automake</command>. Also contains canonical "
599 "<filename>config.sub</filename> and <filename>config.guess</filename> files "
600 "which are known to work on all Debian ports."
603 # type: Content of: <appendix><section><section><title>
605 msgid "<systemitem role=\"package\">dpkg-repack</systemitem>"
608 # type: Content of: <appendix><section><section><para>
611 "<command>dpkg-repack</command> creates Debian package file out of a package "
612 "that has already been installed. If any changes have been made to the "
613 "package while it was unpacked (e.g., files in <filename>/etc</filename> were "
614 "modified), the new package will inherit the changes."
617 # type: Content of: <appendix><section><section><para>
620 "This utility can make it easy to copy packages from one computer to another, "
621 "or to recreate packages which are installed on your system but no longer "
622 "available elsewhere, or to save the current state of a package before you "
626 # type: Content of: <appendix><section><section><title>
628 msgid "<systemitem role=\"package\">alien</systemitem>"
631 # type: Content of: <appendix><section><section><para>
634 "<command>alien</command> converts binary packages between various packaging "
635 "formats, including Debian, RPM (RedHat), LSB (Linux Standard Base), Solaris, "
636 "and Slackware packages."
639 # type: Content of: <appendix><section><section><title>
641 msgid "<systemitem role=\"package\">debsums</systemitem>"
644 # type: Content of: <appendix><section><section><para>
647 "<command>debsums</command> checks installed packages against their MD5 "
648 "sums. Note that not all packages have MD5 sums, since they aren't required "
652 # type: Content of: <appendix><section><section><title>
654 msgid "<systemitem role=\"package\">dpkg-dev-el</systemitem>"
657 # type: Content of: <appendix><section><section><para>
660 "<systemitem role=\"package\">dpkg-dev-el</systemitem> is an Emacs lisp "
661 "package which provides assistance when editing some of the files in the "
662 "<filename>debian</filename> directory of your package. For instance, there "
663 "are handy functions for listing a package's current bugs, and for finalizing "
664 "the latest entry in a <filename>debian/changelog</filename> file."
667 # type: Content of: <appendix><section><section><title>
669 msgid "<systemitem role=\"package\">dpkg-depcheck</systemitem>"
672 # type: Content of: <appendix><section><section><para>
675 "<command>dpkg-depcheck</command> (from the <systemitem role=\"package"
676 "\">devscripts</systemitem> package, <xref linkend=\"devscripts\"/> ) runs a "
677 "command under <command>strace</command> to determine all the packages that "
678 "were used by the said command."
681 # type: Content of: <appendix><section><section><para>
684 "For Debian packages, this is useful when you have to compose a "
685 "<literal>Build-Depends</literal> line for your new package: running the "
686 "build process through <command>dpkg-depcheck</command> will provide you with "
687 "a good first approximation of the build-dependencies. For example:"
690 # type: Content of: <appendix><section><section><screen>
695 "dpkg-depcheck -b debian/rules build\n"
698 # type: Content of: <appendix><section><section><para>
701 "<command>dpkg-depcheck</command> can also be used to check for run-time "
702 "dependencies, especially if your package uses exec(2) to run other programs."
705 # type: Content of: <appendix><section><section><para>
708 "For more information please see <citerefentry> <refentrytitle>dpkg-depcheck</"
709 "refentrytitle> <manvolnum>1</manvolnum> </citerefentry>."
712 # type: Content of: <appendix><section><title>
714 msgid "Porting tools"
717 # type: Content of: <appendix><section><para>
719 msgid "The following tools are helpful for porters and for cross-compilation."
722 # type: Content of: <appendix><section><section><title>
724 msgid "<systemitem role=\"package\">quinn-diff</systemitem>"
727 # type: Content of: <appendix><section><section><para>
730 "<systemitem role=\"package\">quinn-diff</systemitem> is used to locate the "
731 "differences from one architecture to another. For instance, it could tell "
732 "you which packages need to be ported for architecture <replaceable>Y</"
733 "replaceable>, based on architecture <replaceable>X</replaceable>."
736 # type: Content of: <appendix><section><section><title>
738 msgid "<systemitem role=\"package\">dpkg-cross</systemitem>"
741 # type: Content of: <appendix><section><section><para>
744 "<systemitem role=\"package\">dpkg-cross</systemitem> is a tool for "
745 "installing libraries and headers for cross-compiling in a way similar to "
746 "<systemitem role=\"package\">dpkg</systemitem>. Furthermore, the "
747 "functionality of <command>dpkg-buildpackage</command> and <command>dpkg-"
748 "shlibdeps</command> is enhanced to support cross-compiling."
751 # type: Content of: <appendix><section><title>
753 msgid "Documentation and information"
756 # type: Content of: <appendix><section><para>
759 "The following packages provide information for maintainers or help with "
760 "building documentation."
763 # type: Content of: <appendix><section><section><title>
765 msgid "<systemitem role=\"package\">debiandoc-sgml</systemitem>"
768 # type: Content of: <appendix><section><section><para>
771 "<systemitem role=\"package\">debiandoc-sgml</systemitem> provides the "
772 "DebianDoc SGML DTD, which is commonly used for Debian documentation. This "
773 "manual, for instance, is written in DebianDoc. It also provides scripts for "
774 "building and styling the source to various output formats."
777 # type: Content of: <appendix><section><section><para>
780 "Documentation for the DTD can be found in the <systemitem role=\"package"
781 "\">debiandoc-sgml-doc</systemitem> package."
784 # type: Content of: <appendix><section><section><title>
786 msgid "<systemitem role=\"package\">debian-keyring</systemitem>"
789 # type: Content of: <appendix><section><section><para>
792 "Contains the public GPG and PGP keys of Debian developers. See <xref "
793 "linkend=\"key-maint\"/> and the package documentation for more information."
796 # type: Content of: <appendix><section><section><title>
798 msgid "<systemitem role=\"package\">debian-maintainers</systemitem>"
801 # type: Content of: <appendix><section><section><para>
804 "Contains the public GPG keys of Debian Maintainers. See <ulink url=\"&url-"
805 "wiki-dm;\"></ulink> for more information."
808 # type: Content of: <appendix><section><section><title>
810 msgid "<systemitem role=\"package\">debview</systemitem>"
813 # type: Content of: <appendix><section><section><para>
816 "<systemitem role=\"package\">debview</systemitem> provides an Emacs mode for "
817 "viewing Debian binary packages. This lets you examine a package without "