2 Author: Christian Schwarz <schwarz@debian.org>
6 Needs-Info: objdump-info, scripts
7 Info: This script checks if a binary package conforms to policy
8 WRT to files and directories.
10 Tag: package-contains-ancient-file
12 Info: Your package contains a file that claims to been generated more
13 than 20 years ago. This is most probably an error. Your package will
14 be rejected by the Debian archive scripts if it contains a file with
17 Tag: old-app-defaults-directory
19 Info: The app-defaults files have moved to /etc/X11/app-defaults/. Files in
20 the old directory, /usr/X11R6/lib/X11/app-defaults/, will no longer be
21 used by X. The old directory should not exist in packages at all;
22 this prevents X from replacing it with a compatability symlink.
25 Tag: package-installs-font-to-usr-x11r6
27 Info: The standard location for X fonts has moved to /usr/share/fonts/X11.
28 Packages providing X fonts must install them into the new path. Fonts
29 installed into the old /usr/X11R6/lib/X11/fonts path may not be seen by
32 If the package uses imake, it must build-depend on xutils-dev (>=
33 1:1.0.2-2) for the correct paths. If it uses dh_installxfonts to handle X
34 font installation, it must build-depend on debhelper (>= 5.0.31).
37 Tag: package-installs-file-to-usr-x11r6-bin
39 Info: Debian has switched to the modular X tree which now uses the regular
40 FHS paths, and all packages must follow. All packages installing binaries
41 must install them into /usr/bin (or some other appropriate location)
42 instead of /usr/X11R6/bin.
44 The x11-common package attempts to change /usr/X11R6/bin into a symlink
45 to /usr/bin, so if this migration has already occurred, a package
46 installing files into /usr/X11R6/bin may appear to install
47 successfully. However, such a package will be left in an inconsistent
48 state and may orphan files when the compatibility link goes away.
50 If the package uses imake, it must build-depend on xutils-dev (>=
51 1:1.0.2-2) for the correct paths.
54 Tag: file-in-usr-something-x11-without-pre-depends
56 Info: Packages that install files into /usr/include/X11 or /usr/lib/X11
57 should pre-depend on at least x11-common (>= 1:7.0.0). These directories
58 used to be symlinks and installing files in them while they are still
59 symlinks will put files in the wrong locations and cause stranded files
60 and other problems. x11-common is responsible for converting the
61 symlinks to regular directories.
63 A fresh etch (or later) install will not have problems even without this
64 dependency, but this dependency is needed for upgrades from sarge and is
65 therefore still useful for backports.
68 Tag: package-installs-file-to-usr-x11r6
70 Info: Packages using the X Window System should not be configured to install
71 files under the /usr/X11R6/ directory. Debian has switched to the modular
72 X tree which now uses regular FHS paths and all packages should follow.
74 Programs that use GNU autoconf and automake are usually easily configured
75 at compile time to use /usr/ instead of /usr/X11R6/. Packages that use
76 imake must build-depend on xutils-dev (>= 1:1.0.2-2) for the correct
80 Tag: config-file-reserved
82 Info: This file is reserved by a specific package. Please email the
83 maintainer of the package in question if you have questions.
85 Tag: package-uses-obsolete-file
87 Info: the file, /etc/nntpserver, is no longer recommenced. As of policy
88 revision 2.5.1.0, /etc/news/server is the preferred file to use to specify
92 Tag: FSSTND-dir-in-usr
94 Info: As of policy version 3.0.0.0, Debian no longer follows the FSSTND.
96 Instead, the Filesystem Hierarchy Standard (FHS), version 2.3, is
97 used. You can find it in /usr/share/doc/debian-policy/fhs/ .
99 Tag: FSSTND-dir-in-var
101 Info: As of policy version 3.0.0.0, Debian no longer follows the FSSTND.
103 Instead, the Filesystem Hierarchy Standard (FHS), version 2.3, is
104 used. You can find it in /usr/share/doc/debian-policy/fhs/ .
106 Tag: package-installs-into-etc-gconf-schemas
108 Info: The package installs files into the <tt>/etc/gconf/schemas</tt>
109 directory. No package should do this; this directory is reserved for
110 local overrides. Instead, schemas should be installed into
111 <tt>/usr/share/gconf/schemas</tt>.
113 Tag: package-installs-into-etc-rc.d
115 Info: The package installs files into the <tt>/etc/rc.d</tt> or
116 <tt>/etc/rc?.d</tt> which is not allowed.
119 Tag: package-installs-into-etc-rc.boot
121 Info: The package installs files in the <tt>/etc/rc.boot</tt> directory,
122 which is obsolete. See rc.boot(5) for details.
125 Tag: non-standard-file-permissions-for-etc-init.d-script
127 Info: Usually, scripts in the <tt>/etc/init.d</tt> directory should have
130 Tag: file-directly-in-usr-share
132 Info: Packages should not install files directly in <tt>/usr/share</tt>,
133 i.e., without a subdirectory.
135 You should either create a subdirectory <tt>/usr/share/...</tt> for your
136 package or place the file in <tt>/usr/share/misc</tt>.
138 Tag: file-in-usr-local
140 Info: The package installs a file in <tt>/usr/local/...</tt> which is
146 Info: The package installs a file in <tt>/opt/...</tt> which is not allowed.
148 Tag: stray-directory-in-manpage-directory
150 Info: This package installs a directory under <tt>/usr/share/man</tt> or
151 <tt>/usr/X11R6/man</tt> that isn't a manual section directory or locale
155 Tag: executable-manpage
157 Info: Manual pages are not meant to be executed.
159 Tag: dir-in-usr-local
161 Info: The package installs a directory in <tt>/usr/local/...</tt> which is
164 If you want to provide an empty directory in <tt>/usr/local</tt> for
165 convenience of the local system administrator, please follow the rules
166 in the policy manual (section 9.1.2), i.e., create the directories in
167 the postinst script but don't fail if this isn't possible (e.g., if
168 <tt>/usr/local</tt> is mounted read-only).
171 Tag: possible-name-space-pollution
173 Info: The package installs a binary which uses a very short file name (one
174 or two characters). This is not forbidden by policy, but short names
175 should be reserved for the user. Unless this short name has been used
176 for a while already (like the famous `ls', `rm', `cp' commands), you
177 should consider giving these binaries a longer name.
179 Tag: non-standard-dir-perm
181 Info: The directory has a mode different from 0755, and it's not one of the
185 Tag: executable-is-not-world-readable
187 Info: All executables should be readable by any user. Since anyone can
188 download the Debian package and obtain a copy of the executable, no
189 security is gained by making the executable unreadable even for setuid
190 binaries. If only members of a certain group may execute this file,
191 remove execute permission for world, but leave read permission.
194 Tag: non-standard-executable-perm
196 Info: Executables that are not setuid or setgid should always have a mode
197 of 0755. Since anyone can obtain the executable by downloading the
198 Debian package and extracting it, restricting access serves little
202 Tag: non-standard-game-executable-perm
204 Info: The file is owned by the games group but is not mode 2755. If a
205 game does not have to be setgid games, it should be owned by the root
206 group like any other executable. This executable is either owned by the
207 wrong group or is not setgid when it should be.
209 Tag: non-standard-setuid-executable-perm
211 Info: The file is setuid or setgid and has a mode different from any of
212 2755, 4755, 4754, or 6755. Any other permissions on setuid executables
213 is probably a bug. In particular, removing root write privileges serves
214 no purpose, group-writable setuid or setgid executables are probably bad
215 ideas, and setgid executables that are not world-executable serve little
221 Info: The file is tagged SETUID. In some cases this is intentional, but in
222 other cases this is a bug. If this is intentional, please add a lintian
223 override to document this fact.
227 Info: The file is tagged SETGID. In some cases this is intentional, but in
228 other cases this is a bug. If this is intentional, please add a lintian
229 override to document this fact.
231 Tag: setuid-gid-binary
233 Info: The file is tagged SETUID and SETGID. In some cases this is
234 intentional, but in other cases this is a bug. If this is intentional,
235 please add a lintian override to document this fact.
237 Tag: non-standard-file-perm
239 Info: The file has a mode different from 0644. In some cases this is
240 intentional, but in other cases this is a bug.
245 Info: The package contains a <i>special</i> file (e.g., a device file).
246 This is forbidden by current policy. If your program needs this device,
247 you should create it by calling <tt>makedev</tt> from the postinst
251 Tag: old-style-example-dir
253 Info: The package installs some files into the old
254 <tt>/usr/doc/examples</tt> directory. The new location for examples
255 is <tt>/usr/share/doc/<i>pkg</i>/examples</tt>.
257 Tag: compressed-symlink-with-wrong-ext
259 Info: The package installs a symbolic link pointing to a compressed file,
260 but the symbolic link does not use the same file extension than the
261 referenced file. In most cases, this can produce troubles when the
262 user or a program tries to access the file through the link.
265 Tag: symlink-has-double-slash
267 Info: This symlink contains two successive slashes (//). This is in violation
268 of policy, where it is stated that symlinks should be as short as possible
270 If you use debhelper, running dh_link after creating the package structure
271 will fix this problem for you.
274 Tag: symlink-ends-with-slash
276 Info: This symlink ends with a slash (/). This is in violation
277 of policy, where it is stated that symlinks should be as short as possible
279 If you use debhelper, running dh_link after creating the package structure
280 will fix this problem for you.
283 Tag: symlink-should-be-relative
285 Info: Symlinks to files which are in the same top-level directory should be
286 relative according to policy. (In other words, a link in /usr to another
287 file in /usr should be relative, while a link in /usr to a file in /etc
290 If you use debhelper, running dh_link after creating the package structure
291 will fix this problem for you.
294 Tag: symlink-should-be-absolute
296 Info: Symbolic links between different top-level directories should be
299 If you use debhelper, running dh_link after creating the package structure
300 will fix this problem for you.
303 Tag: udeb-contains-documentation-file
305 Info: udeb packages should not contain any documentation.
307 Tag: executable-in-usr-share-doc
309 Info: Usually, documentation files in <tt>/usr/share/doc</tt> should have mode
310 0644. If the executable is an example, it should go in
311 <tt>/usr/share/doc/<i>pkg</i>/examples</tt>.
313 Tag: script-in-usr-share-doc
315 Info: Scripts are usually not documentation files, unless they are
316 examples, in which case they should be in the
317 <tt>/usr/share/doc/<i>pkg</i>/examples</tt> directory.
319 Tag: symlink-has-too-many-up-segments
321 Info: The symlink references a directory beyond the root directory `/'.
325 Info: This link goes up, and then back down into the same subdirectory.
326 Making it shorter will improve its chances of finding the right file
327 if the user's system has lots of symlinked directories.
329 If you use debhelper, running dh_link after creating the package structure
330 will fix this problem for you.
333 Tag: symlink-is-self-recursive
335 Info: The symbolic link is recursive to a higher directory of the symlink
336 itself. This means, that you can infinitely chdir with this symlink. This is
337 usually not okay, but sometimes wanted behaviour.
339 Tag: symlink-contains-spurious-segments
341 Info: The symbolic link has needless segments like '..' and '.' in the middle.
342 These are unneeded, and make the link longer than it could be, which is in
345 If you use debhelper, running dh_link after creating the package structure
346 will fix this problem for you.
349 Tag: run-parts-cron-filename-contains-full-stop
351 Info: The script in /etc/cron.<time-interval> will not be executed by
352 run-parts(8) because the filename contains a "." (full stop).
354 Tag: bad-permissions-for-etc-cron.d-script
356 Info: Files in <tt>/etc/cron.d</tt> are configuration files for cron and not
357 scripts. Thus, they should not be marked executable.
359 Tag: bad-permissions-for-etc-emacs-script
361 Info: Files in the <tt>/etc/emacs*</tt> directories should not be marked
364 Tag: image-file-in-usr-lib
366 Info: This package installs a pixmap or a bitmap within <tt>/usr/lib</tt>.
367 According to the Filesystem Hierarchy Standard, architecture-independent
368 files need to be placed within <tt>/usr/share</tt> instead.
370 Tag: file-directly-in-usr-share-doc
372 Info: Documentation files have to be installed in
373 <tt>/usr/share/doc/<i>pkg</i></tt>.
376 Tag: bad-owner-for-doc-file
378 Info: Documentation files should be owned by <tt>root/root</tt>.
380 Tag: dir-or-file-in-var-www
383 Info: Debian packages should not install files under <tt>/var/www</tt>.
384 This is not one of the <tt>/var</tt> directories in the File Hierarchy
385 Standard and is under the control of the local administrator. Packages
386 should not assume that it is the document root for a web server; it is
387 very common for users to change the default document root and packages
388 should not assume that users will keep any particular setting.
390 Packages that want to make files available via an installed web server
391 should instead put instructions for the local administrator in a
392 README.Debian file and ideally include configuration fragments for common
393 web servers such as Apache.
395 As an exception, packages are permitted to create the <tt>/var/www</tt>
396 directory due to its past history as the default document root, but
397 should at most copy over a default file in postinst for a new install.
399 Tag: dir-or-file-in-tmp
401 Info: Packages should not install into <tt>/tmp</tt> or <tt>/var/tmp</tt>.
403 Tag: dir-or-file-in-mnt
405 Info: Packages should not install into <tt>/mnt</tt>. The FHS states that
406 the contents of this directory is a local issue.
408 Tag: dir-or-file-in-opt
410 Info: Debian packages should not install into <tt>/opt</tt>, because it
411 is reserved for add-on software.
413 Tag: dir-or-file-in-srv
416 Info: Debian packages should not install into <tt>/srv</tt>. The
417 specification of <tt>/srv</tt> states that its structure is at the
418 discretion of the local administrator and no package should rely on any
419 particular structure. Debian packages that install files directly into
420 <tt>/srv</tt> can't adjust for local policy about its structure and in
421 essence force a particular structure.
423 If a package wishes to put its data in <tt>/srv</tt>, it must do this in
424 a way that allows the local administrator to specify and preserve their
425 chosen directory structure (such as through post-install configuration,
426 setup scripts, debconf prompting, etc.).
428 Tag: third-party-package-in-python-dir
430 Info: According to <a href="http://www.python.org/doc/essays/packages.html">
431 <tt>http://www.python.org/doc/essays/packages.html</tt></a>, third-party
432 python packages should install their files in
433 <tt>/usr/lib/python1.5/site-packages</tt>. All other directories in
434 <tt>/usr/lib/python1.5</tt> are for use by the core python packages.
436 Tag: perl-module-in-core-directory
438 Info: Packaged modules must not be installed into the core perl
439 directories as those directories change with each upstream perl
440 revision. The vendor directories are provided for this purpose.
443 Tag: backup-file-in-package
445 Info: There is a file in the package whose name matches the format emacs
446 or vim uses for backup and autosave files. It may have been installed by
449 Tag: nfs-temporary-file-in-package
451 Info: There is a file in the package whose name matches the format NFS
452 uses to temporarily save files that were deleted while another process
453 had them open. It may have been included in the package by accident
454 while building the package in an NFS filesystem.
456 Tag: windows-thumbnail-database-in-package
458 Info: There is a file in the package named <tt>Thumbs.db</tt> or
459 <tt>Thumbs.db.gz</tt>, which is normally a Windows image thumbnail
460 database. Such databases are generally useless in Debian packages and
461 were usually accidentally included by copying complete directories from
464 Tag: macos-ds-store-file-in-package
466 Info: There is a file in the package named <tt>.DS_Store</tt> or
467 <tt>.DS_Store.gz</tt>, the file name used by Mac OS X to store folder
468 attributes. Such files are generally useless in Debian packages and were
469 usually accidentally included by copying complete directories from the
472 Tag: macos-resource-fork-file-in-package
474 Info: There is a file in the package with a name starting with
475 <tt>._</tt>, the file name pattern used by Mac OS X to store resource
476 forks in non-native file systems. Such files are generally useless in
477 Debian packages and were usually accidentally included by copying
478 complete directories from the source tarball.
480 Tag: package-installs-perllocal-pod
482 Info: This package installs a file <tt>perllocal.pod</tt>. Since that
483 file is intended for local documentation, it is not likely that it is
484 a good place for documentation supplied by a Debian package. In fact,
485 installing this package will wipe out whatever local documentation
488 Tag: extra-license-file
491 Info: All license information should be collected in the
492 <tt>debian/copyright</tt> file. This usually makes it unnecessary
493 for the package to install this information in other places as well.
495 Tag: non-standard-toplevel-dir
497 Info: The Filesystem Hierarchy Standard forbids the installation of new
498 files or directories in the root directory, in section 3.
502 Info: The Filesystem Hierarchy Standard forbids the installation of new
503 directories in <tt>/bin</tt>.
505 Tag: subdir-in-usr-bin
507 Info: The Filesystem Hierarchy Standard forbids the installation of new
508 directories in <tt>/usr/bin</tt> other than <tt>/usr/bin/mh</tt>.
510 Tag: non-standard-dir-in-usr
512 Info: The FHS says "No large software packages should use a direct
513 subdirectory under the <tt>/usr</tt> hierarchy". This package contains
514 a directory in <tt>/usr</tt> that is not mentioned in the Filesystem
517 Tag: non-standard-dir-in-var
519 Info: The FHS says "Applications should generally not add directories to
520 the top level of <tt>/var</tt>. Such directories should only be added
521 if they have some system-wide implication, and in consultation with the
524 Tag: use-of-compat-symlink
526 Info: This package uses a directory that, according to the Filesystem
527 Hierarchy Standard, should exist only as a compatibility symlink.
528 Packages should not traverse such symlinks when installing files, they
529 should use the standard directories instead.
531 Tag: file-in-unusual-dir
533 Info: This file or symbolic link is in a directory where files are not
534 normally installed by Debian packages.
536 Tag: package-installs-packlist
538 Info: Packages built using the perl MakeMaker package will have a file
539 named .packlist in them. Those files are useless, and (in some cases)
540 have the additional problem of creating an architecture-specific
541 directory name in an architecture-independent package.
543 They can be suppressed by adding the following to <tt>debian/rules</tt>:
545 find debian/<i>pkg</i> -type f -name .packlist | xargs rm -f
547 or by telling MakeMaker to use vendor install dirs; consult a recent
548 version of Perl policy. Perl 5.6.0-12 or higher supports this.
550 Tag: zero-byte-file-in-doc-directory
552 Info: Package contains a file which is empty.
554 Tag: override-file-in-wrong-location
556 Info: Location of per package overrides the file
557 /usr/share/lintian/overrides/package. See the lintian documentation for more
558 info on proper naming and format.
560 Tag: package-contains-upstream-install-documentation
563 Info: Binary packages do not need to contain the instructions for building
564 and installing the package as this info is not needed by package users.
565 If the info contained is important for configuration perhaps it could be
566 summarized in README.Debian, otherwise an override may be added.
568 Tag: package-contains-hardlink
570 Info: The package contains a hardlink in <tt>/etc</tt> or across different
571 directories. This might not work at all if directories are on different
572 filesystems (which can happen anytime as the system administrator sees fit),
573 certain filesystems such as AFS don't even support cross-directory hardlinks
576 For configuration files, certain editors might break hardlinks, and so
577 does dpkg in certain cases.
579 A better solution might be using symlinks here.
581 Tag: package-contains-bts-control-dir
583 Info: The package contains a control directory for a bug tracking system.
584 It was most likely installed by accident, since bug tracking directories
585 usually don't belong in packages.
587 Tag: package-contains-vcs-control-dir
589 Info: The package contains a control directory for a version control system.
590 It was most likely installed by accident, since version control directories
591 usually don't belong in packages.
593 Tag: package-contains-xvpics-dir
595 Info: Package contains a .xvpics directory. It was most likely installed by
596 accident, since thumbnails usually don't belong in packages.
598 Tag: package-contains-vcs-control-file
600 Info: The package contains a VCS control file such as .(cvs|git|hg)ignore.
601 Files such as these are used by revision control systems to, for example,
602 specify untracked files it should ignore or inventory files. This file
603 is generally useless in an installed package and was probably installed
606 Tag: svn-commit-file-in-package
608 Info: The package contains an svn-commit(.NNN).tmp file. This file is
609 almost certainly a left-over from a failed Subversion commit, and does
610 not belong in a Debian package.
612 Tag: svk-commit-file-in-package
614 Info: The package contains an svk-commitNNN.tmp file. This file is almost
615 certainly a left-over from a failed Subversion commit, and does not
616 belong in a Debian package.
618 Tag: nested-examples-directory
620 Info: Package contains a <tt>usr/share/doc/something/examples/examples</tt>
621 directory. It was most likely installed by accident, since one examples/
622 directory should be enough for everybody(tm).
624 Tag: package-installs-nonbinary-perl-in-usr-lib-perl5
626 Info: Architecture-independent Perl code should be placed in
627 <tt>/usr/share/perl5</tt>, not <tt>/usr/lib/perl5</tt>
628 unless there is at least one architecture-dependent file
631 Tag: file-in-usr-lib-site-python
633 Ref: Python policy 1.4
634 Info: The directory /usr/lib/site-python has been deprecated as a
635 location for installing Python modules and may be dropped from Python's
636 module search path in a future version. Most likely this module is a
637 private module and should be packaged in a directory outside of Python's
640 Tag: package-installs-python-pyc
642 Info: Compiled python source files should not be included in the package.
643 These files should be removed from the package and created at package
644 installation time in the postinst.
646 Tag: bad-permissions-for-ali-file
648 Info: Ada Library Information (*.ali) files are required to be read-only
651 If at least one user can write the *.ali file, GNAT considers whether
652 or not to recompile the corresponding source file. Such recompilation
653 would fail because normal users don't have write permission on the
654 files. Moreover, such recompilation would defeat the purpose of
655 library packages, which provide *.a and *.so libraries to link against).
657 Tag: package-contains-readme-for-other-platform-or-distro
659 Info: package contains a README.(platform) file that contains instructions
660 specific to a platform or distribution other than Debian and thus can
661 most likely be removed. If it contains information that pertains to
662 Debian, please consider renaming it, or including it in an already
663 existing README file.
665 Tag: desktop-file-in-wrong-dir
667 Info: The package contains a .desktop file in an obsolete directory.
668 According to the menu-spec draft on freedesktop.org, those .desktop files
669 that are intended to create a menu should be placed in
670 <tt>/usr/share/applications</tt>, not <tt>/usr/share/gnome/apps</tt>.
672 Tag: file-in-usr-lib-cgi-bin
674 Info: Packages shipping web server CGI files should install them in
675 <tt>/usr/lib/cgi-lib</tt>, not in <tt>/usr/lib/cgi-bin</tt>. This is
676 done to avoid conflicts with the cgi-bin script alias, which is reserved
677 for the local use of webmasters. Web servers should include /cgi-lib/ as
678 a standard ScriptAlias pointing to that directory.
681 Tag: script-with-language-extension
683 Info: When scripts are installed into a directory in the system PATH, the
684 script name should not include an extension such as <tt>.sh</tt> or
685 <tt>.pl</tt> that denotes the scripting language currently used to
686 implement it. The implementation language may change; if it does,
687 leaving the name the same would be confusing and changing it would be
691 Tag: file-in-usr-lib-sgml
694 Info: This package installs a file in <tt>/usr/lib/sgml</tt>. This was
695 the old location for SGML catalogs and similar flies. All those files
696 should now go into <tt>/usr/share/sgml</tt>.
698 Tag: file-name-ends-in-whitespace
700 Info: This package installs a file or directory whose name ends in
701 whitespace. This might be intentional but it's normally a mistake. If
702 it is intentional, add a lintian override.
704 One possible cause is using debhelper 5.0.57 or earlier to install a
705 doc-base file with a Document field that ends in whitespace.
707 Tag: package-contains-empty-directory
709 Info: This package installs an empty directory. This might be intentional
710 but it's normally a mistake. If it is intentional, add a lintian override.
712 Tag: package-section-games-but-contains-no-game
715 Info: This package is marked as part of the section games, but doesn't
716 contain files in <tt>/usr/games</tt>. Binaries of games must be installed
717 in <tt>/usr/games</tt>.
719 Tag: package-section-games-but-has-usr-bin
722 Info: This package is marked as part of the section games, but contains
723 exectuables in <tt>/bin</tt> or <tt>/usr/bin/</tt>. This can be intentional,
724 but is usually a mistake.
726 Tag: package-contains-devhelp-file-without-symlink
728 Info: This package contains a *.devhelp or *.devhelp2 file which is not in
729 the devhelp search path (<tt>/usr/share/devhelp/books</tt> and
730 <tt>/usr/share/gtk-doc/html</tt>) and is apparently not in a directory
731 linked into the devhelp search path. This will prevent devhelp from
732 finding the documentation.
734 If the devhelp documentation is installed in a path outside the devhelp
735 search path (such as <tt>/usr/share/doc</tt>), create a symlink in
736 <tt>/usr/share/gtk-doc/html</tt> pointing to the documentation directory.
738 Tag: debug-package-should-be-named-dbg
740 Info: This package provides at least one file in <tt>/usr/lib/debug</tt>,
741 which is intended for detached debugging symbols, but the package name
742 does not end in "-dbg". Detached debugging symbols should be put into a
743 separate package, Priority: extra, with a package name ending in "-dbg".
745 Tag: package-contains-linda-override
747 Info: This package contains a linda override file in
748 <tt>/usr/share/linda/overrides</tt>. Linda is obsolete and has been
749 removed from the archive as of 2008-03-04. Linda overrides should
750 probably be dropped from packages.
752 Tag: wrong-file-owner-uid-or-gid
754 Info: The user or group ID of the owner of the file is invalid. The
755 owner user and group IDs must be in the set of globally allocated
756 IDs, because other IDs are dynamically allocated and might be used
757 for varying purposes on different systems, or are reserved. The set
758 of the allowed, globally allocated IDs consists of the ranges 0-99,
759 64000-64999 and 65534.
762 Tag: embedded-javascript-library
764 Info: This package contains an embedded copy of the JQuery, Prototype,
765 Mochikit or "Cropper" JavaScript libraries that are now available in their
766 own packages. Please depend on the appropriate package and symlink the
767 library into the appropriate location.
projects / maemian / blob