On Jul 22, 2012, at 13:45, M. Daniel Becque wrote: > 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
I see that #35175 is filed for a universal build failure (I'm looking into this now), and #35148 is filed for a build failure on Leopard and older (that's an upstream issue the developers need to fix). > 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 upgrade" always preserves your existing variants (if they still exist in the port). _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo/macports-dev
