12d571ab65cc863fdcae3fd1d1214391e96c4276
1 Check-Script: files
2 Author: Christian Schwarz <schwarz@debian.org>
3 Abbrev: fil
4 Type: binary, udeb
5 Needs-Info: unpacked, objdump-info, scripts, file-info, index
6 Info: This script checks if a binary package conforms to policy
7 WRT to files and directories.
9 Tag: package-contains-ancient-file
10 Severity: serious
11 Certainty: certain
12 Info: Your package contains a file that claims to have been generated
13 more than 20 years ago. This is most probably an error. Your package
14 will be rejected by the Debian archive scripts if it contains a file
15 with such a timestamp.
17 Tag: package-installs-file-to-usr-x11r6
18 Severity: important
19 Certainty: certain
20 Info: Packages using the X Window System should not be configured to install
21 files under the /usr/X11R6/ directory. Debian has switched to the modular
22 X tree which now uses regular FHS paths and all packages should follow.
23 .
24 Programs that use GNU autoconf and automake are usually easily configured
25 at compile time to use /usr/ instead of /usr/X11R6/. Packages that use
26 imake must build-depend on xutils-dev (>= 1:1.0.2-2) for the correct
27 paths.
28 Ref: policy 11.8.7
30 Tag: config-file-reserved
31 Severity: important
32 Certainty: certain
33 Info: This file is reserved by a specific package. Please email the
34 maintainer of the package in question if you have questions.
36 Tag: FSSTND-dir-in-usr
37 Severity: serious
38 Certainty: certain
39 Info: As of policy version 3.0.0.0, Debian no longer follows the FSSTND.
40 .
41 Instead, the Filesystem Hierarchy Standard (FHS), version 2.3, is
42 used. You can find it in /usr/share/doc/debian-policy/fhs/ .
43 Ref: policy 9.1.1
45 Tag: FSSTND-dir-in-var
46 Severity: serious
47 Certainty: certain
48 Info: As of policy version 3.0.0.0, Debian no longer follows the FSSTND.
49 .
50 Instead, the Filesystem Hierarchy Standard (FHS), version 2.3, is
51 used. You can find it in /usr/share/doc/debian-policy/fhs/ .
52 Ref: policy 9.1.1
54 Tag: package-installs-into-etc-gconf-schemas
55 Severity: normal
56 Certainty: certain
57 Info: The package installs files into the <tt>/etc/gconf/schemas</tt>
58 directory. No package should do this; this directory is reserved for
59 local overrides. Instead, schemas should be installed into
60 <tt>/usr/share/gconf/schemas</tt>.
62 Tag: package-installs-into-etc-rc.d
63 Severity: serious
64 Certainty: certain
65 Info: The package installs files into the <tt>/etc/rc.d</tt> or
66 <tt>/etc/rc?.d</tt> which is not allowed.
67 Ref: policy 9.3.3
69 Tag: package-installs-into-etc-rc.boot
70 Severity: serious
71 Certainty: certain
72 Info: The package installs files in the <tt>/etc/rc.boot</tt> directory,
73 which is obsolete. See rc.boot(5) for details.
74 Ref: policy 9.3.4
76 Tag: non-standard-file-permissions-for-etc-init.d-script
77 Severity: important
78 Certainty: certain
79 Info: Usually, scripts in the <tt>/etc/init.d</tt> directory should have
80 mode 0755.
82 Tag: file-directly-in-usr-share
83 Severity: serious
84 Certainty: certain
85 Info: Packages should not install files directly in <tt>/usr/share</tt>,
86 i.e., without a subdirectory.
87 .
88 You should either create a subdirectory <tt>/usr/share/...</tt> for your
89 package or place the file in <tt>/usr/share/misc</tt>.
91 Tag: file-in-usr-local
92 Severity: serious
93 Certainty: certain
94 Info: The package installs a file in <tt>/usr/local/...</tt> which is
95 not allowed.
96 Ref: policy 9.1.2
98 Tag: stray-directory-in-manpage-directory
99 Severity: important
100 Certainty: certain
101 Info: This package installs a directory under <tt>/usr/share/man</tt> or
102 <tt>/usr/X11R6/man</tt> that isn't a manual section directory or locale
103 directory.
104 Ref: fhs usrsharemanmanualpages
106 Tag: executable-manpage
107 Severity: important
108 Certainty: certain
109 Info: Manual pages are not meant to be executed.
111 Tag: dir-in-usr-local
112 Severity: serious
113 Certainty: certain
114 Info: The package installs a directory in <tt>/usr/local/...</tt> which is
115 not allowed.
116 .
117 If you want to provide an empty directory in <tt>/usr/local</tt> for
118 convenience of the local system administrator, please follow the rules
119 in the policy manual (section 9.1.2), i.e., create the directories in
120 the postinst script but don't fail if this isn't possible (e.g., if
121 <tt>/usr/local</tt> is mounted read-only).
122 Ref: policy 9.1.2
124 Tag: non-standard-dir-perm
125 Severity: normal
126 Certainty: possible
127 Info: The directory has a mode different from 0755, and it's not one of the
128 known exceptions.
129 Ref: policy 10.9
131 Tag: executable-is-not-world-readable
132 Severity: normal
133 Certainty: certain
134 Info: All executables should be readable by any user. Since anyone can
135 download the Debian package and obtain a copy of the executable, no
136 security is gained by making the executable unreadable even for setuid
137 binaries. If only members of a certain group may execute this file,
138 remove execute permission for world, but leave read permission.
139 Ref: policy 10.9
141 Tag: non-standard-executable-perm
142 Severity: normal
143 Certainty: certain
144 Info: Executables that are not setuid or setgid should always have a mode
145 of 0755. Since anyone can obtain the executable by downloading the
146 Debian package and extracting it, restricting access serves little
147 purpose.
148 Ref: policy 10.9
150 Tag: non-standard-game-executable-perm
151 Severity: normal
152 Certainty: certain
153 Info: The file is owned by the games group but is not mode 2755. If a
154 game does not have to be setgid games, it should be owned by the root
155 group like any other executable. This executable is either owned by the
156 wrong group or is not setgid when it should be.
157 Ref: policy 11.11
159 Tag: non-standard-setuid-executable-perm
160 Severity: normal
161 Certainty: certain
162 Info: The file is setuid or setgid and has a mode different from any of
163 2755, 4755, 4754, or 6755. Any other permissions on setuid executables
164 is probably a bug. In particular, removing root write privileges serves
165 no purpose, group-writable setuid or setgid executables are probably bad
166 ideas, and setgid executables that are not world-executable serve little
167 purpose.
168 Ref: policy 10.9
170 Tag: setuid-binary
171 Severity: normal
172 Certainty: possible
173 Info: The file is tagged SETUID. In some cases this is intentional, but in
174 other cases this is a bug. If this is intentional, please add a lintian
175 override to document this fact.
177 Tag: setgid-binary
178 Severity: normal
179 Certainty: possible
180 Info: The file is tagged SETGID. In some cases this is intentional, but in
181 other cases this is a bug. If this is intentional, please add a lintian
182 override to document this fact.
184 Tag: setuid-gid-binary
185 Severity: normal
186 Certainty: possible
187 Info: The file is tagged SETUID and SETGID. In some cases this is
188 intentional, but in other cases this is a bug. If this is intentional,
189 please add a lintian override to document this fact.
191 Tag: non-standard-file-perm
192 Severity: normal
193 Certainty: certain
194 Info: The file has a mode different from 0644. In some cases this is
195 intentional, but in other cases this is a bug.
196 Ref: policy 10.9
198 Tag: bad-perm-for-file-in-etc-sudoers.d
199 Severity: serious
200 Certainty: certain
201 Info: Files in /etc/sudoers.d/ must be 0440 or sudo will refuse to
202 parse them.
203 Ref: #588831, #576527
205 Tag: special-file
206 Severity: serious
207 Certainty: certain
208 Info: The package contains a <i>special</i> file (e.g., a device file).
209 This is forbidden by current policy. If your program needs this device,
210 you should create it by calling <tt>makedev</tt> from the postinst
211 script.
212 Ref: policy 10.6
214 Tag: compressed-symlink-with-wrong-ext
215 Severity: important
216 Certainty: certain
217 Info: The package installs a symbolic link pointing to a compressed file,
218 but the symbolic link does not use the same file extension than the
219 referenced file. In most cases, this can produce troubles when the
220 user or a program tries to access the file through the link.
221 Ref: policy 10.5
223 Tag: symlink-has-double-slash
224 Severity: minor
225 Certainty: certain
226 Info: This symlink contains two successive slashes (//). This is in violation
227 of policy, where it is stated that symlinks should be as short as possible
228 .
229 If you use debhelper, running dh_link after creating the package structure
230 will fix this problem for you.
231 Ref: policy 10.5
233 Tag: symlink-ends-with-slash
234 Severity: minor
235 Certainty: certain
236 Info: This symlink ends with a slash (/). This is in violation
237 of policy, where it is stated that symlinks should be as short as possible
238 .
239 If you use debhelper, running dh_link after creating the package structure
240 will fix this problem for you.
241 Ref: policy 10.5
243 Tag: symlink-should-be-relative
244 Severity: normal
245 Certainty: certain
246 Info: Symlinks to files which are in the same top-level directory should be
247 relative according to policy. (In other words, a link in /usr to another
248 file in /usr should be relative, while a link in /usr to a file in /etc
249 should be absolute.)
250 .
251 If you use debhelper, running dh_link after creating the package structure
252 will fix this problem for you.
253 Ref: policy 10.5
255 Tag: symlink-should-be-absolute
256 Severity: important
257 Certainty: certain
258 Info: Symbolic links between different top-level directories should be
259 absolute.
260 .
261 If you use debhelper, running dh_link after creating the package structure
262 will fix this problem for you.
263 Ref: policy 10.5
265 Tag: udeb-contains-documentation-file
266 Severity: important
267 Certainty: certain
268 Info: udeb packages should not contain any documentation.
270 Tag: executable-in-usr-share-doc
271 Severity: important
272 Certainty: certain
273 Info: Usually, documentation files in <tt>/usr/share/doc</tt> should have mode
274 0644. If the executable is an example, it should go in
275 <tt>/usr/share/doc/<i>pkg</i>/examples</tt>.
277 Tag: script-in-usr-share-doc
278 Severity: wishlist
279 Certainty: certain
280 Info: Scripts are usually not documentation files, unless they are
281 examples, in which case they should be in the
282 <tt>/usr/share/doc/<i>pkg</i>/examples</tt> directory.
284 Tag: symlink-has-too-many-up-segments
285 Severity: serious
286 Certainty: certain
287 Ref: policy 10.5
288 Info: The symlink references a directory beyond the root directory "/".
290 Tag: lengthy-symlink
291 Severity: important
292 Certainty: certain
293 Info: This link goes up, and then back down into the same subdirectory.
294 Making it shorter will improve its chances of finding the right file
295 if the user's system has lots of symlinked directories.
296 .
297 If you use debhelper, running dh_link after creating the package structure
298 will fix this problem for you.
299 Ref: policy 10.5
301 Tag: symlink-is-self-recursive
302 Severity: normal
303 Certainty: possible
304 Info: The symbolic link is recursive to a higher directory of the symlink
305 itself. This means, that you can infinitely chdir with this symlink. This is
306 usually not okay, but sometimes wanted behaviour.
308 Tag: symlink-contains-spurious-segments
309 Severity: important
310 Certainty: certain
311 Info: The symbolic link has needless segments like ".." and "." in the
312 middle. These are unneeded and make the link longer than it could be,
313 which is in violation of policy. They can also cause problems in the
314 presence of symlinked directories.
315 .
316 If you use debhelper, running dh_link after creating the package structure
317 will fix this problem for you.
318 Ref: policy 10.5
320 Tag: run-parts-cron-filename-contains-illegal-chars
321 Severity: normal
322 Certainty: certain
323 Info: The script in /etc/cron.<time-interval> will not be executed by
324 run-parts(8) because the filename contains a "." (full stop) or "+" (plus).
325 .
326 It is recommended to use "_" (underscores) instead of these symbols.
327 Ref: run-parts(8), policy 9.5.1
329 Tag: bad-permissions-for-etc-cron.d-script
330 Severity: important
331 Certainty: certain
332 Info: Files in <tt>/etc/cron.d</tt> are configuration files for cron and not
333 scripts. Thus, they should not be marked executable.
335 Tag: bad-permissions-for-etc-emacs-script
336 Severity: important
337 Certainty: certain
338 Info: Files in the <tt>/etc/emacs*</tt> directories should not be marked
339 executable.
341 Tag: image-file-in-usr-lib
342 Severity: normal
343 Certainty: certain
344 Info: This package installs a pixmap or a bitmap within <tt>/usr/lib</tt>.
345 According to the Filesystem Hierarchy Standard, architecture-independent
346 files need to be placed within <tt>/usr/share</tt> instead.
348 Tag: file-directly-in-usr-share-doc
349 Severity: serious
350 Certainty: certain
351 Info: Documentation files have to be installed in
352 <tt>/usr/share/doc/<i>pkg</i></tt>.
353 Ref: policy 12.3
355 Tag: bad-owner-for-doc-file
356 Severity: important
357 Certainty: certain
358 Info: Documentation files should be owned by <tt>root/root</tt>.
360 Tag: dir-or-file-in-var-lock
361 Severity: serious
362 Certainty: possible
363 Info: <tt>/var/lock</tt> may be a temporary filesystem, so any directories
364 or files needed there must be created dynamically at boot time.
365 Ref: policy 9.3.2
367 Tag: dir-or-file-in-var-run
368 Severity: serious
369 Certainty: possible
370 Info: <tt>/var/run</tt> may be a temporary filesystem, so any directories
371 or files needed there must be created dynamically at boot time.
372 Ref: policy 9.3.2
374 Tag: dir-or-file-in-run
375 Severity: serious
376 Certainty: possible
377 Info: <tt>/run</tt> may be a temporary filesystem, so any directories
378 or files needed there must be created dynamically at boot time.
379 Ref: policy 9.3.2
381 Tag: dir-or-file-in-var-www
382 Severity: serious
383 Certainty: possible
384 Ref: fhs thevarhierarchy
385 Info: Debian packages should not install files under <tt>/var/www</tt>.
386 This is not one of the <tt>/var</tt> directories in the File Hierarchy
387 Standard and is under the control of the local administrator. Packages
388 should not assume that it is the document root for a web server; it is
389 very common for users to change the default document root and packages
390 should not assume that users will keep any particular setting.
391 .
392 Packages that want to make files available via an installed web server
393 should instead put instructions for the local administrator in a
394 README.Debian file and ideally include configuration fragments for common
395 web servers such as Apache.
396 .
397 As an exception, packages are permitted to create the <tt>/var/www</tt>
398 directory due to its past history as the default document root, but
399 should at most copy over a default file in postinst for a new install.
400 In this case, please add a Lintian override.
402 Tag: dir-or-file-in-tmp
403 Severity: serious
404 Certainty: certain
405 Info: Packages must not install files into <tt>/tmp</tt> or
406 <tt>/var/tmp</tt>. The File Hierarchy Standard specifies that such files
407 may be removed by the administrator and that programs may not depend on
408 any files in <tt>/tmp</tt> being preserved across invocations, which
409 combined mean that it makes no sense to ship files in these directories.
410 Ref: fhs tmptemporaryfiles, fhs vartmptemporaryfilespreservedbetwee
412 Tag: dir-or-file-in-mnt
413 Severity: serious
414 Certainty: certain
415 Info: Packages should not install into <tt>/mnt</tt>. The FHS states that
416 this directory is reserved for the local system administrator for
417 temporary mounts and that it must not be used by installation programs.
418 Ref: fhs mntmountpointforatemporarilymount
420 Tag: dir-or-file-in-opt
421 Severity: serious
422 Certainty: certain
423 Info: Debian packages should not install into <tt>/opt</tt>, because it
424 is reserved for add-on software.
425 Ref: fhs optaddonapplicationsoftwarepackages
427 Tag: dir-or-file-in-etc-opt
428 Severity: serious
429 Certainty: certain
430 Info: Debian packages should not install into <tt>/etc/opt</tt>, because it
431 is reserved for add-on software.
432 Ref: fhs optaddonapplicationsoftwarepackages
434 Tag: dir-or-file-in-srv
435 Severity: serious
436 Certainty: certain
437 Info: Debian packages should not install into <tt>/srv</tt>. The
438 specification of <tt>/srv</tt> states that its structure is at the
439 discretion of the local administrator and no package should rely on any
440 particular structure. Debian packages that install files directly into
441 <tt>/srv</tt> can't adjust for local policy about its structure and in
442 essence force a particular structure.
443 .
444 If a package wishes to put its data in <tt>/srv</tt>, it must do this in
445 a way that allows the local administrator to specify and preserve their
446 chosen directory structure (such as through post-install configuration,
447 setup scripts, debconf prompting, etc.).
448 Ref: fhs srvdataforservicesprovidedbysystem
450 Tag: third-party-package-in-python-dir
451 Severity: normal
452 Certainty: certain
453 Info: Third-party Python packages should install their files in
454 <tt>/usr/lib/python<i>VERSION</i>/site-packages</tt> for Python versions
455 before 2.6 and <tt>/usr/lib/python<i>VERSION</i>/dist-packages</tt>
456 for Python 2.6 and later. All other directories in
457 <tt>/usr/lib/python<i>VERSION</i></tt> are for use by the core python
458 packages.
459 Ref: python-policy 1.5
461 Tag: perl-module-in-core-directory
462 Severity: important
463 Certainty: certain
464 Info: Packaged modules must not be installed into the core perl
465 directories as those directories change with each upstream perl
466 revision. The vendor directories are provided for this purpose.
467 Ref: perl-policy 3.1
469 Tag: backup-file-in-package
470 Severity: normal
471 Certainty: certain
472 Info: There is a file in the package whose name matches the format emacs
473 or vim uses for backup and autosave files. It may have been installed by
474 accident.
476 Tag: nfs-temporary-file-in-package
477 Severity: normal
478 Certainty: certain
479 Info: There is a file in the package whose name matches the format NFS
480 uses to temporarily save files that were deleted while another process
481 had them open. It may have been included in the package by accident
482 while building the package in an NFS filesystem.
484 Tag: windows-thumbnail-database-in-package
485 Severity: normal
486 Certainty: certain
487 Info: There is a file in the package named <tt>Thumbs.db</tt> or
488 <tt>Thumbs.db.gz</tt>, which is normally a Windows image thumbnail
489 database. Such databases are generally useless in Debian packages and
490 were usually accidentally included by copying complete directories from
491 the source tarball.
493 Tag: macos-ds-store-file-in-package
494 Severity: normal
495 Certainty: certain
496 Info: There is a file in the package named <tt>.DS_Store</tt> or
497 <tt>.DS_Store.gz</tt>, the file name used by Mac OS X to store folder
498 attributes. Such files are generally useless in Debian packages and were
499 usually accidentally included by copying complete directories from the
500 source tarball.
502 Tag: macos-resource-fork-file-in-package
503 Severity: normal
504 Certainty: certain
505 Info: There is a file in the package with a name starting with
506 <tt>._</tt>, the file name pattern used by Mac OS X to store resource
507 forks in non-native file systems. Such files are generally useless in
508 Debian packages and were usually accidentally included by copying
509 complete directories from the source tarball.
511 Tag: package-installs-perllocal-pod
512 Severity: normal
513 Certainty: certain
514 Info: This package installs a file <tt>perllocal.pod</tt>. Since that
515 file is intended for local documentation, it is not likely that it is
516 a good place for documentation supplied by a Debian package. In fact,
517 installing this package will wipe out whatever local documentation
518 existed there.
520 Tag: extra-license-file
521 Severity: normal
522 Certainty: possible
523 Ref: policy 12.5
524 Info: All license information should be collected in the
525 <tt>debian/copyright</tt> file. This usually makes it unnecessary
526 for the package to install this information in other places as well.
528 Tag: non-standard-toplevel-dir
529 Severity: important
530 Certainty: certain
531 Info: The Filesystem Hierarchy Standard forbids the installation of new
532 files or directories in the root directory.
533 Ref: fhs therootfilesystem
535 Tag: subdir-in-bin
536 Severity: serious
537 Certainty: certain
538 Info: The Filesystem Hierarchy Standard forbids the installation of new
539 directories in <tt>/bin</tt>.
540 Ref: fhs binessentialusercommandbinaries
542 Tag: subdir-in-usr-bin
543 Severity: serious
544 Certainty: certain
545 Info: The Filesystem Hierarchy Standard forbids the installation of new
546 directories in <tt>/usr/bin</tt> other than <tt>/usr/bin/mh</tt>.
547 Ref: fhs usrbinmostusercommands
549 Tag: non-standard-dir-in-usr
550 Severity: normal
551 Certainty: certain
552 Info: The FHS says "No large software packages should use a direct
553 subdirectory under the <tt>/usr</tt> hierarchy". This package contains
554 a directory in <tt>/usr</tt> that is not mentioned in the Filesystem
555 Hierarchy Standard.
556 Ref: fhs theusrhierarchy
558 Tag: non-standard-dir-in-var
559 Severity: important
560 Certainty: certain
561 Info: The FHS says "Applications should generally not add directories to
562 the top level of <tt>/var</tt>. Such directories should only be added
563 if they have some system-wide implication, and in consultation with the
564 FHS mailing list."
565 Ref: fhs thevarhierarchy
567 Tag: use-of-compat-symlink
568 Severity: important
569 Certainty: certain
570 Info: This package uses a directory that, according to the Filesystem
571 Hierarchy Standard, should exist only as a compatibility symlink.
572 Packages should not traverse such symlinks when installing files, they
573 should use the standard directories instead.
575 Tag: file-in-unusual-dir
576 Severity: normal
577 Certainty: certain
578 Info: This file or symbolic link is in a directory where files are not
579 normally installed by Debian packages.
581 Tag: package-installs-packlist
582 Severity: important
583 Certainty: certain
584 Info: Packages built using the perl MakeMaker package will have a file
585 named .packlist in them. Those files are useless, and (in some cases)
586 have the additional problem of creating an architecture-specific
587 directory name in an architecture-independent package.
588 .
589 They can be suppressed by adding the following to <tt>debian/rules</tt>:
590 .
591 find debian/<i>pkg</i> -type f -name .packlist -delete
592 .
593 or by telling MakeMaker to use vendor install dirs; consult a recent
594 version of Perl policy. Perl 5.6.0-12 or higher supports this.
595 Ref: perl-policy 4.1
597 Tag: zero-byte-file-in-doc-directory
598 Severity: normal
599 Certainty: possible
600 Info: The documentation directory for this package contains an empty
601 file. This is often due to installing an upstream NEWS or README file
602 without realizing it's empty and hence not useful.
603 .
604 Files in the examples subdirectory are excluded from this check, but
605 there are some cases where empty files are legitimate parts of the
606 documentation without being examples. In those cases, please add an
607 override.
609 Tag: override-file-in-wrong-location
610 Severity: important
611 Certainty: certain
612 Info: Lintian overrides should be put in a regular file named
613 /usr/share/lintian/overrides/<tt>package</tt>, not in a subdirectory
614 named for the package or in the obsolete location under /usr/share/doc.
615 See the Lintian documentation for more information on proper naming and
616 format.
617 Ref: lintian 2.4
619 Tag: package-contains-upstream-install-documentation
620 Severity: normal
621 Certainty: possible
622 Ref: policy 12.3
623 Info: Binary packages do not need to contain the instructions for building
624 and installing the package as this info is not needed by package users.
625 If the info contained is important for configuration perhaps it could be
626 summarized in README.Debian, otherwise an override may be added.
628 Tag: package-contains-hardlink
629 Severity: normal
630 Certainty: certain
631 Info: The package contains a hardlink in <tt>/etc</tt> or across different
632 directories. This might not work at all if directories are on different
633 filesystems (which can happen anytime as the system administrator sees fit),
634 certain filesystems such as AFS don't even support cross-directory hardlinks
635 at all.
636 .
637 For configuration files, certain editors might break hardlinks, and so
638 does dpkg in certain cases.
639 .
640 A better solution might be using symlinks here.
641 Ref: policy 10.7.3
643 Tag: package-contains-bts-control-dir
644 Severity: normal
645 Certainty: certain
646 Info: The package contains a control directory for a bug tracking system.
647 It was most likely installed by accident, since bug tracking directories
648 usually don't belong in packages.
650 Tag: package-contains-vcs-control-dir
651 Severity: normal
652 Certainty: certain
653 Info: The package contains a control directory for a version control system.
654 It was most likely installed by accident, since version control directories
655 usually don't belong in packages.
657 Tag: package-contains-xvpics-dir
658 Severity: important
659 Certainty: certain
660 Info: Package contains a .xvpics directory. It was most likely installed by
661 accident, since thumbnails usually don't belong in packages.
663 Tag: package-contains-vcs-control-file
664 Severity: normal
665 Certainty: certain
666 Info: The package contains a VCS control file such as .(cvs|git|hg)ignore.
667 Files such as these are used by revision control systems to, for example,
668 specify untracked files it should ignore or inventory files. This file
669 is generally useless in an installed package and was probably installed
670 by accident.
672 Tag: svn-commit-file-in-package
673 Severity: normal
674 Certainty: certain
675 Info: The package contains an svn-commit(.NNN).tmp file. This file is
676 almost certainly a left-over from a failed Subversion commit, and does
677 not belong in a Debian package.
679 Tag: svk-commit-file-in-package
680 Severity: normal
681 Certainty: certain
682 Info: The package contains an svk-commitNNN.tmp file. This file is almost
683 certainly a left-over from a failed Subversion commit, and does not
684 belong in a Debian package.
686 Tag: nested-examples-directory
687 Severity: important
688 Certainty: certain
689 Info: Package contains a <tt>usr/share/doc/something/examples/examples</tt>
690 directory. It was most likely installed by accident, since one examples/
691 directory should be enough for everybody(tm).
693 Tag: package-installs-nonbinary-perl-in-usr-lib-perl5
694 Severity: normal
695 Certainty: certain
696 Info: Architecture-independent Perl code should be placed in
697 <tt>/usr/share/perl5</tt>, not <tt>/usr/lib/perl5</tt>
698 unless there is at least one architecture-dependent file
699 in the module.
700 Ref: perl-policy 2.3
702 Tag: file-in-usr-lib-site-python
703 Severity: important
704 Certainty: certain
705 Ref: python-policy 1.5
706 Info: The directory /usr/lib/site-python has been deprecated as a
707 location for installing Python modules and may be dropped from Python's
708 module search path in a future version. Most likely this module is a
709 private module and should be packaged in a directory outside of Python's
710 default search path.
712 Tag: python-module-in-wrong-location
713 Severity: normal
714 Certainty: possible
715 Ref: python-policy 1.5, #576012
716 Info: The package installs a Python module or debug information for a Python
717 module in the wrong location for the given version of Python.
718 .
719 dh_python3 can be used to fix this for Python 3 modules.
721 Tag: python-debug-in-wrong-location
722 Severity: normal
723 Certainty: possible
724 Ref: #576014
725 Info: The package appears to be installing debug modules in
726 /usr/lib/debug/usr/lib/pyshared/pythonX.Y/. However, gdb(1)
727 will not look for it there, making it less useful. The file
728 should be installed in /usr/lib/debug/usr/lib/pymodules/pythonX.Y/
729 instead.
731 Tag: missing-dependency-on-python-central
732 Severity: important
733 Certainty: possible
734 Ref: #592533
735 Info: The package installs a file with the package name in
736 /usr/share/pyshared-data/ without depending on python-central (>= 0.6).
737 .
738 This can happen if ${python:Depends} was omitted from the Depends field
739 in debian/control.
741 Tag: missing-dependency-on-python-support
742 Severity: important
743 Certainty: possible
744 Info: The package installs a file in usr/share/python-support/ but does
745 not declare the necessary dependency on python-support.
746 .
747 This can happen if ${python:Depends} was omitted from the Depends field
748 in debian/control.
750 Tag: package-installs-python-bytecode
751 Severity: serious
752 Certainty: certain
753 Ref: python-policy 2.6
754 Info: Compiled python source files must not be included in the package.
755 These files should be removed from the package and created at package
756 installation time in the postinst.
758 Tag: package-installs-python-egg
759 Severity: serious
760 Certainty: possible
761 Ref: python-policy 2.6
762 Info: Python eggs should not be installed, since the Debian package is
763 supposed to do the required steps for installing the Python code.
764 .
765 The egg may contain pre-compiled python bytecode or shared libraries.
767 Tag: package-installs-python-pycache-dir
768 Severity: serious
769 Certainty: certain
770 Ref: python-policy 2.6
771 Info: The package installs a __pycache__ directory, which is normally
772 only used to store compiled python source files. Compiled python
773 source files must not be included in the package, instead they
774 should be generated at installation time in the postinst.
775 .
776 Note this tag is issues even if the directory is empty.
778 Tag: bad-permissions-for-ali-file
779 Severity: normal
780 Certainty: certain
781 Ref: policy 8.4
782 Info: Ada Library Information (*.ali) files are required to be read-only
783 (mode 0444) by GNAT.
784 .
785 If at least one user can write the *.ali file, GNAT considers whether
786 or not to recompile the corresponding source file. Such recompilation
787 would fail because normal users don't have write permission on the
788 files. Moreover, such recompilation would defeat the purpose of
789 library packages, which provide *.a and *.so libraries to link against).
791 Tag: package-contains-readme-for-other-platform-or-distro
792 Severity: normal
793 Certainty: certain
794 Info: package contains a README.(platform) file that contains instructions
795 specific to a platform or distribution other than Debian and thus can
796 most likely be removed. If it contains information that pertains to
797 Debian, please consider renaming it, or including it in an already
798 existing README file.
800 Tag: desktop-file-in-wrong-dir
801 Severity: normal
802 Certainty: certain
803 Info: The package contains a .desktop file in an obsolete directory.
804 According to the menu-spec draft on freedesktop.org, those .desktop files
805 that are intended to create a menu should be placed in
806 <tt>/usr/share/applications</tt>, not <tt>/usr/share/gnome/apps</tt>.
808 Tag: script-with-language-extension
809 Severity: normal
810 Certainty: certain
811 Info: When scripts are installed into a directory in the system PATH, the
812 script name should not include an extension such as <tt>.sh</tt> or
813 <tt>.pl</tt> that denotes the scripting language currently used to
814 implement it. The implementation language may change; if it does,
815 leaving the name the same would be confusing and changing it would be
816 disruptive.
817 Ref: policy 10.4
819 Tag: file-in-usr-lib-sgml
820 Severity: normal
821 Certainty: certain
822 Ref: fhs theusrhierarchy
823 Info: This package installs a file in <tt>/usr/lib/sgml</tt>. This was
824 the old location for SGML catalogs and similar flies. All those files
825 should now go into <tt>/usr/share/sgml</tt>.
827 Tag: file-name-ends-in-whitespace
828 Severity: normal
829 Certainty: possible
830 Info: This package installs a file or directory whose name ends in
831 whitespace. This might be intentional but it's normally a mistake. If
832 it is intentional, add a lintian override.
833 .
834 One possible cause is using debhelper 5.0.57 or earlier to install a
835 doc-base file with a Document field that ends in whitespace.
837 Tag: package-contains-empty-directory
838 Severity: wishlist
839 Certainty: possible
840 Info: This package installs an empty directory. This might be intentional
841 but it's normally a mistake. If it is intentional, add a lintian override.
842 .
843 If a package ships with or installs empty directories, you can remove them
844 in debian/rules by calling:
845 .
846 $ find path/to/base/dir -type d -empty -delete
848 Tag: package-section-games-but-contains-no-game
849 Severity: important
850 Certainty: certain
851 Ref: policy 11.11
852 Info: This package is marked as part of the section games, but doesn't
853 contain files in <tt>/usr/games</tt>. Binaries of games must be installed
854 in <tt>/usr/games</tt>.
856 Tag: package-section-games-but-has-usr-bin
857 Severity: normal
858 Certainty: possible
859 Ref: policy 11.11
860 Info: This package is marked as part of the section games, but contains
861 executables in <tt>/bin</tt> or <tt>/usr/bin/</tt>. This can be intentional,
862 but is usually a mistake.
864 Tag: games-package-should-be-section-games
865 Severity: normal
866 Certainty: possible
867 Info: All the executables in this package are in <tt>/usr/games</tt>, but
868 the package is not in section games. This can be intentional but is
869 usually a mistake.
871 Tag: package-contains-devhelp-file-without-symlink
872 Severity: normal
873 Certainty: certain
874 Info: This package contains a *.devhelp or *.devhelp2 file which is not in
875 the devhelp search path (<tt>/usr/share/devhelp/books</tt> and
876 <tt>/usr/share/gtk-doc/html</tt>) and is apparently not in a directory
877 linked into the devhelp search path. This will prevent devhelp from
878 finding the documentation.
879 .
880 If the devhelp documentation is installed in a path outside the devhelp
881 search path (such as <tt>/usr/share/doc</tt>), create a symlink in
882 <tt>/usr/share/gtk-doc/html</tt> pointing to the documentation directory.
884 Tag: debug-package-should-be-named-dbg
885 Severity: normal
886 Certainty: certain
887 Info: This package provides at least one file in <tt>/usr/lib/debug</tt>,
888 which is intended for detached debugging symbols, but the package name
889 does not end in "-dbg". Detached debugging symbols should be put into a
890 separate package, Priority: extra, with a package name ending in "-dbg".
891 Ref: devref 6.7.9
893 Tag: package-contains-linda-override
894 Severity: normal
895 Certainty: certain
896 Info: This package contains a linda override file in
897 <tt>/usr/share/linda/overrides</tt>. Linda is obsolete and has been
898 removed from the archive as of 2008-03-04. Linda overrides should
899 probably be dropped from packages.
901 Tag: wrong-file-owner-uid-or-gid
902 Severity: serious
903 Certainty: certain
904 Info: The user or group ID of the owner of the file is invalid. The
905 owner user and group IDs must be in the set of globally allocated
906 IDs, because other IDs are dynamically allocated and might be used
907 for varying purposes on different systems, or are reserved. The set
908 of the allowed, globally allocated IDs consists of the ranges 0-99,
909 64000-64999 and 65534.
910 .
911 It's possible for a Policy-compliant package to trigger this bug if the
912 user is created in the preinst maintainer script, but this is a very rare
913 case and doesn't appear to be necessary. If you found yourself needing
914 to create a package that works this way, please file a bug against
915 Lintian to let the maintainers know.
916 Ref: policy 9.2
918 Tag: embedded-javascript-library
919 Severity: normal
920 Certainty: possible
921 Info: This package contains an embedded copy of JavaScript libraries
922 that are now available in their own packages (for example, JQuery,
923 Prototype, Mochikit or "Cropper"). Please depend on the appropriate
924 package and symlink the library into the appropriate location.
925 Ref: policy 4.13
927 Tag: embedded-feedparser-library
928 Severity: normal
929 Certainty: certain
930 Info: This package contains an embedded copy of Mark Pilgrim's Universal
931 Feed Parser. Please depend on the "python-feedparser" package and use
932 the normal Python import mechanism to load it.
933 Ref: policy 4.13
935 Tag: embedded-pear-module
936 Severity: normal
937 Certainty: possible
938 Experimental: yes
939 Info: This package appears to contain an embedded copy of a PEAR module.
940 Please depend on the respective PEAR package providing the module and
941 make sure the library can be found by the scripts via the include_path.
942 Ref: policy 4.13
944 Tag: embedded-php-library
945 Severity: normal
946 Certainty: possible
947 Info: This package appears to contain an embedded copy of a PHP library.
948 Please depend on the respective package providing the library and
949 make sure it can be found by the scripts via the include_path.
950 Ref: policy 4.13
952 Tag: windows-devel-file-in-package
953 Severity: normal
954 Certainty: possible
955 Info: This package appears to contain development files only meaningful to
956 Windows environments. Such files are generally useless in Debian packages and
957 were usually accidentally included by copying complete directories from the
958 source tarball.
960 Tag: font-in-non-font-package
961 Severity: wishlist
962 Certainty: possible
963 Info: This package contains a *.ttf, *.otf, or *.pfb file, file
964 extensions used by TrueType, OpenType, or Type 1 fonts, but the package
965 does not appear to be a dedicated font package. Dedicated font package
966 names should begin with <tt>fonts-</tt>. (Type 1 fonts are also allowed
967 in packages starting with <tt>xfonts-</tt>.) If the font is already
968 packaged, you should depend on that package instead. Otherwise, normally
969 the font should be packaged separately, since fonts are usually useful
970 outside of the package that embeds them.
972 Tag: font-adobe-copyrighted-fragment
973 Severity: serious
974 Certainty: possible
975 Info: This type 1 font file includes some postscript fragment with a
976 non free license of Adobe. In order to check if this tag is genuine
977 please follow the proceedure described in the reference.
978 .
979 Should this be a false-positive, please override the tag.
980 Ref: http://wiki.debian.org/qa.debian.org/type1nondfsg
982 Tag: font-adobe-copyrighted-fragment-no-credit
983 Severity: serious
984 Certainty: possible
985 Info: This type 1 font file includes some postscript fragment with a
986 non free license of Adobe. In order to check if this tag is genuine
987 please follow the proceedure described in the reference.
988 .
989 Moreover the fragment was likely verbatim copied from black
990 book without any credit to Adobe.
991 .
992 Should this be a false-positive, please override the tag.
993 Ref: http://wiki.debian.org/qa.debian.org/type1nondfsg
995 Tag: duplicate-font-file
996 Severity: normal
997 Certainty: possible
998 Info: This package appears to include a font file that is already provided
999 by another package in Debian. Ideally it should instead depend on the
1000 relevant font package. If the application in this package loads the font
1001 file by name, you may need to include a symlink pointing to the file name
1002 of the font in its Debian package.
1003 .
1004 Sometimes the font package containing the font is huge and you only need
1005 one font. In that case, you have a few options: modify the package (in
1006 conjunction with upstream) to use libfontconfig to find the font that you
1007 prefer but fall back on whatever installed font is available, ask that
1008 the font package be split apart into packages of a more reasonable size,
1009 or add an override and be aware of the duplication when new versions of
1010 the font are released.
1012 Tag: icon-size-and-directory-name-mismatch
1013 Severity: normal
1014 Certainty: certain
1015 Info: The icon has a size that differs from the size specified by the name
1016 of the directory under which it was installed. The icon was probably
1017 mistakenly installed into the wrong directory.
1019 Tag: raster-image-in-scalable-directory
1020 Severity: normal
1021 Certainty: certain
1022 Info: The given raster image was installed into a "scalable" icon directory.
1023 Only vector graphics (e.g. SVG) should be installed into those directories.
1025 Tag: gz-file-not-gzip
1026 Severity: normal
1027 Certainty: possible
1028 Info: The given file ends with <tt>.gz</tt>, which normally indicates it
1029 is compressed with gzip. However, it doesn't seem to be a
1030 gzip-compressed file. gzip will fail with an error on such files.
1031 Normally this indicates a mistake in the installation process of the
1032 package.
1034 Tag: non-free-flash
1035 Severity: serious
1036 Certainty: possible
1037 Info: The given Flash file has a filename which suggests that it may be
1038 one of a number of known Flash files with non-free content.
1040 Tag: non-conf-file-in-modprobe.d
1041 Severity: important
1042 Certainty: certain
1043 Ref: http://lists.debian.org/debian-devel/2009/03/msg00119.html
1044 Info: Files in <tt>/etc/modprobe.d</tt> should use filenames ending in
1045 <tt>.conf</tt>. modprobe currently warns about files which do not match
1046 this convention and at some point in the future the files will no longer
1047 be processed.
1048 .
1049 If the file is an example containing only comments, consider installing
1050 it in another location as files in <tt>/etc/modprobe.d</tt> are
1051 read each time modprobe is run (which is often at boot time).
1053 Tag: file-in-discouraged-x11-font-directory
1054 Severity: minor
1055 Certainty: certain
1056 Ref: policy 11.8.5
1057 Info: For historical reasons, use of <tt>PEX</tt>, <tt>CID</tt>,
1058 <tt>Speedo</tt>, and <tt>cyrillic</tt> subdirectories of
1059 <tt>/usr/share/fonts/X11</tt> are permitted, but installation of files
1060 into these directories is discouraged. Support for the first three font
1061 types is deprecated or no longer available, and Cyrillic fonts should use
1062 the normal font directories where possible.
1064 Tag: file-in-unknown-x11-font-directory
1065 Severity: serious
1066 Certainty: certain
1067 Ref: policy 11.8.5
1068 Info: Subdirectories of <tt>/usr/share/fonts/X11</tt> other than
1069 <tt>100dpi</tt>, <tt>75dpi</tt>, <tt>misc</tt>, <tt>Type1</tt>, and some
1070 historic exceptions must be neither created nor used. (The directories
1071 <tt>encodings</tt> and <tt>util</tt>, used by some X Window System
1072 packages, are also permitted by Lintian.)
1074 Tag: package-contains-multiple-dpi-fonts
1075 Severity: normal
1076 Certainty: certain
1077 Ref: policy 11.8.5
1078 Info: This package contains both 100dpi and 75dpi bitmapped fonts. Both
1079 versions should not be included in a single package. If both resolutions
1080 are available, they should be provided in separate binary packages with
1081 <tt>-75dpi</tt> or <tt>-100dpi</tt> appended to the package name for the
1082 corresponding fonts.
1084 Tag: package-mixes-misc-and-dpi-fonts
1085 Severity: normal
1086 Certainty: certain
1087 Ref: policy 11.8.5
1088 Info: This package contains both bitmapped fonts for a specific DPI
1089 (100dpi or 75dpi) and misc bitmapped fonts. These should not be combined
1090 in the same package. Instead, the misc bitmapped fonts should be
1091 provided in a separate package with <tt>-misc</tt> appended to its name.
1093 Tag: package-contains-info-dir-file
1094 Severity: serious
1095 Certainty: certain
1096 Info: This package contains a file named <tt>dir</tt> or <tt>dir.old</tt>,
1097 possibly compressed, in <tt>/usr/share/info</tt>. This is the directory
1098 (or backup) of info pages and is generated automatically by install-info
1099 when a package containing info documentation is installed. Some upstream
1100 build systems create it automatically, but it must not be included in a
1101 package since it needs to be generated dynamically based on the installed
1102 info files on the system.
1104 Tag: package-contains-mime-cache-file
1105 Severity: serious
1106 Certainty: certain
1107 Info: This package contains a cache file generated automatically by
1108 update-mime-database when a package containing MIME-Info Database
1109 files is installed. Some upstream build systems create them
1110 automatically, but they must not be included in a package since they need
1111 to be generated dynamically based on the installed MIME-Info Database
1112 files on the system.
1114 Tag: package-contains-mimeinfo.cache-file
1115 Severity: serious
1116 Certainty: certain
1117 Info: This package contains a file named <tt>mimeinfo.cache</tt>,
1118 possibly compressed, in <tt>/usr/share/applications</tt>. This file is
1119 generated automatically by update-desktop-database when a package
1120 containing <tt>.desktop</tt> files associated to MIME types is installed.
1121 Some upstream build systems create it automatically, but it must not be
1122 included in a package since it needs to be generated dynamically based on
1123 the installed .desktop files on the system.
1125 Tag: package-modifies-ld.so-search-path
1126 Severity: important
1127 Certainty: possible
1128 Ref: policy 10.2
1129 Info: This package installs a file in <tt>/etc/ld.so.conf.d</tt>,
1130 presumably to modify the search path of the run-time linker, and does not
1131 appear to be part of libc.
1132 .
1133 Packages containing shared libraries should either install them into
1134 <tt>/usr/lib</tt> or should require binaries built against them to set
1135 RPATH to find the library at run-time. Installing libraries in a
1136 different directory and modifying the run-time linker path is equivalent
1137 to installing them into <tt>/usr/lib</tt> except now conflicting library
1138 packages may cause random segfaults and difficult-to-debug problems
1139 instead of conflicts in the package manager.
1141 Tag: global-data-in-games-directory
1142 Severity: important
1143 Certainty: certain
1144 Info: This package contains files under <tt>/usr/share/games</tt>, such as
1145 desktop files, icons, pixmaps, or MIME type entries, that are global
1146 system data. The user's desktop environment will only check in the
1147 directories directly under <tt>/usr/share</tt> and this information
1148 should be put in the global directory even if it is for games.
1149 .
1150 The most common cause of this problem is using a
1151 <tt>--datadir=/usr/share/games</tt> argument to configure or an
1152 equivalent and using the upstream installation rules. These files need
1153 to be moved into the corresponding directories directly under
1154 <tt>/usr/share</tt>.
1156 Tag: duplicated-compressed-file
1157 Severity: minor
1158 Certainty: possible
1159 Info: The given, apparently compressed, file is shipped in the package
1160 in addition to another file with the same name without the
1161 compression-method extension. Normally this indicates a mistake in the
1162 installation process of the package.
1164 Tag: udev-rule-in-etc
1165 Severity: important
1166 Certainty: certain
1167 Ref: #559208
1168 Info: This package ships a udev rule and installs it under
1169 <tt>/etc/udev/rules.d</tt>, which is reserved for user-installed files.
1170 The correct directory for system rules is <tt>/lib/udev/rules.d</tt>.
1172 Tag: obsolete-comments-style-in-php-ini
1173 Severity: normal
1174 Certainty: certain
1175 Info: This package ships a <tt>.ini</tt> file used to configure php but
1176 it has comments using the old-style comment separator <tt>#</tt>.
1177 Instead, the <tt>;</tt> separator should be used.
1178 .
1179 Since version 5.3, the PHP interpreter warns about the use of the
1180 old style of comment separator.
1182 Tag: triplet-dir-and-architecture-mismatch
1183 Severity: serious
1184 Certainty: possible
1185 Ref: policy 9.1.1
1186 Info: This package contains a directory under <tt>/lib</tt> or
1187 <tt>/usr/lib</tt> which doesn't match the proper triplet for the
1188 binary package's architecture. This is very likely to be a mistake
1189 when indicating the underlying build system where the files should be
1190 installed.
1192 Tag: empty-binary-package
1193 Severity: important
1194 Certainty: wild-guess
1195 Info: This binary package appears to be empty, and its description does
1196 not say that it's a metapackage or a transitional package. This is
1197 often due to problems with updating debhelper *.install files during
1198 package renames or similar problems where installation rules don't put
1199 files in the correct place.
1200 .
1201 If the package is deliberately empty, please mention in the package long
1202 description one of the phrases "metapackage", "dummy", "dependency
1203 package", or "empty package".
1205 Tag: star-file
1206 Severity: important
1207 Certainty: possible
1208 Info: The given file is literally installed as <tt>*</tt> (star
1209 symbol). Normally this indicates a mistake in the installation
1210 process of the package either when creating symlinks or renaming files.
1212 Tag: incorrect-locale-code
1213 Severity: normal
1214 Certainty: possible
1215 Info: The package appears to ship locales for a language but uses an
1216 incorrect locale code as a subdirectory of <tt>/usr/share/locale</tt>.
1217 This usually results in users of the intended target language not
1218 finding the locale. The language codes used in the locale directories
1219 are those from the ISO 639-1 and ISO 639-2 standards, not those
1220 usually used as TLDs (which are from the ISO 3166 standard).
1221 .
1222 Lintian only knows about some commonly-mistaken set of incorrect
1223 locale codes.
1225 Tag: unknown-locale-code
1226 Severity: normal
1227 Certainty: certain
1228 Ref: http://www.loc.gov/standards/iso639-2/php/code_list.php
1229 Info: The package appears to ship locales for a language but uses an
1230 unknown locale code as a subdirectory of <tt>/usr/share/locale</tt>.
1231 This usually results in users of the intended target language not
1232 finding the locale. The language codes used in the locale directories
1233 are those from the ISO 639-1 and ISO 639-2 standards, not those
1234 usually used as TLDs (which are from the ISO 3166 standard).
1235 .
1236 It is possible that the language code was mistyped or incorrectly
1237 guessed from the language's or country's name.
1239 Tag: compressed-objects.inv
1240 Severity: normal
1241 Certainty: possible
1242 Info: The package appears to ship a gzip compressed objects.inv file
1243 in it's documentation. Unfortunately some tools do not cope with
1244 this file being compressed.
1245 .
1246 This file should be excluded from compression during build time.
1247 If using debhelper (<< 8.1.0), you may need to use the -X
1248 option to dh_compress. Newer versions of debhelper handle this
1249 correctly by default.
1251 Tag: missing-pre-dependency-on-multiarch-support
1252 Severity: serious
1253 Certainty: certain
1254 Info: The package ships a library in one of the multiarch lib directories,
1255 /lib/<triplet> and /usr/lib/<triplet>, but does not declare a
1256 pre-dependency on multiarch-support. Packages installing to these
1257 paths must Pre-Depends: multiarch-support to ensure the library can be
1258 found by the dynamic linker at every point during an upgrade.
1260 Tag: package-contains-no-arch-dependent-files
1261 Severity: minor
1262 Certainty: possible
1263 Experimental: yes
1264 Info: The package is not marked architecture all, but all the files it
1265 ships are installed in /usr/share.
1266 .
1267 Most likely this package should be marked architecture all, but there
1268 is a chance that the package is missing files.
1269 Ref: policy 5.6.8
1271 Tag: vim-addon-within-vim-runtime-path
1272 Severity: normal
1273 Certainty: certain
1274 Info: Vim addons should not be installed directly under a directory contained
1275 in the Vim runtime path. Users shall be given the freedom to choose which
1276 addons they want to have enabled and which they don't.
1277 Ref: vim-policy 3.1
1279 Tag: perl-module-uses-perl4-libs-without-dep
1280 Severity: normal
1281 Certainty: possible
1282 Info: This package includes perl modules using obsoleted perl 4-era
1283 libraries. These libraries have been deprecated in perl in 5.14, and
1284 are likely to be removed from the core in perl 5.16. Please either
1285 remove references to these libraries, or add a dependency on
1286 <tt>libperl4-corelibs-perl | perl (<< 5.12.3-7)</tt> to this package.
1288 Tag: gzip-file-is-not-multi-arch-same-safe
1289 Severity: important
1290 Certainty: certain
1291 Info: The gzip file contains a timestamp that will differ between
1292 architectures. Multi-Arch: same implies all shared files must be
1293 byte-for-byte identical.
1294 .
1295 This can usually be fixed by passing -n to gzip.
1297 Tag: dir-or-file-in-home
1298 Severity: serious
1299 Certainty: certain
1300 Info: Debian packages should not install into <tt>/home</tt>, because it
1301 is reserved for users.
1303 Tag: dir-or-file-in-build-tree
1304 Severity: serious
1305 Certainty: possible
1306 Info: Your package install file in our build tree.
1308 Tag: file-name-is-not-valid-UTF-8
1309 Severity: normal
1310 Certainty: certain
1311 Ref: #701081
1312 Info: The file name does not appear to be valid UTF-8. This may become
1313 a requirement in future Policy versions.
1314 .
1315 Note that Lintian may be unable to display the filename accurately.
1316 Unprintable characters may have been replaced.