lintian.debian.org
Hello, lintian.debian.org for conky lists warnings about long changelog entries and national encodings in copyright files which were fixed in version 1.4.9-2 (at least according to the local installation of lintian version 1.23.41). The problem is perhaps that it refers to version 1.4.9-2 but has actually only checked 1.4.9-1 since 1.4.9-2 has not yet been built for i386 (as per the buildd.debian.org data at Thu, 27 Dec 2007 11:00 UTC). The source package for 1.4.9-2 and the binary for arm were uploaded yesterday. Perhaps there is some fix so that it only displays information about the actual version(s) checked. Regards, Kapil. -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
erroneous Lintian report
Greetings, My Lintian report at http://lintian.debian.org/reports/maintainer/q-funk%40iki.fi.html states that: Source package: rus-ispell (0.99g4-7) W: irussian binary: debian-copyright-file-uses-obsolete-national-encoding at line 3 Yet fetching the current package from pool and extracting gives me this: dpkg-source: extracting rus-ispell in rus-ispell-0.99g4 dpkg-source: unpacking rus-ispell_0.99g4.orig.tar.gz dpkg-source: applying ./rus-ispell_0.99g4-7.diff.gz [EMAIL PROTECTED]:/home/q-funk/Projects$ cd rus-ispell-0.99g4/ [EMAIL PROTECTED]:/home/q-funk/Projects/rus-ispell-0.99g4$ file debian/copyright debian/copyright: UTF-8 Unicode English text [EMAIL PROTECTED]:/home/q-funk/Projects/rus-ispell-0.99g4$ Did I miss anything? Isn't UTF-8 the standard these days? -- Martin-Éric Racine http://q-funk.iki.fi
Re: lintian.debian.org
Kapil Hari Paranjape [EMAIL PROTECTED] writes: lintian.debian.org for conky lists warnings about long changelog entries and national encodings in copyright files which were fixed in version 1.4.9-2 (at least according to the local installation of lintian version 1.23.41). The problem is perhaps that it refers to version 1.4.9-2 but has actually only checked 1.4.9-1 since 1.4.9-2 has not yet been built for i386 (as per the buildd.debian.org data at Thu, 27 Dec 2007 11:00 UTC). The source package for 1.4.9-2 and the binary for arm were uploaded yesterday. Perhaps there is some fix so that it only displays information about the actual version(s) checked. Yeah, this is a long-standing problem. It's a little tricky to fix, so could you file a bug against the lintian package so that I don't lose track of it? -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: erroneous Lintian report
Martin-Éric Racine [EMAIL PROTECTED] writes: My Lintian report at http://lintian.debian.org/reports/maintainer/q-funk%40iki.fi.html states that: Source package: rus-ispell (0.99g4-7) W: irussian binary: debian-copyright-file-uses-obsolete-national-encoding at line 3 Yet fetching the current package from pool and extracting gives me this: dpkg-source: extracting rus-ispell in rus-ispell-0.99g4 dpkg-source: unpacking rus-ispell_0.99g4.orig.tar.gz dpkg-source: applying ./rus-ispell_0.99g4-7.diff.gz [EMAIL PROTECTED]:/home/q-funk/Projects$ cd rus-ispell-0.99g4/ [EMAIL PROTECTED]:/home/q-funk/Projects/rus-ispell-0.99g4$ file debian/copyright debian/copyright: UTF-8 Unicode English text [EMAIL PROTECTED]:/home/q-funk/Projects/rus-ispell-0.99g4$ Did I miss anything? Isn't UTF-8 the standard these days? No, the problem is that irussian wasn't built yet for i386 when the last lintian run happened, so it was actually checking the old package. This is a long-standing bug in lintian that I haven't had a chance to fix. I'm thinking about completely rewriting the HTML report generation script and will try to fix this at the same time. It should produce good results as soon as irussian is built for i386. -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
Re: erroneous Lintian report
Martin-Éric Racine [EMAIL PROTECTED] writes: The problem seems to be that most uploads are done with i386 packages, so they seldom get built there. How about we switch Debian to source-only uploads while we're at it (as opposed to the current architecture upload)? This is a long-standing debate on debian-devel. Ubuntu went that way, I think. Some people are strongly in favor of it, and others are worried that source-only uploads will result in more build failures and more work for the buildd admins by making it much easier to upload packages that don't build at all. (It also means that all arch-independent packages would have to be built somewhere, but that's probably a minor implementation detail.) It's one of those debates that's been going on for years and never reaches any firm consensus, and hence nothing ever changes. -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
Re: erroneous Lintian report
On 12/27/07, Russ Allbery [EMAIL PROTECTED] wrote: Martin-Éric Racine [EMAIL PROTECTED] writes: My Lintian report at http://lintian.debian.org/reports/maintainer/q-funk%40iki.fi.html states that: Source package: rus-ispell (0.99g4-7) W: irussian binary: debian-copyright-file-uses-obsolete-national-encoding at line 3 Yet fetching the current package from pool and extracting gives me this: dpkg-source: extracting rus-ispell in rus-ispell-0.99g4 dpkg-source: unpacking rus-ispell_0.99g4.orig.tar.gz dpkg-source: applying ./rus-ispell_0.99g4-7.diff.gz [EMAIL PROTECTED]:/home/q-funk/Projects$ cd rus-ispell-0.99g4/ [EMAIL PROTECTED]:/home/q-funk/Projects/rus-ispell-0.99g4$ file debian/copyright debian/copyright: UTF-8 Unicode English text [EMAIL PROTECTED]:/home/q-funk/Projects/rus-ispell-0.99g4$ Did I miss anything? Isn't UTF-8 the standard these days? No, the problem is that irussian wasn't built yet for i386 when the last lintian run happened, so it was actually checking the old package. This is a long-standing bug in lintian that I haven't had a chance to fix. I'm thinking about completely rewriting the HTML report generation script and will try to fix this at the same time. It should produce good results as soon as irussian is built for i386. The problem seems to be that most uploads are done with i386 packages, so they seldom get built there. How about we switch Debian to source-only uploads while we're at it (as opposed to the current architecture upload)? -- Martin-Éric Racine http://q-funk.iki.fi
Processed: Patch for symbols support
Processing commands for [EMAIL PROTECTED]: tags 457067 + patch Bug#457067: lintian: Check symbols files and warn about usage of Debian revisions There were no tags set. Tags added: patch thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457067: Patch for symbols support
tags 457067 + patch
thanks
Hi,
Attached is a patch adding support for the checks that I requested. I'd
appreciate if it could be integrated quickly. Some review is welcome. It
worked quite well on the test package that I used:
http://ftp.debian.org/debian/pool/main/t/tokyocabinet/libtokyocabinet1_1.1.4-1_i386.deb
$ lintian libtokyocabinet1_1.1.4-1_i386.deb
E: libtokyocabinet1: symbols-file-contains-current-version-with-debian-revision
on symbol [EMAIL PROTECTED] and 3 others
W: libtokyocabinet1: symbols-file-contains-debian-revision on symbol [EMAIL
PROTECTED] and 321 others
Cheers,
--
Raphaël Hertzog
Le best-seller français mis à jour pour Debian Etch :
http://www.ouaza.com/livre/admin-debian/
diff -Nru /tmp/Yq0Lbe3ntH/lintian-1.23.41/checks/control-files /tmp/3p28KrBmDX/lintian-1.23.41/checks/control-files
--- /tmp/Yq0Lbe3ntH/lintian-1.23.41/checks/control-files 2007-11-21 00:12:21.0 +0100
+++ /tmp/3p28KrBmDX/lintian-1.23.41/checks/control-files 2007-12-27 19:21:22.0 +0100
@@ -107,8 +107,48 @@
}
close IN;
+if (-e control/symbols) {
+my $version = getfield(version);
+my $version_wo_rev = $version;
+$version_wo_rev =~ s/(.+)-(.+)/$1/;
+my ($full_version_count, $full_version_sym) = (0, undef);
+my ($debian_revision_count, $debian_revision_sym) = (0, undef);
+open(IN, , control/symbols);
+while (IN) {
+ next if not /^\s+(\S+)\s(\S+)(?:\s(\d+))?/;
+ my ($sym, $v, $dep_order) = ($1, $2, $3);
+ if (($v eq $version) and ($version =~ /-/)) {
+ $full_version_sym ||= $sym;
+ $full_version_count++;
+ }
+ if (($v =~ /-/) and (not $v =~ /~$/) and ($v ne $version_wo_rev)) {
+ $debian_revision_sym ||= $sym;
+ $debian_revision_count++;
+ }
+}
+close IN;
+if ($full_version_count) {
+ $full_version_count--;
+ tag symbols-file-contains-current-version-with-debian-revision,
+ on symbol $full_version_sym and $full_version_count others;
+}
+if ($debian_revision_count) {
+ $debian_revision_count--;
+ tag symbols-file-contains-debian-revision,
+ on symbol $debian_revision_sym and $debian_revision_count others;
+}
+}
+
} # /run
+sub getfield {
+return undef if not open (FIELD, '', fields/ . shift);
+my $field = FIELD;
+close FIELD;
+$field =~ s/\n$//;
+return $field;
+}
+
1;
# vim: syntax=perl sw=4 ts=8
diff -Nru /tmp/Yq0Lbe3ntH/lintian-1.23.41/checks/control-files.desc /tmp/3p28KrBmDX/lintian-1.23.41/checks/control-files.desc
--- /tmp/Yq0Lbe3ntH/lintian-1.23.41/checks/control-files.desc 2007-12-07 05:39:02.0 +0100
+++ /tmp/3p28KrBmDX/lintian-1.23.41/checks/control-files.desc 2007-12-27 19:32:16.0 +0100
@@ -26,3 +26,28 @@
Tag: control-file-has-bad-owner
Type: error
Info: All control files should be owned by root/root.
+
+Tag: symbols-file-contains-current-version-with-debian-revision
+Type: error
+Info: By default, dpkg-gensymbols uses the full version number for the
+ dependency associated to any new symbol that it detects. But this
+ shouldn't happen as the maintainer should have updated before-hand the
+ debian/lt;packagegt;.symbols file by adding the new symbols with the
+ corresponding upstream version.
+ .
+ Debian revisions should be stripped from symbols files because not doing
+ it leads to dependencies unsatisfiable by backports (1.0-1~bpo lt;lt; 1.0-1
+ while 1.0-1~bpo gt;= 1.0). If the debian revision can't be stripped because
+ the symbol really appearead between two specific revisions, then you
+ should postfix the version with a single ~ (example: 1.0-3~ if the
+ symbol appeared in 1.0-3).
+
+Tag: symbols-file-contains-debian-revision
+Type: warning
+Info: Debian revisions should be stripped from symbols files because not doing
+ it leads to dependencies unsatisfiable by backports (1.0-1~bpo lt;lt; 1.0-1
+ while 1.0-1~bpo gt;= 1.0). If the debian revision can't be stripped because
+ the symbol really appearead between two specific revisions, then you
+ should postfix the version with a single ~ (example: 1.0-3~ if the
+ symbol appeared in 1.0-3).
+
diff -Nru /tmp/Yq0Lbe3ntH/lintian-1.23.41/debian/changelog /tmp/3p28KrBmDX/lintian-1.23.41/debian/changelog
--- /tmp/Yq0Lbe3ntH/lintian-1.23.41/debian/changelog 2007-12-10 05:03:03.0 +0100
+++ /tmp/3p28KrBmDX/lintian-1.23.41/debian/changelog 2007-12-27 19:36:29.0 +0100
@@ -1,3 +1,10 @@
+lintian (1.23.41-0.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Add checks on symbols files. Closes: #457067
+
+ -- Raphael Hertzog [EMAIL PROTECTED] Mon, 24 Dec 2007 10:31:34 +0100
+
lintian (1.23.41) unstable; urgency=low
The it would be lovely if there were an actual desktop file standard
Bug#293296: See what our store has to offer
Great Gift ideas online Top Quality for Men, Women and Kids http://syoldyear.com M#232;re and P#232;re Chose are walking away from the Onto my frozen fingers. their bellies, they're out cold, instantaneously -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#458036: lintian.debian.org shows warnings about wrong version
Package: lintian Version: 1.23.41 Severity: minor Hello, lintian.debian.org should list only print warnings about the version it actually checked rather than the latest package in the archive. In more detail: (the following was sent in a mail to lintian-maint and Russ Allberry suggested filing a bug report.) lintian.debian.org (on 27 Dec 2007 11:00 UTC) for conky lists warnings about long changelog entries and national encodings in copyright files which were fixed in version 1.4.9-2 (at least according to the local installation of lintian version 1.23.41). The problem is perhaps that it refers to version 1.4.9-2 but has actually only checked 1.4.9-1 since 1.4.9-2 has not yet been built for i386 (as per the buildd.debian.org data at Thu, 27 Dec 2007 11:00 UTC). The source package for 1.4.9-2 and the binary for arm were uploaded yesterday. Regards, Kapil. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.22-3-vserver-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages lintian depends on: ii binutils2.18.1~cvs20071027-1 The GNU assembler, linker and bina ii diffstat1.45-2 produces graph of changes introduc ii dpkg-dev1.14.7 package building tools for Debian ii file4.21-3 Determines file type using magic ii gettext 0.16.1-2 GNU Internationalization utilities ii intltool-debian 0.35.0+20060710.1Help i18n of RFC822 compliant conf ii libparse-debianchan 1.1.1-1 parse Debian changelogs and output ii liburi-perl 1.35.dfsg.1-1Manipulates and accesses URI strin ii man-db 2.5.0-4 on-line manual pager ii perl [libdigest-md5 5.8.8-12 Larry Wall's Practical Extraction lintian recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
