ruby version going backwards...?
kris at obsecurity.org
Mon Nov 14 17:22:24 PST 2005
On Tue, Nov 15, 2005 at 04:19:35AM +0300, Sergey Matveychuk wrote:
> Kris Kennaway wrote:
> >On Mon, Nov 14, 2005 at 02:12:57PM -0500, Chuck Swiger wrote:
> >>Hi, all (and Mark in particular :-)--
> >>I just saw a message about the version for ruby and other ports
> >>maintained by knu being reset. I'm getting a rather odd update message
> >>from portupgrade now:
> >>---> Upgrade of lang/ruby18 started at: Mon, 14 Nov 2005 14:06:08 -0500
> >>---> Upgrading 'ruby-1.8.3' to 'ruby-1.8.2_5,1' (lang/ruby18)
> >>OK? [yes] n
> >>Did PORTEPOCH get removed?
> What is a problem here?
> >No, as you can see there was no PORTEPOCH that was removed :)
> >The ruby upgrade was reverted, but this has just caused further
> >problems :/
> If user update both bsd.ruby.mk and lang/ruby18 there is no problem there.
> Or I something miss?
According to the version check script a number of port versions still
went backwards (you should be getting notification of this by email).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20051114/5ccfd822/attachment.bin
More information about the freebsd-ports