File: debdiff.desc

package info (click to toggle)
lintian 1.23.28%2Betch1
  • links: PTS
  • area: main
  • in suites: etch
  • size: 2,044 kB
  • ctags: 295
  • sloc: perl: 5,038; makefile: 702; python: 431; sh: 329; ansic: 30; tcl: 4; sed: 1
file content (42 lines) | stat: -rw-r--r-- 1,730 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
Check-Script: debdiff
Author: Richard Braakman <dark@xs4all.nl>
Abbrev: dif
Standards-Version: 3.6.1
Type: source
Unpack-Level: 1
Info: This script checks the diff to the original source tarball of a
 debian package
Needs-Info: diffstat

Tag: patch-failure-file-in-diff
Type: warning
Info: If the <tt>patch</tt> utility cannot completely apply a diff,
 it leaves certain files in the directory tree.  Lintian found such files
 in the Debian-diff for this source package.  This may indicate that the
 maintainer applied a patch that did not quite fit, and didn't notice.

Tag: editor-backup-file-in-diff
Type: info
Info: The Debian diff contains a file ending in <tt>~</tt> or of the form
 <tt>.xxx.swp</tt>, which is normally either an Emacs or vim backup file
 or a backup file created by programs such as <tt>autoheader</tt> or
 <tt>debconf-updatepo</tt>.  This usually causes no harm, but it's messy
 and bloats the size of the Debian diff to no useful purpose.

Tag: native-package-with-dash-version
Type: warning
Info: Native packaging should only be used if a piece of software was
 written specifically to be turned into a Debian package. In this case,
 the version number should not contain a debian revision part.
 .
 Native source packages are sometimes created by accident. In most cases
 the reason is the location of the original source tarball. dpkg-source
 searches for this in ../package_upstream-version.orig.tar.gz.

Tag: diff-contains-substvars
Type: warning
Info: Lintian found a substvars file in the Debian diff for this source 
 package. The debian/substvars file is usually generated and modified
 dynamically by debian/rules targets, in which case it must be removed by
 the clean target.
Ref: policy 4.9