tar mangles (some?) non-ascii characters in paths when extracting images

[justin.holewinski@…]

While attempting to install py27-matplotlib, I discovered that the dependency py27-py2app does not activate.

Installation (after uninstall/clean from original failure):

$ sudo port install py27-py2app
--->  Computing dependencies for py27-py2app
--->  Fetching archive for py27-py2app
--->  Fetching py27-py2app
--->  Verifying checksum(s) for py27-py2app
--->  Extracting py27-py2app
--->  Configuring py27-py2app
--->  Building py27-py2app
--->  Staging py27-py2app into destroot
--->  Installing py27-py2app @0.6.3_0
--->  Activating py27-py2app @0.6.3_0
Error: Target org.macports.activate returned: Image error: Source file /tmp/mpextractNvluKOE2/opt/local/share/examples/py27-py2app/PyObjC/TinyTinyEdit/dist.€/TinyTinyEdit.app/Contents/Frameworks/Python.framework/Versions/3.2/Python does not appear to exist (cannot lstat it).  Unable to activate port py27-py2app.
Log for py27-py2app is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_python_py27-py2app/py27-py2app/main.log
Error: Status 1 encountered during processing.
To report a bug, see <http://guide.macports.org/#project.tickets>

Log attached.

I'm not sure why it's trying to find Python 3.2 libraries for the Python 2.7 version...

OS: OS X Lion 10.7 (retail) XCode: 4.1 (retail)

[justin.holewinski@…]

port build log

[justin.holewinski@…]

Cc Me!

[nerdling (Jeremy Lavergne)]

What's your default version of python?

[justin.holewinski@…]

Python 2.7 (from MacPorts, not OS X) is the current default. I also installed Python 3.2 to see if it would magically pick up the needed frameworks, but no luck.

[jmroot (Joshua Root)]

Please remember to fill in the Port field and cc the maintainer. You do not need to be in cc when you are the reporter.

[justin.holewinski@…]

I invested this further, and the problem appears to be an incompatibility between a directory name in the py2app sources, and the archiver MacPorts uses to activate ports. Specifically, the py2app package has a directory named

py2app-0.6.3/examples/PyObjC/TinyTinyEdit/dist.€

(Note the €). When inflating the package during activation, that symbol appears to be morphed into a sequence of character escapes (see original log), which confuses MacPorts.

As a work-around, I manually changed the "dist.€" directory to just "dist" in the py2app source archive and forced MacPorts to use the new archive instead of the one on PyPI. With this change, the installation is successful. I'm not sure how best to handle this in general, but a simple patch that just renames that directory would suffice in the short term.

Though, this could also just be an upstream issue. I'm not sure why you would intentionally put a € in a directory name like that.

[nerdling (Jeremy Lavergne)]

If we're not respecting encodings in file names it'll only become a bigger issue as time goes on.

[wicentowski@…]

Replying to justin.holewinski@…:

As a work-around, I manually changed the "dist.€" directory to just "dist" in the py2app source archive and forced MacPorts to use the new archive instead of the one on PyPI. With this change, the installation is successful. I'm not sure how best to handle this in general, but a simple patch that just renames that directory would suffice in the short term.

Can you give some tips on how you did this?

[jmroot (Joshua Root)]

Workaround added to py2app in r80927. This definitely sounds like a tar bug, so I'm not really sure what we can do about it.

[wicentowski@…]

Replying to jmr@…:

Workaround added to py2app in r80927. This definitely sounds like a tar bug, so I'm not really sure what we can do about it.

The new Portfile worked for me. Thanks.

[jmroot (Joshua Root)]

Actually, it looks like tar is now obeying the locale environment vars in Lion, and assuming "C" when they're not set.

[jmroot (Joshua Root)]

r80928, r80932

[justin.holewinski@…]

That makes me a bit more confused now.

The non-ASCII character is present in the original archive, and gets extracted correctly (I believe). Everything builds fine, but the re-archiving is what shows a change in the encoding. Both use tar, so why is it correct in one case and not in the other? Does MacPorts modify the locale at some point during installation?