On Mar 20, 2010, at 16:22, Rainer Müller wrote:
On 2010-03-20 20:57 , Kok-Yong Tan wrote:
I'm encountering the following error to subversion after doing a
"port
-vd upgrade subversion". Is this a bug or something I've
forgotten to
do before invoking "port -vd upgrade subversion"? Here is the last
chunk of the output (please let me know if you need more):
Unfortunately, that's a bug with cyrus-sasl2:
http://trac.macports.org/ticket/17328
Workaround:
sudo port deactivate cyrus-sasl2
sudo port clean cyrus-sasl2
sudo port upgrade cyrus-sasl2
Rainer
Many thanks for the reply. I did as you recommended and that got me
over that obstacle. Then it happened again. This time, after also
doing a deactivate, clean and install on subversion 1.6.5, I watched
the build long enough to see it complain about my version of ruby
being too outdated for subversion to use. When I scrolled back
(thank goodness for sufficiently big scroll buffers) over the
previous subversion build failure's output, I noticed that despite it
also making the same complaint about ruby being too outdated for
subversion 1.6.5 to use, the build had continued until it crapped out
about an hour later instead of acknowledging the critical dependency
on ruby versions and just stopping at that point so it would be
obvious what the issue was. I discovered that if I manually built
the latest version of ruby and then went back to do a deactivate,
clean and install, subversion 1.6.5 built and installed without
problems. FYI.
--
Reality Artisans, Inc. # Network Wrangling and Delousing
P.O. Box 565, Gracie Station # Apple Certified Consultant
New York, NY 10028-0019 # Apple Consultants Network member
<http://www.realityartisans.com> # Apple Developer Connection member
(212) 369-4876 (Voice) # My PGP public key can be found
at <https://keyserver.pgp.com>
_______________________________________________
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
