{"id":624,"date":"2008-02-20T09:39:57","date_gmt":"2008-02-20T14:39:57","guid":{"rendered":"http:\/\/blogs.law.harvard.edu\/hoanga\/2008\/02\/20\/getting-screwed-by-an-upgrade-libtidy-"},"modified":"2008-02-20T09:39:57","modified_gmt":"2008-02-20T14:39:57","slug":"getting-screwed-by-an-upgrade-libtidy-in-ubuntu-804-not-ready-for-r","status":"publish","type":"post","link":"https:\/\/archive.blogs.harvard.edu\/hoanga\/2008\/02\/20\/getting-screwed-by-an-upgrade-libtidy-in-ubuntu-804-not-ready-for-r\/","title":{"rendered":"Getting screwed by an upgrade (libtidy in Ubuntu 8.04 not ready for real work)"},"content":{"rendered":"<p>On my workstation at work I&#8217;ve been running Ubuntu 8.04 to test out something I&#8217;ll post on later.  However, one thing that was driving me nuts was that tidy was blowing up with a very unhelpful message like so:<\/p>\n<blockquote><p>\n\/usr\/lib\/ruby\/1.8\/tidy\/tidybuf.rb:39: [BUG] Segmentation fault\n<\/p><\/blockquote>\n<p>At first I thought it was some incompatibility with the gem installed version of tidy however after a bit more searching it seems tied with a specific bug in Debian that is <a href=\"http:\/\/groups.google.com\/group\/linux.debian.bugs.dist\/browse_thread\/thread\/2090a2a92dac4267\/859f841b6cb89654\">logged here<\/a>.   Basically, the recent version of libtidy has some sort of instability that will blow up on certain types of HTML input.  Kind of not useful I say&#8230;<\/p>\n<p>Looks like this has been fixed in Debian unstable so this might be a perfect candidate to have merged into Ubuntu since this really sucks inheriting a package bug.<\/p>\n<p><a href=\"http:\/\/bugs.debian.org\/cgi-bin\/bugreport.cgi?bug=462325\">Read the Bug Report<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>On my workstation at work I&#8217;ve been running Ubuntu 8.04 to test out something I&#8217;ll post on later. However, one thing that was driving me nuts was that tidy was blowing up with a very unhelpful message like so: \/usr\/lib\/ruby\/1.8\/tidy\/tidybuf.rb:39: [BUG] Segmentation fault At first I thought it was some incompatibility with the gem installed [&hellip;]<\/p>\n","protected":false},"author":703,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1100,1217],"tags":[],"class_list":["post-624","post","type-post","status-publish","format-standard","hentry","category-linux","category-stupid"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/archive.blogs.harvard.edu\/hoanga\/wp-json\/wp\/v2\/posts\/624","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/archive.blogs.harvard.edu\/hoanga\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/archive.blogs.harvard.edu\/hoanga\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/hoanga\/wp-json\/wp\/v2\/users\/703"}],"replies":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/hoanga\/wp-json\/wp\/v2\/comments?post=624"}],"version-history":[{"count":0,"href":"https:\/\/archive.blogs.harvard.edu\/hoanga\/wp-json\/wp\/v2\/posts\/624\/revisions"}],"wp:attachment":[{"href":"https:\/\/archive.blogs.harvard.edu\/hoanga\/wp-json\/wp\/v2\/media?parent=624"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/hoanga\/wp-json\/wp\/v2\/categories?post=624"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/hoanga\/wp-json\/wp\/v2\/tags?post=624"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}