On Thu, Dec 18, 2014 at 4:30 PM, Yavor Doganov <ya...@gnu.org> wrote:
>
> It seems that there are two different problems -- Santiago's failure
> that he posted on the bug log is at dhelp.rb:185 while mine is at
> debian.rb:914 (which is why I suggested it might be a ruby-debian
> issue). If you and Daniel have reproduced and fixed Santiago's bug it
> is not surprising that the NMU does not address the bug I am
> observing. (At least that is how I explain the mystery for the time
> being, with my limited knowledge.)
Yes, that's my understanding, too.
Can you run with the attached patch to debian.rb, and see if it will show
which entry of which file triggers the error?
--- /usr/lib/ruby/vendor_ruby/debian.rb.orig 2014-12-18 19:01:03.233496178 -0100
+++ /usr/lib/ruby/vendor_ruby/debian.rb.debug 2014-12-18 19:00:26.229041877 -0100
@@ -911,7 +911,14 @@
@provides = {}
@file = [file]
@lists = Archives.parseArchiveFile(file) {|info|
- info =~ /Package:\s(.*)$/;
+ begin
+ info =~ /Package:\s(.*)$/;
+ rescue => e
+ puts "Error parsing file #{file}"
+ puts "Contents of info:"
+ puts info
+ raise e
+ end
if pkgs.empty? || pkgs.include?($1)
d = Deb.new(info,fields)
add_provides(d)
