On Wed, Apr 11, 2018 at 10:34:06AM (+0300), Hleb Valoshka wrote:
> Please see attached file. It fixes the failure.
Hi,
Thanks Hleb !!
Just added your patch here
https://salsa.debian.org/puppet-team/ruby-gettext-setup/blob/master/debian/patches/0003-fix-invalid-byte-sequence-in-US-ASCII.patch
Ch
On 4/5/18, Georg Faerber wrote:
>> /usr/lib/ruby/vendor_ruby/gettext/tools/parser/ruby.rb is UTF-8 file,
Oops, wrong file. spec/lib/gettext-setup/gettext_setup_spec.rb is a proper one.
> Please go ahead and feel free to fix the package; I failed to do so
> yesterday, but I've to admit, I didn't
Hi,
On 18-04-04 23:58:32, Hleb Valoshka wrote:
> On 4/4/18, Georg Faerber wrote:
> > ruby-gettext-setup FTBFS now, with errors like
> >
> > /usr/lib/ruby/vendor_ruby/gettext/tools/parser/ruby.rb:50:in `gsub':
> > invalid byte sequence in US-ASCII (ArgumentError)
erested in how you came to this conclusion:
I did `fgrep -R require | fgrep gettext` and saw nothing (actually
this gem uses rxgettext from ruby-gettext).
> ruby-gettext-setup FTBFS now, with errors like
>
> /usr/lib/ruby/vendor_ruby/gettext/tools/parser/ruby.rb:50:in `gsub': invalid
> b
;ve checked ruby-gettext-setup and can say that it doesn't actually
> use anything from gettext gem, only from fast-gettext. So its test
> failures caused by something else, not the new gettext version.
I would be interested in how you came to this conclusion:
ruby-gettext-setup FTBFS now,
5 matches
Mail list logo