Opened 10 years ago

Closed 10 years ago

#45882 closed defect (worksforme)

Configure fails for textmate2. Missing from http://packages.macports.org

Reported by: hardwhack Owned by: neverpanic (Clemens Lang)
Priority: Normal Milestone:
Component: ports Version: 2.3.2
Keywords: Cc: anddam@…
Port: textmate2

Description

The logfile is attached but the relevant part (I think) is

:msg:archivefetch --->  Attempting to fetch textmate2-2.0-beta.6_0.darwin_14.x86_64.tbz2 from http://packages.macports.org/textmate2
:debug:archivefetch Fetching archive failed:: The requested URL returned error: 404 Not Found
:msg:archivefetch --->  Attempting to fetch textmate2-2.0-beta.6_0.darwin_14.x86_64.tbz2 from http://lil.fr.packages.macports.org/textmate2
:debug:archivefetch Fetching archive failed:: The requested URL returned error: 404 Not Found
:msg:archivefetch --->  Attempting to fetch textmate2-2.0-beta.6_0.darwin_14.x86_64.tbz2 from http://nue.de.packages.macports.org/macports/packages/textmate2
:debug:archivefetch Fetching archive failed:: The requested URL returned error: 404 Not Found

If I use a web browser to open the first two servers, http://packages.macports.org and http://lil.fr.packages.macports.org, there is no entry for textmate2. And opening http://packages.macports.org/textmate2 returns a not found error.

Attachments (1)

main.log (166.0 KB) - added by hardwhack 10 years ago.

Download all attachments as: .zip

Change History (5)

Changed 10 years ago by hardwhack

Attachment: main.log added

comment:1 Changed 10 years ago by neverpanic (Clemens Lang)

The errors you quoted just tell you that there is no prebuilt binary archive for textmate2, but that's to be expected:

"textmate2" is not distributable because its license "gpl" conflicts with license "OpenSSL" of dependency "openssl"

The real problem is

:info:configure *** cap’n’proto not installed in ‘/opt/local’. Set `capnp_prefix` if installed elsewhere.

What do port -v installed capnproto and port contents capnproto print?

comment:2 Changed 10 years ago by neverpanic (Clemens Lang)

Cc: anddam@… added
Owner: changed from macports-tickets@… to cal@…
Port: textmate2 added

Oh, and when filing bugs against ports, please set the port field and Cc the maintainer (port info --maintainer textmate2), if any.

comment:3 Changed 10 years ago by hardwhack

port -v installed capnproto
The following ports are currently installed:
  capnproto @0.4.1_0 (active) platform='darwin 14' archs='x86_64'

Looking at the attached log file, capnproto appears to be installed:

357	:debug:main capnproto 0.4.1_0 exists in the ports tree
358	:debug:main capnproto 0.4.1_0  is the latest installed
359	:debug:main capnproto 0.4.1_0  is active

I didn't check the results of port contents capnproto prior to the next step.

I tried uninstalling capnproto and installing, followed by cleaning and installing textmate2. Seems to have fixed the problem. Thank you. I will try to remember the CC field next time.

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. Can I suggest that these terms, "error" and "fail(ed/ure)" be used only when there is a real problem?

Once again, thank you.

Last edited 10 years ago by hardwhack (previous) (diff)

comment:4 in reply to:  3 Changed 10 years ago by anddam (Andrea D'Amore)

Resolution: worksforme
Status: newclosed

Replying to 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.

Note: See TracTickets for help on using tickets.