freebsd stable - Jan 2006 - portupgrade ruby-1.8.4

Hi Folks,

I did a portsnap on 01.20.06 around 7am and ruby was available for upgrade, so I
ran portupgrade -arR and the ruby-1.8.4 upgrade failed.


The error message is:

rbconfig.db updated
./mkconfig.rb:156: undefined method `touch' for FileUtils:Module
(NoMethodError)
*** Error code 1


Should I just wait until the package is updated again or is there something else
on my end going on?


The server is:
    - FreeBSD 6.0 -> latest sources installed, except for the wireless update


Thanks,
~jeff

On Sat, 21 Jan 2006 08:37:56 -0600
"Mark J. Carpio" <jcarpio@velezcarpio.com> wrote:
> I did a portsnap on 01.20.06 around 7am and ruby was available for
> upgrade, so I ran portupgrade -arR and the ruby-1.8.4 upgrade failed.
> 
> 
> The error message is:
> 
> rbconfig.db updated
> ./mkconfig.rb:156: undefined method `touch' for FileUtils:Module
> (NoMethodError) *** Error code 1
I see the same error on a machine which runs:
root@kg-fil# uname -a
FreeBSD kg-fil.kg4.no 6.0-STABLE FreeBSD 6.0-STABLE #2: Sat Jan  7
23:08:43 CET 2006     root@kg-fil.kg4.no:/usr/obj/usr/src/sys/FIL60 
amd64

and on another:
root@kg-quiet# uname -a
FreeBSD kg-quiet.kg4.no 6.0-STABLE FreeBSD 6.0-STABLE #3: Sun Jan  8
20:22:06 CET 2006     root@kg-quiet.kg4.no:/usr/obj/usr/src/sys/QUIET 
amd64

But on my i386 machine, it installed without problems. This machine
runs:
root@kg-work# uname -a
FreeBSD kg-work.kg4.no 5.4-STABLE FreeBSD 5.4-STABLE #5: Sat Dec 31
16:54:14 CET 2005     root@kg-work.kg4.no:/usr/obj/usr/src/sys/SS51G 
i386
> Should I just wait until the package is updated again or is there
> something else on my end going on?  
Well, you should probably send-pr(1) it, if nobody has done so already.
-- 
Regards,
Torfinn Ingolfsen,
winter city Oslo,
Norway

On Sun, 22 Jan 2006 03:19:46 +0900
Hajimu UMEMOTO <ume@freebsd.org> wrote:
>> I've just committed the workaround by backing out the logic partly.
>> Since I don't have AMD64 box, I cannot test it by myself.  But, one
of
>> my friend tested it on his AMD64 box.  So, please re-CVSup and try it.
Yes, it works now. portupgrade just now without any problems.
Thanks!
-- 
Torfinn Ingolfsen

-----------------------------------------------------------------

Hajimu thank you ... I just did a portsnap, portupgrade and ruby upgraded
without a hitch.

~jeff