[MacPorts] #43281: jpilot @1.8.1: extract fails

MacPorts noreply at macports.org
Wed Apr 9 01:21:42 PDT 2014


#43281: jpilot @1.8.1: extract fails
---------------------------+-------------------------------
  Reporter:  ryandesign@…  |      Owner:  kristian.peters@…
      Type:  defect        |     Status:  new
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:  2.2.99
Resolution:                |   Keywords:
      Port:  jpilot        |
---------------------------+-------------------------------

Comment (by ryandesign@…):

 Replying to [comment:3 kristian.peters@…]:
 > Older versions of Mac OS X use UTF-8 for encoding filenames in the
 filesystem. Newer version (don't know the exact version when they changed
 it) use UTF-16. If you upgraded from a really old Mac OS X the filesystem
 could be still UTF-8.

 I haven't heard of that before. Do you have a citation for that? In any
 case, my filesystem was created in May 2012 when Apple shipped this Mac to
 me. I have also tested on a second machine with Mavericks whose drive was
 initialized in August 2012 and it experiences the same error. These two
 machines use the normal case-insensitive filesystems, while the
 buildslaves use case-sensitive filesystems, but so far this doesn't seem
 like a case-sensitivity issue to me.

 > You should check your locale settings. Setting LC_ALL="C" before running
 macports should do the trick. (export LC_ALL="C").

 Which locale settings are you referring to? Setting `LC_ALL=C` before
 running a MacPorts command doesn't change anything, because MacPorts
 deliberately clears the environment variables before it runs, to ensure
 consistency across systems regardless what environment variables the user
 may have set.

 > Maybe you should use bash as shell as well.

 I do use bash.

 > It could be a problem with your tar as well. I'm using the tar supplied
 with 10.9 in /usr/bin/tar. Otherwise, I'm stumped.

 I am also using OS X 10.9's tar.

 Extracting within MacPorts fails, but extracting at the command line
 succeeds:

 {{{
 $ tar xzf jpilot-1.8.1.tar.gz
 }}}

 However the extracted file has the wrong name:

 {{{
 $ ls jpilot-1.8.1/empty/Ma*ana*
 jpilot-1.8.1/empty/Ma%F1anaDB.pdb
 }}}

 Using `LC_ALL=C` doesn't change this.

 I would say that the tarball has been created improperly: the non-ASCII
 character "ñ" has been encoded as ISO8859-1, whereas UTF-8 encoding would
 be desired. This probably needs to be reported to the developers of jpilot
 so that they can package it correctly for the next version.

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


More information about the macports-tickets mailing list