[MacPorts] #45882: Configure fails for textmate2. Missing from http://packages.macports.org

[MacPorts]

#45882: Configure fails for textmate2. Missing from http://packages.macports.org
-------------------------+--------------------
  Reporter:  pjkim00@…   |      Owner:  cal@…
      Type:  defect      |     Status:  closed
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:  2.3.2
Resolution:  worksforme  |   Keywords:
      Port:  textmate2   |
-------------------------+--------------------
Changes (by and.damore@…):

 * status:  new => closed
 * resolution:   => worksforme


Comment:

 Replying to [comment:3 pjkim00@…]:

 > I am still trying to learn how to parse and understand the log files. In
 my naive way of thinking, I search for "error" to find where the problems
 are. It seems that both "error" and "failed" are used when precompiled
 binaries can't be found.

 That's fine but you should search backward starting from the end, in this
 case the macport log shows that ''configure'' script failed in
 ''configure'' phase
 {{{
 :error:configure org.macports.configure for port textmate2 returned:
 configure failure: command execution failed
 }}}

 In any case you have to do a bit of critical reading about the error, from
 the HTTP fetcher's point of view a 404 is an error and it's correctly
 reporting that. You then see the processing of the ports went on with the
 fetching of source distfiles, as opposed as a prebuilt binary.

 Somehow your capnproto active port got broken, the configure script calls
 {{{
 test -x "${capnp_prefix}/bin/capnp"
 }}}
 with ''capnp_prefix'' set to /opt/local as you can see in the log, the
 file should have been there and it simply wasn't. Go figure.

 Ticket closed.

-- 
Ticket URL: <https://trac.macports.org/ticket/45882#comment:4>
MacPorts <https://www.macports.org/>
Ports system for OS X