I can confirm that the new version in debian resolved this issue. I've prepared a merge from Debian. Subscribing ubuntu-release for guidance.
Do we want the newest version in Jaunty? It would be helpful (beyond fixing this bug) for those of us working on packages for Debian as the new release uses Standards Version 3.8.1 Though I don't know what Ubuntu policy is on something like this. Should this wait for jaunty-backports? If ubuntu-release decides to hold off on this, I could prepare a patch for this bug alone. Upstream git commit resolving this issue: http://git.debian.org/?p=lintian/lintian.git;a=commitdiff;h=1dcd45e8941505fe78995036a4f697ab43f31106 ** Attachment added: "diff from debian" http://launchpadlibrarian.net/24762433/debian%3Eubuntu -- internal error: command failed with error code 123 https://bugs.launchpad.net/bugs/351901 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
