Bug#557023: Barby::Code128: private method split called for nil

tags 557023 = pending thanks Hmm... Looking more closely to your submitted patches: The second part makes sense (using an empty string when a nil is presented), although its correctness might be stylistic (i.e. some authors prefer to raise an exception on an anomalous condition, which you can

Bug#557023: Barby::Code128: private method split called for nil

tags 557023 + upstream, forwarded, pending thanks Hi, I have forwarded your report to the upstream list, and will be applying it shortly for the Debian package regardless. Thanks a lot, -- Gunnar Wolf • gw...@gwolf.org • (+52-55)5623-0154 / 1451-2244 signature.asc Description: Digital

Bug#557023: Barby::Code128: private method split called for nil

Package: libbarby-ruby1.8 Version: 0.3-1 Severity: normal Tags: patch Creating a new instance of Barby::Code128 with a legitimate string can cause a stack trace. One such string is the empty string: Barby::Code128.new(, 'B') The stack trace is:

Bug#557023: (Barby::Code128: private method split called for nil)

My apologies. The patch I submitted with the original report is incomplete. It fixes the case in foo.rb with the non-empty string, but does not fix the empty string case. Attached is the complete patch. diff -ur libbarby-ruby-0.3.orig/lib/barby/barcode/code_128.rb