has lintian developed a ruby (bang) related bug?

2006-08-30 Thread ralph . amissah
This should have been filed as a bug report, but is a bit too messy, I
hope it is ok that I send as post. I started writing a bug report on the
26th and abandoned it - because if it is a bug, it did not work in the
way I expected it to, i.e. I was unable to find it in another package
where I expected it should also be found. However, I still have no
explanation for it, and have done a number of checks, and the mystery
lintian error occurs on packages that previously build cleanly, so I
post you my quandary.

Has lintian has developed a ruby related bug)?, it appears to no longer
recognise ruby bangs in some packages (not in others for the same bang,
I have not been able to isolate why).

This error now appears in new builds and attempts to redo old builds
that previously built without warnings (and have used pbuilder):

Now running lintian...
E: sisu: ruby-script-but-no-ruby-dep ./usr/bin/sisu
E: sisu: ruby-script-but-no-ruby-dep ./usr/bin/sisu_webrick
E: sisu: ruby-script-but-no-ruby-dep ./usr/bin/sisu_termsheet
Finished running lintian.

test packages
dget -x http://ftp.debian.org/debian/pool/main/s/sisu/sisu_0.46.1-1.dsc
and
dget -x http://www.jus.uio.no/sisu/pkg/src/sisu_0.46.2-1.dsc

(i) error is reported on versions that previously built without error

(ii) have checked the control file, ruby depends (appear to) look ok there

grep-aptavail -F Package -e '^sisu$' -s Package -s Version -s Depends
Package: sisu
Version: 0.46.2-1
Depends: ruby (= 1.8.2), libwebrick-ruby

(iii) within the files complained about i use a standard ruby bang variant:
#!/usr/bin/env ruby

have rebuilt to test using
#!/usr/bin/ruby

same error message

(iv) to check run linda, no error reported

(v) mysteriously my other package rant, has no such problem
dget -x http://ftp.debian.org/debian/pool/main/r/rant/rant_0.5.6-2.dsc

My apologies in advance if this is just me being obtuse.

-- System Information:
Debian Release: testing/unstable
 APT prefers unstable
 APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-1-486
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)

Versions of packages lintian depends on:
ii  binutils 2.17-2  The GNU assembler, linker and bina
ii  diffstat 1.43-1  produces graph of changes introduc
ii  dpkg-dev 1.13.22 package building tools for Debian
ii  file 4.17-3  Determines file type using magic
ii  gettext  0.15-1  GNU Internationalization utilities
ii  intltool-debian  0.35.0+20060710 Help i18n of RFC822 compliant conf
ii  libparse-debianchangelog 1.0-1   parse Debian changelogs and output
ii  man-db   2.4.3-3 The on-line manual pager
ii  perl [libdigest-md5-perl 5.8.8-6.1   Larry Wall's Practical Extraction

lintian recommends no packages.

 Problem with Lintian (or vice versa)
 
 (SiSU build or) Lintian bug (with ruby bangs?) - a rather verbose
 account (feedback/explanation/confirmation of issue welcome):
 
 It appears Lintian no longer recognises ruby bangs?? (it is late, who
 knows what i could be missing)
 
 This error now appears in new builds and attempts to redo old builds
 that previously built without warnings (and have used pbuilder):
 
 verbose lintian output:
 
 E: sisu: ruby-script-but-no-ruby-dep ./usr/bin/sisu
 N:
 N:   Packages with scripts that are executed with ruby must depend on the
 N:   package ruby. Those that have scripts executed with a versioned ruby
 N:   package need a dependency on the equivalent version of ruby.
 N:
 N:   For example, if a script in the package uses #!/usr/bin/ruby, then the
 N:   package needs a dependency on ruby. If a script uses
 N:   #!/usr/bin/ruby1.6, then the package need a dependency on ruby1.6.
 N:
 N:   In some cases a weaker relationship, such as Suggests or Recommends,
 N:   will be more appropriate.
 N:
 E: sisu: ruby-script-but-no-ruby-dep ./usr/bin/sisu_webrick
 E: sisu: ruby-script-but-no-ruby-dep ./usr/bin/sisu_termsheet
 
 (a) within the files complained about i use a standard ruby bang variant:
 #!/usr/bin/env ruby
 
 have rebuilt to test using
 #!/usr/bin/ruby
 
 same errors thrown
 
 (b) have checked the control file, ruby depends look ok there
 
 grep-aptavail -F Package -e '^sisu$' -s Package -s Version -s Depends
 Package: sisu
 Version: 0.46.2-1
 Depends: ruby (= 1.8.2), libwebrick-ruby
 
 (c) oh, and no such warnings from linda
 
 I started writing a bug report, but abandoned it when I got inconsistent
 reports from lintian (on other packages) for what I thought the bug must
 be - it threw an error on previous build of sisu, but not on rant, which
 by my reckoning should have met with the same issue... whether bug is in
 my builds or in lintian - my abandoned bug report is also attached


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]

Re: has lintian developed a ruby (bang) related bug?

2006-08-30 Thread Russ Allbery
ralph amissah [EMAIL PROTECTED] writes:

 This should have been filed as a bug report, but is a bit too messy, I
 hope it is ok that I send as post. I started writing a bug report on the
 26th and abandoned it - because if it is a bug, it did not work in the
 way I expected it to, i.e. I was unable to find it in another package
 where I expected it should also be found. However, I still have no
 explanation for it, and have done a number of checks, and the mystery
 lintian error occurs on packages that previously build cleanly, so I
 post you my quandary.

 Has lintian has developed a ruby related bug)?, it appears to no longer
 recognise ruby bangs in some packages (not in others for the same bang,
 I have not been able to isolate why).

There's a bug in the current version of lintian that causes it to
internally corrupt the dependency line in certain situations when checking
for script dependencies.  The result of that bug is that in some packages,
but not others, it will not see one of the dependencies and then produce
this warning.

It's already fixed in Subversion, and since it's a fairly annoying bug,
I'm going to try to get a new version of lintian uploaded by this weekend
with a fix.

-- 
Russ Allbery ([EMAIL PROTECTED])   http://www.eyrie.org/~eagle/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]