Bug#768127: Fails to build the index when invalid UTF-8 is met

2014-12-19 Thread gregor herrmann
On Fri, 19 Dec 2014 07:57:15 +0200, Yavor Doganov wrote: > > Right, cloning+reassigning to ruby-debian might make sense. > > Let's do this :) > > (And close the original bug since it does fix another problem.) > Thanks. I used "dpkg --update-avail" to get rid of that ancient > package and now dhe

Processed: Re: Bug#768127: Fails to build the index when invalid UTF-8 is met

2014-12-19 Thread Debian Bug Tracking System
Processing control commands: > severity 773485 normal Bug #773485 [ruby-debian] Fails to build the index when invalid UTF-8 is met Severity set to 'normal' from 'grave' -- 768127: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768127 773485: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773

Bug#768127: Fails to build the index when invalid UTF-8 is met

2014-12-19 Thread Antonio Terceiro
Control: severity 773485 normal On Thu, Dec 18, 2014 at 11:19:31PM +0100, gregor herrmann wrote: > Probably the severity in the cloned bug in ruby-debian shoule be > lowered; the problem might not be present if a non-UTF-9 file is not > opened as UTF-8 ... yes -- Antonio Terceiro signature.a

Bug#768127: Fails to build the index when invalid UTF-8 is met

2014-12-18 Thread Yavor Doganov
gregor herrmann wrote: > On Thu, 18 Dec 2014 21:02:58 -0100, Daniel Getz wrote: > > However, the code in question is in ruby-debian, which is a > > separate library used by other packages. Might not be correct > > behavior for other users of the library? > > Right, cloning+reassigning to ruby-debi

Bug#768127: Fails to build the index when invalid UTF-8 is met

2014-12-18 Thread gregor herrmann
Control: clone -1 -2 Control: reassign -2 ruby-debian Control: affects -2 dhelp Control: close -1 768127 0.6.21+nmu6 On Thu, 18 Dec 2014 21:02:58 -0100, Daniel Getz wrote: > > While I would like dhelp to handle this situation a bit more > > gracefully, I suggest to downgrade the severity of the b

Processed: Re: Bug#768127: Fails to build the index when invalid UTF-8 is met

2014-12-18 Thread Debian Bug Tracking System
Processing control commands: > clone -1 -2 Bug #768127 [dhelp] Fails to build the index when invalid UTF-8 is met Bug 768127 cloned as bug 773485 > reassign -2 ruby-debian Bug #773485 [dhelp] Fails to build the index when invalid UTF-8 is met Bug reassigned from package 'dhelp' to 'ruby-debian'. N

Bug#768127: Fails to build the index when invalid UTF-8 is met

2014-12-18 Thread Daniel Getz
On Thu, Dec 18, 2014 at 8:49 PM, gregor herrmann wrote: > Ok, so what are we doing now? > > While I would like dhelp to handle this situation a bit more > gracefully, I suggest to downgrade the severity of the bug since it > shouldn't affect anyone running packages contained in recent and > upcom

Bug#768127: Fails to build the index when invalid UTF-8 is met

2014-12-18 Thread gregor herrmann
On Thu, 18 Dec 2014 23:25:06 +0200, Yavor Doganov wrote: > Daniel Getz wrote: > > Can you run with the attached patch to debian.rb, and see if it will > > show which entry of which file triggers the error? > Thanks; here's the output: > Error parsing file /var/lib/dpkg/available Wow, that's an i

Bug#768127: Fails to build the index when invalid UTF-8 is met

2014-12-18 Thread Yavor Doganov
Daniel Getz wrote: > Can you run with the attached patch to debian.rb, and see if it will > show which entry of which file triggers the error? Thanks; here's the output: Error parsing file /var/lib/dpkg/available Contents of info: Package: ayuda Priority: extra Section: misc Installed-Size: 204 M

Bug#768127: Fails to build the index when invalid UTF-8 is met

2014-12-18 Thread gregor herrmann
On Thu, 18 Dec 2014 19:30:32 +0200, Yavor Doganov wrote: > > So according to the previous findings, my guess is that > > /var/lib/doc-base/documents/xterm-faq can't be interpreted as UTF-8. > I don't think this has anything to do with xterm-faq, it's just that > this is the last file in alphabetic

Bug#768127: Fails to build the index when invalid UTF-8 is met

2014-12-18 Thread Daniel Getz
On Thu, Dec 18, 2014 at 4:30 PM, Yavor Doganov 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 r

Bug#768127: Fails to build the index when invalid UTF-8 is met

