On 2010-5-26 10:34 , Scott Webster wrote:
> Hi folks. This question is likely quite similar to many that have
> come before, but my searches haven't helped me. A couple of times
> recently I've gotten the following message when upgrading some ports:
>
> Warning: Skippi
Hi folks. This question is likely quite similar to many that have
come before, but my searches haven't helped me. A couple of times
recently I've gotten the following message when upgrading some ports:
Warning: Skipping upgrade since automake 1.11.1_0 >= automake
1.11.1_0, even tho
"port outdated" nothing needs doing.
> (...)
>> Warning: Skipping upgrade since libtool 2.2.6b_1 >= libtool 2.2.6b_1, even
>> though installed variants "" do not match "+darwin". Use 'upgrade
>> --enforce-variants' to switch to the req
On Mar 21, 2010, at 19:14 , Mark Hattam wrote:
I don't understand which port was skipped in the upgrading ... all
four items that were outdated now appear to be "active". If I run a
subsequent "port outdated" nothing needs doing.
(...)
Warning: Skipping upgra
h into destroot
---> Deactivating bash @4.0.37_0
---> Computing dependencies for bash
---> Installing bash @4.1.2_0
---> Activating bash @4.1.2_0
---> Cleaning bash
Warning: Skipping upgrade since libtool 2.2.6b_1 >= libtool 2.2.6b_1, even
though installed variants "&qu
