Opened 9 years ago
Closed 9 years ago
#50362 closed defect (invalid)
llvm-3.7 upgrade error
Reported by: | dershow | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.4 |
Keywords: | Cc: | jeremyhu (Jeremy Huddleston Sequoia), larryv (Lawrence Velázquez) | |
Port: | llvm-3.7 |
Description
I just upgraded llvm-3.7 from 3.7.1_0 to 3.7.1_1. During the upgrade I got the following error:
---> Computing dependencies for llvm-3.7 ---> Fetching archive for llvm-3.7 ---> Attempting to fetch llvm-3.7-3.7.1_1.darwin_15.x86_64.tbz2 from http://packages.macports.org/llvm-3.7 ---> Attempting to fetch llvm-3.7-3.7.1_1.darwin_15.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/llvm-3.7 ---> Attempting to fetch llvm-3.7-3.7.1_1.darwin_15.x86_64.tbz2 from http://lil.fr.packages.macports.org/llvm-3.7 ---> Fetching distfiles for llvm-3.7 ---> Verifying checksums for llvm-3.7 ---> Extracting llvm-3.7 ---> Applying patches to llvm-3.7 ---> Configuring llvm-3.7 ---> Building llvm-3.7 2016-01-18 07:46:42.874 Python[19885:2850337] Communications error: <OS_xpc_error: <error: 0x7fff7be6fb90> { count = 1, contents = "XPCErrorDescription" => <string: 0x7fff7be6ff40> { length = 22, contents = "Connection interrupted" } }> ---> Staging llvm-3.7 into destroot ---> Installing llvm-3.7 @3.7.1_1 ---> Cleaning llvm-3.7 ---> Computing dependencies for llvm-3.7 ---> Deactivating llvm-3.7 @3.7.1_0 ---> Cleaning llvm-3.7 ---> Activating llvm-3.7 @3.7.1_1 ---> Cleaning llvm-3.7 ---> Uninstalling llvm-3.7 @3.7.1_0 ---> Cleaning llvm-3.7
And, as can be seen, then then seemed to install correctly. Is it safe to ignore this error? If not, what does it mean, and what should be done about it?
Change History (1)
comment:1 Changed 9 years ago by jeremyhu (Jeremy Huddleston Sequoia)
Resolution: | → invalid |
---|---|
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
That's not really an error. Whoever is logging that should not.