2014-12-18 Thread Yavor Doganov
gregor herrmann wrote: > > /var/lib/doc-base/documents/xterm-ctlseqs > > /var/lib/doc-base/documents/xterm-faq > > ArgumentError: invalid byte sequence in UTF-8 > > (/usr/lib/ruby/vendor_ruby/debian.rb:914:in `block in initialize' > > So according to the previous findings, my guess is that > /var

Bug#768127: Fails to build the index when invalid UTF-8 is met

2014-12-18 Thread gregor herrmann
On Thu, 18 Dec 2014 18:24:53 +0200, Yavor Doganov wrote: > > I guess it would be helpful if you could try to > > - add a "puts @path" in /usr/lib/ruby/vendor_ruby/dhelp.rb:184 > > (see Santiago's message #24); > > - copy the output of `locale' and `/etc/cron.weekly/dhelp'; Thanks! > $ locale

Bug#768127: Fails to build the index when invalid UTF-8 is met

2014-12-18 Thread Yavor Doganov
gregor herrmann wrote: > On Thu, 18 Dec 2014 12:01:02 +0200, Yavor Doganov wrote: > > Thanks for your work, but unfortunately I experience exactly the > > same problem with the new version. > > I guess it would be helpful if you could try to > - add a "puts @path" in /usr/lib/ruby/vendor_ruby/dhel

Bug#768127: Fails to build the index when invalid UTF-8 is met

2014-12-18 Thread gregor herrmann
On Thu, 18 Dec 2014 12:01:02 +0200, Yavor Doganov wrote: > Thanks for your work, but unfortunately I experience exactly the same > problem with the new version. > > $ isutf8 /var/lib/doc-base/documents/* > $ echo $? > 0 Ouch. I'm sorry to hear this. Could you please provide a bit more informati

Bug#768127: Fails to build the index when invalid UTF-8 is met

2014-12-18 Thread Yavor Doganov
reopen 768127 notfixed 768127 0.6.21+nmu6 thanks Thanks for your work, but unfortunately I experience exactly the same problem with the new version. $ isutf8 /var/lib/doc-base/documents/* $ echo $? 0 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubsc

Processed: Re: Bug#768127: Fails to build the index when invalid UTF-8 is met

2014-12-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reopen 768127 Bug #768127 {Done: gregor herrmann } [dhelp] Fails to build the index when invalid UTF-8 is met 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add

Bug#768127: Fails to build the index when invalid UTF-8 is met

2014-12-07 Thread Daniel Getz
UTF-8 should be the right format for doc-base files, according to https://lintian.debian.org/tags/doc-base-file-uses-obsolete-national-encoding.html I also don't know ruby, but from my research setting Encoding.default_external is considered the "wrong" thing to do, the "right" way being to pass "

Processed: Re: Bug#768127: Fails to build the index when invalid UTF-8 is met

2014-12-07 Thread Debian Bug Tracking System
Processing control commands: > tag -1 - moreinfo Bug #768127 [dhelp] Fails to build the index when invalid UTF-8 is met Removed tag(s) moreinfo. > tag -1 + confirmed Bug #768127 [dhelp] Fails to build the index when invalid UTF-8 is met Added tag(s) confirmed. -- 768127: http://bugs.debian.org/c

Bug#768127: Fails to build the index when invalid UTF-8 is met

2014-12-07 Thread gregor herrmann
Control: tag -1 - moreinfo Control: tag -1 + confirmed On Sat, 06 Dec 2014 01:33:58 -0100, Daniel Getz wrote: I can reproduce the problem with LC_ALL=C LANG=C /etc/cron.weekly/dhelp > Attached is a diff with a change to dhelp_parse.rb which sets > Encoding.default_external explicitly, so that ev

Bug#768127: Fails to build the index when invalid UTF-8 is met

2014-12-05 Thread Daniel Getz
Attached is a diff with a change to dhelp_parse.rb which sets Encoding.default_external explicitly, so that even if LANG=C, it uses UTF-8 instead of US-ASCII as the default for opening files. By my (limited) understanding of Encoding.default_external, this should have the same effect on opening fil

Bug#768127: Fails to build the index when invalid UTF-8 is met

2014-12-04 Thread Santiago
Package: dhelp Version: 0.6.21+nmu5 Followup-For: Bug #768127 I don't know if it helps, but I got a similar error from the weekly cron task. LANG=C sudo /etc/cron.weekly/dhelp ArgumentError: invalid byte sequence in US-ASCII (/usr/lib/ruby/vendor_ruby/dhelp.rb:185:in `===' /usr/lib/ruby/vendor_r