2 Author: Sean 'Shaleh' Perry <shaleh@debian.org>
6 Info: This looks for cruft in Debian packaging or upstream source
7 Needs-Info: debfiles, diffstat
9 Tag: native-package-with-dash-version
11 Info: Native packaging should only be used if a piece of software was
12 written specifically to be turned into a Debian package. In this case,
13 the version number should not contain a debian revision part.
15 Native source packages are sometimes created by accident. In most cases
16 the reason is the location of the original source tarball. dpkg-source
17 searches for this in ../package_upstream-version.orig.tar.gz.
19 Tag: documentation-package-not-architecture-independent
21 Info: Documentation packages usually shouldn't carry anything that requires
22 recompiling on various architectures, in order to save space on mirrors.
24 Tag: debian-files-list-in-source
26 Info: Leaving <tt>debian/files</tt> causes problems for the autobuilders,
27 since that file will likely include the list of .deb files for another
28 architecture, which will cause dpkg-buildpackage run by the buildd to fail.
30 The clean rule for the package should remove this file.
32 Tag: diff-contains-cvs-control-dir
34 Info: The Debian diff or native package contains files in a CVS directory.
35 These are usually artifacts of the revision control system used by the
36 Debian maintainer and not useful in a diff or native package. Passing
37 <tt>-i</tt> to <tt>dpkg-buildpackage</tt> or the equivalent will
38 automatically exclude them.
40 Tag: source-contains-cvs-control-dir
42 Info: The upstream source contains a CVS directory. It was most likely
43 included by accident since CVS directories usually don't belong in
44 releases. When packaging a CVS snapshot, export from CVS rather than use
45 a checkout. If an upstream release tarball contains CVS directories, you
46 usually should report this as a bug to upstream.
48 Tag: diff-contains-svn-control-dir
50 Info: The Debian diff or native package contains files in an .svn
51 directory. These are usually artifacts of the revision control system
52 used by the Debian maintainer and not useful in a diff or native package.
53 Passing <tt>-i</tt> to <tt>dpkg-buildpackage</tt> or the equivalent will
54 automatically exclude them.
56 Tag: source-contains-svn-control-dir
58 Info: The upstream source contains an .svn directory. It was most likely
59 included by accident since Subversion version control directories
60 usually don't belong in releases. When packaging a Subversion snapshot,
61 export from subversion rather than checkout. If an upstream release
62 tarball contains .svn directories, this should be reported as a bug to
63 upstream since it can double the size of the tarball to no purpose.
65 Tag: diff-contains-bzr-control-dir
67 Info: The Debian diff or native package contains files in a .bzr
68 directory. These are usually artifacts of the revision control system
69 used by the Debian maintainer and not useful in a diff or native package.
70 Passing <tt>-i</tt> to <tt>dpkg-buildpackage</tt> or the equivalent will
71 automatically exclude them.
73 Tag: source-contains-bzr-control-dir
75 Info: The upstream source contains a .bzr directory. It was most likely
76 included by accident since bazaar-ng version control directories usually
77 don't belong in releases and may contain the entire repository. When
78 packaging a bzr snapshot, use bzr export to create a clean tree. If an
79 upstream release tarball contains .bzr directories, you should usually
80 report this as a bug upstream.
82 Tag: diff-contains-arch-control-dir
84 Info: The Debian diff or native package contains files in an {arch} or
85 .arch-ids directory or a directory starting with <tt>,,</tt> (used by baz
86 for debugging traces). These are usually artifacts of the revision
87 control system used by the Debian maintainer and not useful in a diff or
88 native package. Passing <tt>-i</tt> to <tt>dpkg-buildpackage</tt> or the
89 equivalent will automatically exclude them.
91 Tag: source-contains-arch-control-dir
93 Info: The upstream source contains an {arch} or .arch-ids directory or a
94 directory starting with <tt>,,</tt> (used by baz for debugging traces).
95 It was most likely included by accident since Arch version control
96 directories usually don't belong in releases. If an upstream release
97 tarball contains these directories, you should usually report this as a
100 Tag: diff-contains-git-control-dir
102 Info: The Debian diff or native package contains files in a .git
103 directory. These are usually artifacts of the revision control system
104 used by the Debian maintainer and not useful in a diff or native package.
105 Passing <tt>-i</tt> to <tt>dpkg-buildpackage</tt> or the equivalent will
106 automatically exclude them.
108 Tag: source-contains-git-control-dir
110 Info: The upstream source contains a .git directory. It was most likely
111 included by accident since git version control directories usually don't
112 belong in releases and may contain a complete copy of the repository. If
113 an upstream release tarball contains .git directories, you should usually
114 report this as a bug upstream.
116 Tag: diff-contains-hg-control-dir
118 Info: The Debian diff or native package contains files in a .hg
119 directory. These are usually artifacts of the revision control system
120 used by the Debian maintainer and not useful in a diff or native package.
121 Passing <tt>-i</tt> to <tt>dpkg-buildpackage</tt> or the equivalent will
122 automatically exclude them.
124 Tag: source-contains-hg-control-dir
126 Info: The upstream source contains a .hg directory. It was most likely
127 included by accident since hg version control directories usually don't
128 belong in releases and may contain a complete copy of the repository. If
129 an upstream release tarball contains .hg directories, you should usually
130 report this as a bug upstream.
132 Tag: diff-contains-svn-commit-file
134 Info: The Debian diff or native package contains an
135 <tt>svn-commit(.NNN).tmp</tt>, almost certainly a left-over from a failed
136 Subversion commit by the Debian package maintainer.
138 Tag: source-contains-svn-commit-file
140 Info: The upstream source contains an <tt>svn-commit(.NNN).tmp</tt>,
141 almost certainly a left-over from a failed Subversion commit. You may
142 want to report this as an upstream bug.
144 Tag: diff-contains-svk-commit-file
146 Info: The Debian diff or native package contains an
147 <tt>svk-commitNNN.tmp</tt>, almost certainly a left-over from a failed
148 svk commit by the Debian package maintainer.
150 Tag: source-contains-svk-commit-file
152 Info: The upstream source contains an <tt>svk-commitNNN.tmp</tt>,
153 almost certainly a left-over from a failed Subversion commit. You may
154 want to report this as an upstream bug.
156 Tag: diff-contains-arch-inventory-file
158 Info: The Debian diff or native package contains an
159 <tt>.arch-inventory</tt> file. This is Arch metadata that should
160 normally not be distributed.
162 Tag: source-contains-arch-inventory-file
164 Info: The upstream source contains an <tt>.arch-inventory</tt> file. This
165 is Arch metadata that should normally not be distributed. You may want
166 to report this as an upstream bug.
168 Tag: diff-contains-cvs-conflict-copy
170 info: The Debian diff or native package contains a CVS conflict copy.
171 These have file names like <tt>.#file.version</tt> and are generated by
172 CVS when a conflict was detected when merging local changes with updates
173 from a source repository. They're useful only while resolving the
174 conflict and should not be included in the package.
176 Tag: source-contains-cvs-conflict-copy
178 info: The upstream source contains a CVS conflict copy. These have file
179 names like <tt>.#file.version</tt> and are generated by CVS when a
180 conflict was detected when merging local changes with updates from a
181 source repository. They're useful only while resolving the conflict and
182 were probably included by accident. You may want to report this as an
185 Tag: diff-contains-svn-conflict-file
187 info: The Debian diff or native package contains a file that looks like a
188 Subversion conflict file. These are generated by Subversion when a
189 conflict was detected while merging local changes with updates from a
190 source repository. Use <tt>svn resolved</tt> to remove them and clear
191 the Subversion conflict state after you have resolved the conflict.
193 Tag: source-contains-svn-conflict-file
195 info: The upstream source contains a file that looks like a Subversion
196 conflict file. These are generated by Subversion when a conflict was
197 detected while merging local changes with updates from a source
198 repository. They're useful only while resolving the conflict and
199 were probably included by accident. You may want to report this as an
202 Tag: diff-contains-patch-failure-file
204 Info: The Debian diff or native package contains a file that looks like
205 the files left behind by the <tt>patch</tt> utility when it cannot
206 completely apply a diff. This may be left over from a patch applied by
207 the maintainer. Normally such files should not be included in the
210 Tag: diff-contains-editor-backup-file
212 Info: The Debian diff or native package contains a file ending in
213 <tt>~</tt> or of the form <tt>.xxx.swp</tt>, which is normally either an
214 Emacs or vim backup file or a backup file created by programs such as
215 <tt>autoheader</tt> or <tt>debconf-updatepo</tt>. This usually causes no
216 harm, but it's messy and bloats the size of the Debian diff to no useful
219 Tag: diff-contains-substvars
221 Info: Lintian found a substvars file in the Debian diff for this source
222 package. The debian/substvars file is usually generated and modified
223 dynamically by debian/rules targets, in which case it must be removed by
227 Tag: configure-generated-file-in-source
229 Info: Leaving config.cache/status causes autobuilders problems.
230 config.cache and config.status are produced by GNU autoconf's configure
231 scripts. If they are left in the source package, autobuilders may pick
232 up settings for the wrong architecture.
234 The clean rule in <tt>debian/rules</tt> should remove this file. This
235 should ideally be done by fixing the upstream build system to do it when
236 you run the appropriate cleaning command (and don't forget to forward the
237 fix to the upstream authors so it doesn't happen in the next release). If
238 that is already implemented, then make sure you are indeed cleaning it in
239 the clean rule. If all else fails, a simple rm -f should work.
241 Note that Lintian cannot reliably detect the removal in the clean rule,
242 so once you fix this, please ignore or override this warning.
244 Tag: outdated-autotools-helper-file
246 Info: The referenced file has a time stamp older than year 2004 and the
247 package does not build-depend on autotools-dev or automake and therefore
248 apparently does not update it. This usually means that the source package
249 will not work correctly on all currently released architectures.
251 Read /usr/share/doc/autotools-dev/README.Debian.gz (from the
252 autotools-dev package) for information on how to fix this problem.
254 Tag: diff-contains-bts-control-dir
256 Info: The Debian diff or native package contains files in a directory
257 used by a bug tracking system, which are not useful in a diff or native
258 package. Passing <tt>-i</tt> to <tt>dpkg-buildpackage</tt> or the
259 equivalent will automatically exclude them.
261 Tag: source-contains-bts-control-dir
263 Info: The upstream source contains a directory used by a bug tracking
264 system. It was most likely included by accident since bug tracking system
265 directories usually don't belong in releases.