Your message dated Thu, 30 May 2013 16:43:57 +0200
with message-id <20130530144357.ga7...@hephaistos.amsuess.com>
and subject line Re: lolcat: chokes upon invalid utf-u
has caused the Debian Bug report #705799,
regarding lolcat: chokes upon invalid utf-u
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
705799: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705799
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lolcat
Version: 42.0.99-1
Severity: normal
Hi,
lolcatting a file containing an invalid utf-8 character when it's not
expected, like in
Helenenstra�e 22
(I'll try to attach the file for testing)
leads to an exception:
/usr/lib/ruby/vendor_ruby/lolcat/lol.rb:45:in `gsub!': invalid byte sequence
/in UTF-8 (ArgumentError)
from /usr/lib/ruby/vendor_ruby/lolcat/lol.rb:45:in `println'
from /usr/lib/ruby/vendor_ruby/lolcat/lol.rb:36:in `block in cat'
from /usr/lib/ruby/vendor_ruby/lolcat/lol.rb:34:in `each'
from /usr/lib/ruby/vendor_ruby/lolcat/lol.rb:34:in `cat'
from /usr/lib/ruby/vendor_ruby/lolcat/cat.rb:113:in `block in cat!'
from /usr/lib/ruby/vendor_ruby/lolcat/cat.rb:107:in `each'
from /usr/lib/ruby/vendor_ruby/lolcat/cat.rb:107:in `cat!'
from /usr/games/lolcat:24:in `<main>'
-- System Information:
Debian Release: 7.0
APT prefers proposed-updates
APT policy: (500, 'proposed-updates'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.8-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages lolcat depends on:
ii ruby 1:1.9.3
ii ruby-paint 0.8.5-1
ii ruby-trollop 1.16.2-3
ii ruby1.8 [ruby-interpreter] 1.8.7.358-7
ii ruby1.9.1 [ruby-interpreter] 1.9.3.194-8.1
lolcat recommends no packages.
lolcat suggests no packages.
-- no debconf information
Helenenstraße 22
--- End Message ---
--- Begin Message ---
On Sat, Apr 20, 2013 at 11:25:06PM +0200, chrysn wrote:
> can you demonstrate a behavior where it can be argued that the input is
> valid and lolcat still errs out? so far, i'd say that "invalid byte
> sequence" is a valid reaction to invalid input data.
closing this bug after a month of inactivity, not having observed any
behavior that would seem erroneous to me.
if you have an example in which lolcat's behavior can be enhanced,
please open a new bug report.
best regards
chrysn
--
When others do a foolish thing, you should tell them it is a foolish
thing. They can still continue to do it, but at least the truth is where
it needs to be.
-- Dukhat
signature.asc
Description: Digital signature
--- End Message ---
_______________________________________________
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
