On Fri, Oct 17, 2008 at 11:53 AM, C. Florian Ebeling <[EMAIL PROTECTED]> wrote: > 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: >>> 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.
This is the effect I mean: # port installed tree The following ports are currently installed: tree @1.5.1.1_0 (active) # port deactivate tree ---> Deactivating tree # port install tree ---> Installing tree @1.5.1.1_0 Error: Target org.macports.install returned: Registry error: tree @1.5.1.1_0 already registered as installed. Please uninstall it first. Error: Status 1 encountered during processing. Florian -- Florian Ebeling Twitter: febeling [EMAIL PROTECTED] _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
