Date: Sat, 20 Aug 2016 08:31:52 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-amd64@FreeBSD.org Subject: [Bug 212010] DEFAULT_VERSIONS broken for ruby Message-ID: <bug-212010-6@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212010 Bug ID: 212010 Summary: DEFAULT_VERSIONS broken for ruby Product: Ports & Packages Version: Latest Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Ports Framework Assignee: portmgr@FreeBSD.org Reporter: chrysalis@chrysalisnet.org CC: freebsd-amd64@FreeBSD.org, freebsd-ports-bugs@FreeBSD.org CC: freebsd-amd64@FreeBSD.org I have upgraded a machine to 10.3 from an older version, I manually recompi= led portupgrade, and its two dependencies first which was ruby21 and ruby-bdb. In my make .conf is the following line which sets the default ruby to 2.1. = Or at least I think it does (apologies if it is incorrect but I believe it to = be correct). DEFAULT_VERSIONS=3D perl5=3D5.22 mysql=3D56p bdb=3D5 python=3D2.7 python2= =3D2.7 python3=3D3.4 tcltk=3D8.6 ruby=3D2.2 ghostscript=3D9 Also in /usr/ports/Mk/bsd.default-versions.mk exists these lines showing if undefined in the make.conf the default version falls back to 2.2. # Possible values: 2.0, 2.1, 2.2, 2.3 RUBY_DEFAULT?=3D 2.2 After about 4-5 hours I checked how things were going and portupgrade had crashed, it was due to the ruby21 binary been missing. I checked pkg info = and ruby21 had been replaced with ruby22 so make.conf setting was ignored. This is a production machine so I need to minimise time on this so have res= umed with ruby22 been the new default but I do have a spare machine which I can carry out further testing if requested. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-212010-6>