On May 20, 2013, at 20:57, Kevin Layer wrote: > Ryan Schmidt wrote: > >> On May 20, 2013, at 18:13, Kevin Layer wrote: >> >>> :error:install org.macports.install for port python27 returned: no destroot >>> found at: >>> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_python27/python27/work/destroot >> >> This sounds like #29223, except that it was fixed in MacPorts 2.1.3. >> >> https://trac.macports.org/ticket/29223 >> >> Perhaps you had last tried to install python27 with MacPorts 2.1.2 or >> earlier. Please run "sudo port clean python27" and try again.
> I tried that already, but tried it again to make sure. Results below. > ---> Computing dependencies for python27 > ---> Fetching archive for python27 > ---> Attempting to fetch > python27-2.7.3_1+universal.darwin_10.i386-x86_64.tbz2 from > http://packages.macports.org/python27 > ---> Attempting to fetch > python27-2.7.3_1+universal.darwin_10.i386-x86_64.tbz2.rmd160 from > http://packages.macports.org/python27 Note that python27 was updated to 2.7.5 yesterday; you should "sudo port selfupdate" to receive this and other updates, then re-try upgrading python27. No universal packages for python27 @2.7.5 are available yet, so you'll be building it from source instead of using a pre-built package as you were with @2.7.3_1. > ---> Installing python27 @2.7.3_1+universal > Error: org.macports.install for port python27 returned: @name > python27-2.7.3_1+universal > @portname python27 > @portepoch 2 > @portversion 2.7.3 > @portrevision 1 > @archs i386 x86_64 > @portvariant +universal [snip] This looks like the contents of the "+CONTENTS" file in the binary package. I don't know why MacPorts would decide to display that to you. But I also haven't used our precompiled binaries so I'm not familiar with exactly how they work or what the behavior is when things go wrong. _______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
