On Sun, 22 Jan 2006 03:19:46 +0900
Hajimu UMEMOTO <[EMAIL PROTECTED]> 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,
Hi,
> On Sat, 21 Jan 2006 18:05:37 +0100
> Torfinn Ingolfsen <[EMAIL PROTECTED]> said:
torfinn> On Sat, 21 Jan 2006 08:37:56 -0600
torfinn> "Mark J. Carpio" <[EMAIL PROTECTED]> wrote:
> I did a portsnap on 01.20.06 around 7am and ruby was available for
> upgrade, so I ran portupgrade -ar
Hi,
> On Sat, 21 Jan 2006 18:05:37 +0100
> Torfinn Ingolfsen <[EMAIL PROTECTED]> said:
torfinn> On Sat, 21 Jan 2006 08:37:56 -0600
torfinn> "Mark J. Carpio" <[EMAIL PROTECTED]> wrote:
> I did a portsnap on 01.20.06 around 7am and ruby was available for
> upgrade, so I ran portupgrade -ar
On Sat, 21 Jan 2006 08:37:56 -0600
"Mark J. Carpio" <[EMAIL PROTECTED]> 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: un
