Struggling mightily with port updates

[Paul Schmehl]

--On June 8, 2014 at 6:38:48 PM -0600 Warren Block <wblock at wonkity.com> 
wrote:

> On Sun, 8 Jun 2014, Paul Schmehl wrote:
>
>> I upgraded two systems to 8.4 and ran portmaster -ad to update all ports.
>>
>> Most of it worked fine, but I'm in docbook hell now. I also don't
>> understand  this:
>>
>> ===>>> All >> (6)
>>
>> ===>>> The following actions will be taken if you choose to proceed:
>> 	Upgrade en-freebsd-doc-43251,1 to en-freebsd-doc-44807,1
>> 	Re-install ruby-1.9.3.484_2,1
>> 	Install textproc/docbook-xml
>> 	Install www/mod_authnz_external22
>> 	Re-install docproj-2.0_2
>> 	Install print/ghostscript9
>>
>> ===>>> Proceed? y/n [y]
>>
>> I just upgraded ruby:
>>
>> ===>>> The following actions were performed:
>> 	Re-installation of ruby-1.9.3.484_2,1
>> 	Re-installation of ruby19-bdb-0.6.6_3
>> 	Re-installation of ruby19-date2-4.0.19
>>
>> So why does portmaster want to reinstall it?
>
> /usr/ports/UPDATING shows manual steps that must be taken.  The 20140219
> entry talks about the DocBook ports.
>

I read that, but the uninstalls failed.  I ended up having to run down the 
dependency rabbit hole, uninstalling ports one at a time until the one 
depending upon them were all gone.  It's working now.

Paul Schmehl, Senior Infosec Analyst
As if it wasn't already obvious, my opinions
are my own and not those of my employer.
*******************************************
"It is as useless to argue with those who have
renounced the use of reason as to administer
medication to the dead." Thomas Jefferson
"There are some ideas so wrong that only a very
intelligent person could believe in them." George Orwell