Hello,
I''m having problems getting Instiki to work on Kanotix (Debian-based
Linux). I followed the advice given on this page
http://instiki.org/show/Debian and installed all possible additional
packages and yet I still get the following error message when I try to
run it (after I type "ruby instiki.rb" or "ruby instiki"):
/home/user/instiki/vendor/rails/activesupport/lib/active_support/clean_logger.rb:13:in
`remove_const'': constant Logger::Format not defined (NameError)
from
/home/user/instiki/vendor/rails/activesupport/lib/active_support/clean_logger.rb:13
from
/home/user/instiki/vendor/rails/activesupport/lib/active_support.rb:31
from /home/user/instiki/config/environment.rb:52
from ./script/server:68
from instiki.rb:3
I''m still pretty much a beginner in Linux. I have Instiki up and
running on my webhosting server at Dreamhost without any problems,
except I can''t have it running in the background. Running it locally
(or even from a USB stick) would be far more convenient.
Any help is much welcome. Thanks in advance!
Johanka
Hi,> I''m having problems getting Instiki to work on Kanotix (Debian-based > Linux). I followed the advice given on this page > http://instiki.org/show/Debian and installed all possible additional > packages and yet I still get the following error message when I try to > run it (after I type "ruby instiki.rb" or "ruby instiki"):The debian packagers (which Ubuntu relies on) have done nasty things to the Ruby stdlib. Try building Ruby 1.8.4 from the source. HTH, Assaph
> The debian packagers (which Ubuntu relies on) have done nasty things > to the Ruby stdlib. Try building Ruby 1.8.4 from the source. >I did reinstall Ruby built from the source (the usual ./configure, make, make install), but I''m getting the same error message when trying to run Instiki... J.
Assaph,
Instead of repeatedly slandering the Debian packagers, it would be more
constructive to actually study the problem and understand what''s going
on.
http://bugs.debian.org/330400
This bug is resolved in Debian''s rails since September of last year.
Unfortunately, the instiki tarball forces you to use the rails packaged
with it, so that if you have ruby >= 1.8.3, Instiki breaks. This is not
Debian''s fault. It''s a consequence of Instiki not keeping up
with
current versions of ruby and rails.
See:
http://dev.rubyonrails.org/ticket/2245
So there you have it, plain and simple. The Debian packagers aren''t
incompetent, as you suppose.
Finally, if you read the fine print, http://instiki.org/show/Debian (or
at least the cached copy at Google, since the site seems to be down
right now) even mentions this problem and suggests a workaround, though
I can understand if you''ve missed it, as it is scanty on details:
From what I understand ruby1.8.3+ breaks things. I had to
specifically install ruby1.8.2 (ruby1.8=1.8.2-7sarge2)
?Timcad
I''d love to take my rough pre-packaging work on instiki and tidy it up
into a proper package for Debian, but I''m a bit reluctant to make a go
of it on my own with upstream development in a shambles. However, if
there were others interested in making it happen, I''d certainly be
happy
to help collaboratively maintain it.
Ben
(aka. synrg at debian dot org -- not a Ruby maintainer, though)
Hi Ben, Thanks muchly for the update. I am actually a debian (Ubuntu) usermyself. Love the system, hate what they did to Ruby - just didn''t havetime to catch up on updates as much as I should :-) Cheers,Assaph On 2/15/06, BG - Ben Armstrong <BArmstrong at dymaxion.ca> wrote:> Assaph,>> Instead of repeatedly slandering the Debian packagers, it would be more> constructive to actually study the problem and understand what''s going> on.>> http://bugs.debian.org/330400>> This bug is resolved in Debian''s rails since September of last year.> Unfortunately, the instiki tarball forces you to use the rails packaged> with it, so that if you have ruby >= 1.8.3, Instiki breaks. This is not> Debian''s fault. It''s a consequence of Instiki not keeping up with> current versions of ruby and rails.>> See:>> http://dev.rubyonrails.org/ticket/2245>> So there you have it, plain and simple. The Debian packagers aren''t> incompetent, as you suppose.>> Finally, if you read the fine print, http://instiki.org/show/Debian (or> at least the cached copy at Google, since the site seems to be down> right now) even mentions this problem and suggests a workaround, though> I can understand if you''ve missed it, as it is scanty on details:>> From what I understand ruby1.8.3+ breaks things. I had to> specifically install ruby1.8.2 (ruby1.8=1.8.2-7sarge2)> ?Timcad>> I''d love to take my rough pre-packaging work on instiki and tidy it up> into a proper package for Debian, but I''m a bit reluctant to make a go> of it on my own with upstream development in a shambles. However, if> there were others interested in making it happen, I''d certainly be happy> to help collaboratively maintain it.>> Ben> (aka. synrg at debian dot org -- not a Ruby maintainer, though)>>> _______________________________________________> Instiki-users mailing list> Instiki-users at rubyforge.org> http://rubyforge.org/mailman/listinfo/instiki-users
On Wed, 2006-02-15 at 06:53 +1100, Assaph Mehr wrote:> Hi Ben, > Thanks muchly for the update. I am actually a debian (Ubuntu) usermyself. Love the system, hate what they did to Ruby - just didn''t havetime to catch up on updates as much as I should :-) > Cheers,AssaphCuriously, I use ruby 1.8.3 + instiki 0.10.2 on Ubuntu Breezy, and it seems to work without throwing this error. I wonder why? Does it somehow pick up the 0.13.1 rails I have installed on the system in preference to the old broken one that ships with it? I haven''t had time to investigate. Fragmentation of ruby into individual libruby* packages is, I think, a necessary evil on a Debian system. However, the fragmentation doesn''t have to be as aggressive as it was initially, and I believe that has been remedied already. The other contentious issue was rubygems. The trouble is, ruby''s goals for rubygems, and Debian''s goals with their packaging system are somewhat at odds with each other. But I don''t think either side deliberately wants to make it hard for each other, so I remain optimistic that we''ll work out a mutually agreeable compromise. In short, although ruby and Debian''s relationship had a rocky start, it looks like things are stabilizing, so that running ruby applications on Debian won''t have to be a pulling-hair-out-at-the-roots experience. Ben -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/instiki-users/attachments/20060214/807166ed/attachment.htm
On Tue, 2006-02-14 at 16:08 -0400, BG - Ben Armstrong wrote:> On Wed, 2006-02-15 at 06:53 +1100, Assaph Mehr wrote: > > Hi Ben, > > Thanks muchly for the update. I am actually a debian (Ubuntu) usermyself. Love the system, hate what they did to Ruby - just didn''t havetime to catch up on updates as much as I should :-) > > Cheers,Assaph > Curiously, I use ruby 1.8.3 + instiki 0.10.2 on Ubuntu Breezy, and it > seems to work without throwing this error. I wonder why? Does it > somehow pick up the 0.13.1 rails I have installed on the system in > preference to the old broken one that ships with it? I haven''t had > time to investigate.So you''re essentially saying I should install a different Ruby and a different Rails? I have Ruby 1.8.3 on my Ubuntu Breezy, and the rails _I_ see in my Instiki is 0.13.1; my ruby is still throwing up the same errors I included in my previous message even after installing as many of the Ubuntu/Debian ruby packages as I could, as suggested by Assaph. I see the warning on the rails page to use 1.8.4, or .2, not 1.8.3 with rails 1.0. Can I just pull out the old rails directory in instiki and drop in rails 1.0 there, or do I have to do something more? Thanks, Bill Budell
On Wed, 2006-02-15 at 20:34 -0600, William Budell wrote:> So you''re essentially saying I should install a different Ruby and a > different Rails?The Ubuntu version of Rails installed is irrelevant, as Instiki is packaged with Rails included and will use that version instead. In fact, I have just proven that point to my satisfaction. I shut Instiki down, purged the Ubuntu rails package, and started Instiki again. It continues to work as it did before. I was not suggesting any particular course of action, but was merely thinking out loud about something I didn''t quite understand about the problem. Given that my Ubuntu Breezy Ruby reports itself as being 1.8.3, I thought Instiki shouldn''t work, based on my experience with 1.8.3 on Debian, and on the bug reports I cited. But clearly it does work for me, so that was a bit of a mystery. However, looking at it more closely today I have discovered that the Ubuntu ruby1.8 (Debian version 1.8.2-9ubuntu1) isn''t the final release of 1.8.3, but is based on 1.8.3-preview1 plus some patches. So that could account for Instiki working even though it claims to be ruby 1.8.3 which has been reported to not work with the old Rails included in Instiki.> I have Ruby 1.8.3 on my Ubuntu Breezy, and the rails > _I_ see in my Instiki is 0.13.1; my ruby is still throwing up the same > errors I included in my previous message even after installing as many > of the Ubuntu/Debian ruby packages as I could, as suggested by Assaph.Since my Instiki works and yours doesn''t, and we''re both running Breezy, that begs the question "what''s different?" Which version of the ruby1.8 package do you have? Are you using entirely Breezy-supplied ruby components, or do you have some things (other than Instiki itself) supplied from upstream or other deb repositories?> I see the warning on the rails page to use 1.8.4, or .2, not 1.8.3 with > rails 1.0. Can I just pull out the old rails directory in instiki and > drop in rails 1.0 there, or do I have to do something more?No. Don''t use Rails 1.0. As I said before, Instiki has its own rails included, so you don''t need to install it. You just need to have a compatible ruby. Ben -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/instiki-users/attachments/20060216/16128d8d/attachment-0001.htm
> I was not suggesting any particular course of action, but was merely > thinking out loud about something I didn''t quite understand about the > problem. Given that my Ubuntu Breezy Ruby reports itself as being 1.8.3, I > thought Instiki shouldn''t work, based on my experience with 1.8.3 on Debian, > and on the bug reports I cited. But clearly it does work for me, so that > was a bit of a mystery. However, looking at it more closely today I have > discovered that the Ubuntu ruby1.8 (Debian version 1.8.2-9ubuntu1) isn''t the > final release of 1.8.3, but is based on 1.8.3-preview1 plus some patches. > So that could account for Instiki working even though it claims to be ruby > 1.8.3 which has been reported to not work with the old Rails included in > Instiki. >I was already going to give up on this, considering I''m not that well versed in this stuff, but now my curiosity got piqued again. Can you, guys, please give me some hints how to downgrade Ruby 1.8.3 which I''ve installed from the source (not from the repositories) to some earlier version, so that I could see if that works? Johanka
On Thu, 2006-02-16 at 09:53 -0500, Johanka wrote:> I was already going to give up on this, considering I''m not that well > versed in this stuff, but now my curiosity got piqued again. Can you, > guys, please give me some hints how to downgrade Ruby 1.8.3 which I''ve > installed from the source (not from the repositories) to some earlier > version, so that I could see if that works?If you want to make sure there are no leftovers from 1.8.3 after the downgrade, first remove anything ruby installed in your target bin and lib directories. (I don''t think there is a "make uninstall" so you''ll have to investigate on your own.) Then build and install 1.8.2 from source. Ben