On Fri, Oct 17, 2008 at 11:53:37AM +0200, C. Florian Ebeling said: > On Fri, Oct 17, 2008 at 9:30 AM, Bryan Blackburn <[EMAIL PROTECTED]> wrote: > > On Fri, Oct 17, 2008 at 08:54:42AM +0200, C. Florian Ebeling said: > >> Hi Bryan, > >> > > [...] > >> - portOutput=`/opt/local/bin/port -dvf uninstall $uninstallPort 2>&1` > >> + portOutput=`/opt/local/bin/port -dvf deactivate $uninstallPort 2>&1` > >> if [[ $? != 0 ]]; then > >> echo $portOutput > >> break > >> > >> I think this breaks things a bit. Running my little build server script > >> I noticed many more failing builds. They complain ultimately about > >> the port in question already being installed, after otherwise building > >> fine. > >> > > > > Is it running a trunk build? It definitely had no issues with my trunk > > build, but I didn't try it against a 1.6 build. > > yes, running trunk, and I dropped the mp-shadow image. > Also when I rolled back that revision all the failing ports > succeed again. >
Definitely strange, I ran quite a few ports through it once I initially made that change locally. I'll give it a try again in the next couple of days and see if fails for me this time. > Did you run it with a larger set of ports as well, or even all? Definitely not all, that'd take forever on my MBP, I usually let it build 150-200 as a test, but I let it run without a port list and kill it after a while. Bryan > > Florian > > > > -- > Florian Ebeling > Twitter: febeling > [EMAIL PROTECTED] _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
