[MacPorts] #37949: rev-upgrade report does not explain missing slices
#37949: rev-upgrade report does not explain missing slices -------------------------+----------------------------- Reporter: jeremyhu@… | Owner: jmr@… Type: defect | Status: new Priority: Normal | Milestone: MacPorts Future Component: ports | Version: 2.1.99 Keywords: rev-upgrade | Port: -------------------------+----------------------------- rev-upgrade found that w3m was broken, but it didn't explain why: {{{ $ sudo port -v rev-upgrade ---> Updating database of binaries: 100.0% ---> Scanning binaries for linking errors: 9.7% Warning: Error parsing file /opt/local/lib/apple-gcc40/lib/gcc/i686-apple- darwin10.8.0/4.0.1/kext/crt3.o: Premature end of data, possibly corrupt file ---> Scanning binaries for linking errors: 9.8% Warning: Error parsing file /opt/local/lib/apple-gcc40/lib/gcc/i686-apple- darwin10.8.0/4.0.1/static/crt3.o: Premature end of data, possibly corrupt file ---> Scanning binaries for linking errors: 100.0% ---> Found 3 broken file(s), matching files to ports ---> Found 1 broken port(s): w3m @0.5.3 +universal /opt/local/bin/w3m /opt/local/libexec/w3m/cgi-bin/w3mbookmark /opt/local/libexec/w3m/cgi-bin/w3mhelperpanel }}} The reason was that one of its dependencies is not correctly +universal: {{{ $ arch -i386 /opt/local/bin/w3m dyld: Library not loaded: /opt/local/lib/libgc.1.dylib Referenced from: /opt/local/bin/w3m Reason: no suitable image found. Did find: /opt/local/lib/libgc.1.dylib: mach-o, but wrong architecture Trace/BPT trap }}} -- Ticket URL: <https://trac.macports.org/ticket/37949> MacPorts <http://www.macports.org/> Ports system for Mac OS
#37949: rev-upgrade report does not explain missing slices -------------------------+----------------------------- Reporter: jeremyhu@… | Owner: jmr@… Type: defect | Status: new Priority: Normal | Milestone: MacPorts Future Component: ports | Version: 2.1.99 Resolution: | Keywords: rev-upgrade Port: | -------------------------+----------------------------- Comment (by cal@…): If you ran port rev-upgrade with the debug flag, you'd see the reasons. -- Ticket URL: <https://trac.macports.org/ticket/37949#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS
#37949: rev-upgrade report does not explain missing slices -------------------------+-------------------------------- Reporter: jeremyhu@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: MacPorts Future Component: base | Version: 2.1.99 Resolution: | Keywords: rev-upgrade Port: | -------------------------+-------------------------------- Changes (by jmr@…): * owner: jmr@… => macports-tickets@… * component: ports => base -- Ticket URL: <https://trac.macports.org/ticket/37949#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS
#37949: rev-upgrade report does not explain missing slices -------------------------+-------------------------------- Reporter: jeremyhu@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: MacPorts Future Component: base | Version: 2.1.99 Resolution: wontfix | Keywords: rev-upgrade Port: | -------------------------+-------------------------------- Changes (by cal@…): * status: new => closed * resolution: => wontfix Comment: This works as intended. Run rev-upgrade with `-v` to see the reasons. The "premature end of data" messages have meanwhile been fixed aswell. -- Ticket URL: <https://trac.macports.org/ticket/37949#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts