qjson @0.7.1_1 build failure

[anonymous@…]

Can't install qjson (on 10.6.8), needed by amarok.

--->  Computing dependencies for qjson
--->  Fetching archive for qjson
--->  Attempting to fetch qjson-0.7.1_1.darwin_10.x86_64.tbz2 from http://packages.macports.org/qjson
--->  Fetching qjson
--->  Verifying checksum(s) for qjson
Error: Target org.macports.checksum returned:  does not exist in /opt/local/var/macports/distfiles/qjson
Log for qjson is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_qjson/qjson/main.log
Error: Status 1 encountered during processing.
To report a bug, see <http://guide.macports.org/#project.tickets>

[anonymous@…]

qjson error log (/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_qjson/qjson/main.log)

[rmstonecipher@…]

Jeremy,
Must qjson fetch from git when tarballs are available from SourceForge mirrors?
Attached is a patch to switch the fetch to sourceforge.

Cheers,
Ryan Stonecipher

[nerdling (Jeremy Lavergne)]

Was simply where I had found it when I created the port; my initial clicking to get the project home page continued to keep me at gitorious instead of sf. Feel free to submit this patch if you have time before I do.

[nerdling (Jeremy Lavergne)]

I think the real issue here might be in how base is handling a package that was not fully failed on the archive mirror (that is, fetch failed but not building or license).

[raimue (Rainer Müller)]

The issue has been fixed on trunk in r83471, but was not yet released.

[raimue (Rainer Müller)]

I committed a workaround for this problem to qjson in r83492.

[rmstonecipher@…]

Switched to SourceForge, workaround removed in r83506.

[pixilla (Bradley Giesbrecht)]

My port command is built from trunk r83544.
qjson extracts to ${name} rather then ${distname}.

DEBUG: Executing proc-post-org.macports.extract-extract-1
Error: Target org.macports.extract returned: /opt/local/var/macports/build/_opt_local_var_macports_sources_svn.macports.org_trunk_dports_devel_qjson/qjson/work/qjson-0.7.1: no such file or directory

Oddly, setting "worksrcdir ${name}" still produces this error.
Adding the following is working for me:

extract.mkdir       yes
extract.post_args   "| tar -xf - --strip-components 1 -C ${worksrcpath}"

[pixilla (Bradley Giesbrecht)]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

Replying to pixilla@…:

qjson extracts to ${name} rather then ${distname}.

[snip]

Oddly, setting "worksrcdir ${name}" still produces this error.

The kde4 portgroup was buggy. Fixed in r83562.

extract.post_args   "| tar -xf - --strip-components 1 -C ${worksrcpath}"

Let's not do that kind of thing if possible. It introduces too much knowledge into the portfile about the internals of how the extract phase currently works, and makes it harder for us to change / improve the extract phase later.