Additionally to the gconf dependencies, I think lintian should check
packages for FHS compliance on this matter.
First, any file shipped in /etc/gconf/schemas is a bug.
Second, any package calling gconftool or gconftool-2 directly in the
maintainer scripts is most likely buggy, because it should
Package: lintian
Version: 1.23.21
Severity: normal
--- /usr/share/lintian/checks/common_data.pm.orig 2006-05-15
03:05:45.0 +
+++ /usr/share/lintian/checks/common_data.pm2006-05-15 03:08:32.0
+
@@ -15,7 +15,7 @@
# simple defines for commonly needed data
Lior Kaplan [EMAIL PROTECTED] writes:
Package: lintian
Version: 1.23.21
Severity: normal
--- /usr/share/lintian/checks/common_data.pm.orig 2006-05-15
03:05:45.0 +
+++ /usr/share/lintian/checks/common_data.pm2006-05-15 03:08:32.0
+
@@ -15,7 +15,7 @@
#
Package: lintian
Version: 1.23.16
Severity: wishlist
gzip crc errors in the components of a .deb (conrol.tar.gz and
data.tar.gz) should be detected and reported as a lintian error.
For example, #364293 should thusly have been detected by lintian (not
that it'd have helped in this case, as
4 matches
Mail list logo