Ben, Thanks for the answer. I can't upgrade because these servers are used for webhosting and the hosting control panel not support etch yet.
Regards, Sander On Wed, 2007-07-11 at 15:13, Ben Armstrong wrote: > Sander, > > On Wed, 11 Jul 2007 14:27:23 +0200 > Sander Hamel - ICI-Multimedia <[EMAIL PROTECTED]> wrote: > > Not sure if this is the correct place to post this problem. > > The normal procedure is to use reportbug to file a bug against the relevant > package which, in this case, is libruby1.8. But in your case, that is not > appropriate ... > > > > But it seems > > that after installing ruby by: > > > > apt-get install irb1.8 libreadline-ruby1.8 libruby libruby1.8 rdoc1.8 \ > > > ruby ruby1.8 ruby1.8-dev > > > > the FileUtils package is not complete. I tried it on 2 debian(3.1) > > machines and both have the same problem. > > That release (Sarge) is now obsolete. It has been superceded by > Debian 4.0 (Etch). See: > > http://www.debian.org/releases/ > > I suspect ruby just didn't include these methods in FileUtils back then. > > > The following statements are > > not accepted while they normally are part of the fileutils. > > > > chmod_R > > chown > > chown_R > > > > Is there anyway to fix this problem? Or should I post it somewhere else? > > > > Small sample of chmod_R not working: > > > > mars:~/installers/webici# irb > > irb(main):001:0> require 'fileutils' > > => true > > irb(main):002:0> include FileUtils > > => Object > > irb(main):003:0> chmod_R 0700, "/home/sander" > > NoMethodError: undefined method `chmod_R' for main:Object > > from (irb):3 > > Not reproducible in Sid. And I'm confident you won't be able to reproduce > the problem on Etch either, though I have not tested this. Please update > your system to the latest supported stable release, Debian 4.0 (Etch). > > Ben > -- > ,-. nSLUG http://www.nslug.ns.ca [EMAIL PROTECTED] > \`' Debian http://www.debian.org [EMAIL PROTECTED] > ` [ gpg 395C F3A4 35D3 D247 1387 2D9E 5A94 F3CA 0B27 13C8 ] > [ pgp 7F DA 09 4B BA 2C 0D E0 1B B1 31 ED C6 A9 39 4F ] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
