2 Author: Christian Schwarz <schwarz@debian.org>
6 Needs-Info: doc-base-files
8 Tag: postinst-should-not-set-usr-doc-link
10 Info: The technical committee chose the symlink transition method to move
11 from FSSTND to FHS. That transition has been completed with woody and thus
12 this link is no longer required.
14 Tag: maintainer-script-does-not-check-for-existence-of-updatemenus
16 Info: The maintainer script calls the <tt>update-menus</tt> command without
17 checking for existence first. (The <tt>menu</tt> package which provides the
18 command is not marked as `essential' package.)
20 For example, use the following code in your maintainer script:
21 if [ -x /usr/bin/update-menus ] ; then update-menus ; fi
23 Tag: maintainer-script-does-not-check-for-existence-of-wm-menu-config
25 Info: The maintainer script calls the <tt>wm-menu-config</tt> command without
26 checking for existence first. (The <tt>menu</tt> package which provides
27 the command is not marked as `essential' package.)
29 For example, use the following code in your maintainer script:
30 if [ -x /usr/sbin/wm-menu ]; then /usr/sbin/wm-menu-config; fi
32 Tag: maintainer-script-does-not-check-for-existence-of-installdocs
34 Info: The maintainer script calls the <tt>install-docs</tt> command without
35 checking for existence first. (The <tt>doc-base</tt> package which provides
36 the command is not marked as `essential' package.)
38 For example, use the following code in your maintainer script:
39 if [ -x /usr/sbin/install-docs ]; then
40 /usr/sbin/install-docs -i /usr/share/doc-base/<your-package>
43 Tag: maintainer-script-calls-deprecated-wm-menu-config
45 Info: The use of the wm-menu-config script is deprecated because it's
46 design had some serious flaws. Please see the menu documentation,
47 chapter 5 for more information.
49 Tag: preinst-calls-updatemenus
51 Info: The preinst script calls the <tt>update-menus</tt> command. Usually,
52 this command should be called from the <tt>postinst</tt> maintainer script.
54 Tag: preinst-calls-installdocs
56 Info: The preinst script calls the <tt>install-docs</tt> command. Usually,
57 this command should be called from the <tt>postinst</tt> maintainer script.
59 Tag: prerm-calls-updatemenus
61 Info: The prerm script calls the <tt>update-menus</tt> command. Usually,
62 this command should be called from the <tt>postrm</tt> maintainer script.
64 Tag: postrm-calls-installdocs
66 Info: The postrm script calls the <tt>install-docs</tt> command. Usually,
67 this command should be called from the <tt>prerm</tt> maintainer script.
69 Tag: executable-menu-file
71 Info: Menu files should normally not be marked as executables. You only
72 need to do this if your package has to generate menu entries dynamically.
74 Tag: menu-file-in-usr-lib
76 Info: As of menu, version 2.1.25, /usr/lib/menu as location for menu
77 files is deprecated (but still works perfectly). Menu files should
78 now be placed in /usr/share/menu instead. Only menu files that are
79 actually binary executables still need to go to /usr/lib/menu.
81 Tag: executable-in-usr-share-docbase
83 Info: Files in <tt>/usr/share/doc-base</tt> may not be marked as executables.
85 Tag: postinst-does-not-call-installdocs
87 Info: Since the package installs a file in <tt>/usr/share/doc-base</tt>, the
88 package should probably call the <tt>install-docs</tt> command in its
89 <tt>postinst</tt> script.
91 For example, use the following code in your maintainer script:
92 if [ -x /usr/sbin/install-docs ]; then
93 /usr/sbin/install-docs -i /usr/share/doc-base/<your-package>
96 Tag: prerm-does-not-call-installdocs
98 Info: Since the package installs a file in <tt>/usr/share/doc-base</tt>, the
99 package should probably call the <tt>install-docs</tt> command in its
100 <tt>prerm</tt> script.
102 For example, use the following code in your maintainer script:
103 if [ -x /usr/sbin/install-docs ]; then
104 /usr/sbin/install-docs -r <your-package> || true
107 Tag: postinst-does-not-call-updatemenus
109 Info: Since the package installs a file in either <tt>/usr/lib/menu</tt> or
110 <tt>/etc/menu-methods</tt>, the package should probably call the
111 <tt>update-menus</tt> command in it's <tt>postinst</tt> script.
113 For example, use the following code in your maintainer script:
114 if [ -x /usr/bin/update-menus ] ; then update-menus ; fi
116 Tag: postrm-does-not-call-updatemenus
118 Info: Since the package installs a file in either <tt>/usr/lib/menu</tt> or
119 <tt>/etc/menu-methods</tt>, the package should probably call the
120 <tt>update-menus</tt> command in it's <tt>postrm</tt> script.
122 For example, use the following code in your maintainer script:
123 if [ -x /usr/bin/update-menus ] ; then update-menus ; fi
125 Tag: postinst-has-useless-call-to-update-menus
127 Info: The <tt>postinst</tt> script calls the <tt>update-menus</tt> program
128 though no file is installed in <tt>/usr/lib/menu</tt> or
129 <tt>/etc/menu-methods</tt>.
131 Tag: postrm-has-useless-call-to-update-menus
133 Info: The <tt>postrm</tt> script calls the <tt>update-menus</tt> program
134 though no file is installed in <tt>/usr/lib/menu</tt> or
135 <tt>/etc/menu-methods</tt>
137 Tag: postinst-has-useless-call-to-install-docs
139 Info: The <tt>postinst</tt> script calls the <tt>install-docs</tt> program
140 though no file is installed in <tt>/usr/share/doc-base</tt>.
142 Tag: prerm-has-useless-call-to-install-docs
144 Info: The <tt>prerm</tt> script calls the <tt>install-docs</tt> program
145 though no file is installed in <tt>/usr/share/doc-base</tt>.
147 Tag: bad-menu-file-name
150 Info: The package installs a file <tt>/usr/lib/menu/menu</tt>, which is
151 already in use by the <tt>menu</tt> package itself. The menu file should
152 be named after the package that installs it.
154 Tag: doc-base-file-references-usr-doc
156 Info: Files in <tt>/usr/share/doc-base</tt> should only contain links to
157 files in the <tt>/usr/share/doc</tt> directory.
159 Tag: doc-base-index-references-multiple-files
161 Info: The Index field in a doc-base file should reference the single index
162 file for that document. Any other files belonging to the same document
163 should be listed in the Files field.
164 Ref: Debian doc-base Manual section 2.3.2.2
166 Tag: doc-base-file-references-missing-file
168 Info: One of the files referenced in an Index or Files field in this
169 doc-base control file does not exist in the package. The doc-base
170 control files should be installed by the package that provides the
171 documents they are registering.
173 Tag: doc-base-file-unknown-format
175 Info: The Format field in this doc-base control file declares a format
176 that is not supported. Recognized formats are "HTML", "Text", "PDF",
177 "PostScript", "Info", "DVI", and "DebianDoc-SGML" (case-insensitive).
178 Ref: Debian doc-base Manual section 2.3.2.2
180 Tag: doc-base-file-no-format
182 Info: A format section of this doc-base control file didn't specify a
183 format. Each section after the first must specify a format.
184 Ref: Debian doc-base Manual section 2.3.2.2
186 Tag: doc-base-file-no-format-section
188 Info: This doc-base control file didn't specify any format
190 Ref: Debian doc-base Manual section 2.3.2.2
192 Tag: doc-base-file-no-index
194 Info: Format sections in doc-base control files for HTML or Info documents
195 must contain an Index field specifying the starting document for the
196 documentation. Even if the documentation is a single file, this field
198 Ref: Debian doc-base Manual section 2.3.2.2
200 Tag: doc-base-document-field-ends-in-whitespace
202 Info: The Document field in a doc-base file should not end in whitespace.
203 doc-base (at least as of 0.8.5) cannot cope with such fields and
204 debhelper 5.0.57 or earlier may create files ending in whitespace when
205 installing such files.
207 Tag: doc-base-document-field-not-in-first-line
209 Info: The Document field in doc-base control file must be located at
210 first line of the file. While unregistering documents, doc-base 0.8
211 and later parses only the first line of the control file for performance
213 Ref: Debian doc-base Manual section 2.3.2.1
215 Tag: doc-base-file-unknown-field
217 Info: The doc-base control file contains field which is either unknown
218 or not valid for the section where was found. Possible reasons for this
219 error are: a typo in field name, missing empty line between control file
220 sections, or an extra empty line separating sections.
221 Ref: Debian doc-base Manual sections 2.3.2.1 and 2.3.2.2
223 Tag: doc-base-file-duplicated-field
225 Info: The doc-base control file contains duplicated field.
227 Tag: doc-base-file-duplicated-format
229 Info: The doc-base control file contains a duplicated format. Doc-base
230 files must not register different documents in one control file.
231 Ref: Debian doc-base Manual section 2.3.2.2
233 Tag: doc-base-file-lacks-required-field
235 Info: The doc-base control file does not contain a required field for the
237 Ref: Debian doc-base Manual sections 2.3.2.1 and 2.3.2.2
239 Tag: doc-base-invalid-document-field
241 Info: The Document field should consists only of letters (a-z), digits
242 (0-9), plus (+) or minus (-) signs, and dots (.). In particular,
243 uppercase letters are not allowed.
244 Ref: Debian doc-base Manual section 2.2
246 Tag: doc-base-abstract-field-is-template
248 Info: The Abstract field of doc-base contains a "manage online manuals"
249 phrase, which was copied verbatim from an example control file found in
250 section 2.3.1 of the Debian doc-base Manual.
252 Tag: doc-base-abstract-might-contain-extra-leading-whitespaces
254 Info: Continuation lines of the Abstract field of doc-base control file
255 should start with only one space unless they are meant to be displayed
256 verbatim by fontends.
257 Ref: Debian doc-base Manual section 2.3.2
259 Tag: doc-base-abstract-field-separator-extra-whitespaces
261 Info: Unnecessary spaces were found in the paragraph separator line of the
262 doc-base's Abstract field. The separator line should consist of a single
263 space followed by a single dot.
264 Ref: Debian doc-base Manual section 2.3.2
266 Tag: spelling-error-in-doc-base-title-field
268 Info: Lintian found a spelling or capitalization error in the Title field
269 of this doc-base control file. Lintian has a list of common misspellings
270 that it looks for. It does not have a dictionary like a spelling checker
273 Tag: spelling-error-in-doc-base-abstract-field
275 Info: Lintian found a spelling or capitalization error in the Abstract
276 field of this doc-base control file. Lintian has a list of common
277 misspellings that looks for. It does not have a dictionary like a
278 spelling checker does.
280 Tag: doc-base-file-syntax-error
282 Info: Lintian found a syntax error in the doc-base control file.
283 Ref: Debian doc-base Manual section 2.3.2.2
285 Tag: doc-base-file-separator-extra-whitespaces
287 Info: Unnecessary spaces were found in the doc-base file sections'
288 separator. The section separator is an empty line and should not contain
290 Ref: Debian doc-base Manual section 2.3.2
292 Tag: doc-base-file-uses-obsolete-national-encoding
294 Info: doc-base files must be valid UTF-8, an encoding of the Unicode
297 There are many ways to convert a doc-base file from an obsolete encoding
298 like ISO-8859-1. You may, for example, use "iconv" like:
300 $ iconv -f ISO-8859-1 -t UTF-8 doc-base > doc-base.new
301 $ mv doc-base.new doc-base
302 Ref: Debian doc-base Manual section 2.3.2
304 Tag: doc-base-unknown-section
306 Info: The section indicated in this doc-base control file is not one of
307 the standard doc-base sections. The doc-base sections are based on the
308 menu sections but are not exactly the same.
309 Ref: Debian doc-base Manual section 2.3.3
311 Tag: menu-method-should-include-menu-h
313 Info: A menu-method file must include the menu.h configuration file
314 (using "!include menu.h").
315 Ref: Debian Menu System manual section 5