Upgrading Gegl from 0.1.8_2 to 0.2.0_0 fails on my machine [ticket filed].
I am thinking that maybe the upgrade is trying to do a universal build but
when I look at the active version of Gegl on my machine I get *gegl
@0.1.8_2+python27 (active). *To test this theory can I make sure the upgrade
is to the python27 variant?

port -u upgrade [email protected]_0+python27 but from usage I think that upgrade
wants the present port named.

Thanks for you thoughts in advance.
Dan
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-dev

Reply via email to