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]
