Re: Next upload?
On Tue, Jul 08, 2008 at 06:53:02PM +0100, Adam D. Barratt wrote:
> On that subject, are there any plans / thoughts as to when the next
> release might be? IMHO, we've got a good (for want of a better word that
> escapes me right now) set of changes since the last upload.
Before the next upload it would be interesting to apply the attached
patch, which basically fixes two typos in tag descriptions, updates some
references (it looks like policy 7.6 became 7.7 in 3.8.0), and includes
a few more references (FHS and devref's Collaborative maintenance
section).
diff --git a/checks/binaries.desc b/checks/binaries.desc
index f8f0d4d..6a84e3e 100644
--- a/checks/binaries.desc
+++ b/checks/binaries.desc
@@ -98,11 +98,13 @@ Info: The listed shared library doesn't include information about which
Tag: arch-dependent-file-in-usr-share
Type: error
+Ref: fhs 4.11
Info: This package installs an ELF binary in the <tt>/usr/share</tt>
hierarchy, which is reserved for architecture-independent files.
Tag: binary-in-etc
Type: error
+Ref: fhs 3.7
Info: This package installs an ELF binary in <tt>/etc</tt>.
The Filesystem Hierarchy Standard forbids this.
diff --git a/checks/changelog-file.desc b/checks/changelog-file.desc
index ab1b391..cb2e7bc 100644
--- a/checks/changelog-file.desc
+++ b/checks/changelog-file.desc
@@ -166,7 +166,7 @@ Info: The latest Debian changelog entry has a version number that's either
Tag: syntax-error-in-debian-changelog
Type: warning
-Info: While parsing the Debian changelog, an syntax error was found.
+Info: While parsing the Debian changelog, a syntax error was found.
Ref: policy 4.4
Tag: syntax-error-in-debian-news-file
diff --git a/checks/fields.desc b/checks/fields.desc
index 75f675c..9d7d932 100644
--- a/checks/fields.desc
+++ b/checks/fields.desc
@@ -189,6 +189,7 @@ Type: warning
Info: The Maintainer address for this package is a mailing list and there
are no Uploaders listed. Team-maintained packages should list the human
maintainers in the Uploaders field.
+Ref: devref 5.12
Tag: no-source-field
Type: error
@@ -479,13 +480,13 @@ Ref: policy 11.8.5
Tag: build-depends-indep-without-arch-indep
Type: error
-Ref: policy 7.6
+Ref: policy 7.7
Info: The control file specifies source relations for architecture-independent
packages, but no architecture-independent packages are built.
Tag: build-depends-without-arch-dep
Type: info
-Ref: policy 7.6
+Ref: policy 7.7
Info: The control file lists the given package in Build-Depends, but no
architecture-dependent packages are built. If all the packages built are
architecture-independent, the only packages that should be listed in
@@ -495,7 +496,7 @@ Info: The control file lists the given package in Build-Depends, but no
Tag: clean-should-be-satisfied-by-build-depends
Type: error
-Ref: policy 7.6
+Ref: policy 7.7
Info: The specified package is required to run the clean target of
<tt>debian/rules</tt> and therefore must be listed in Build-Depends, not
Build-Depends-Indep, even if no architecture-dependent packages are
@@ -541,7 +542,7 @@ Info: The package runs dh_python in <tt>debian/rules</tt> but doesn't
Tag: build-conflicts-with-build-dependency
Type: error
-Ref: policy 7.6
+Ref: policy 7.7
Info: The package build-conflicts with a package that it also
build-depends on.
@@ -647,7 +648,7 @@ Info: This package declares a Breaks relationship with another package
that has no version number. Normally, Breaks should be used to indicate
an incompatibility with a specific version of another package, or with
all versions predating a fix. If the two packages can never be installed
- at the same time, Conflicts should normally be uesd instead.
+ at the same time, Conflicts should normally be used instead.
Tag: bad-menu-item
Type: error
@@ -684,7 +685,7 @@ Info: You use the Bugs field though the field value is the default
Tag: build-depends-on-build-essential
Type: error
-Ref: policy 7.6
+Ref: policy 7.7
Info: You depends on the build-essential package, which is only a
meta-package depending on build tools that have to be installed in all
build environments.
Reply to: