Upgrades that include netpbm

Barrie Stott zen146410 at zen.co.uk
Sat Jun 13 00:56:15 PDT 2015

On 12 Jun 2015, at 21:57, Ryan Schmidt wrote:

> On Jun 12, 2015, at 10:21 AM, Barrie Stott wrote:
>> Whenever I perform such an 'upgrade outdated', a message is displayed when trying to configure netpbm saying that I should force a deactivation of netpbm and then the upgrade stops. Normally I deactivate netpbm, upgrade netpbm and upgrade outdated.
>> Is there any reason why I cannot force deactivate netpbm before starting the 'upgrade aoutdated' in the first place?
> I'm the maintainer of netpbm. Yes, if "port outdated" shows that netpbm is outdated, running "sudo port -f deactivate netpbm" before running "sudo port upgrade outdated" is fine; it's what I do, if I remember to do so.

My worry now is that if run "sudo port -f deactivate netpbm" then that newly deactivated version of netpbm will no longer register as outdated so it will not be upgraded when I run "sudo port upgrade outdated". Will I not have to run "sudo port install netpbm" straight after my forced deactivation?

> For ports that have build conflicts with other ports (like netpbm which has a build conflict with itself), we leave deactivating the conflicting port to you, rather than doing it automatically, because it means that ports that use the conflicting port will be broken until you reactivate it. But if you're about to upgrade your ports anyway, you're probably ok with that, and the problem will be fixed by the time the upgrades are done.

Thank you for taking time to help me.


More information about the macports-users mailing list