[MacPorts] #24227: libzzip destroot fails on Leopard: no files matched glob pattern "*.3" (was: libzzip destroot: no files matched glob pattern "*.3")

MacPorts noreply at macports.org
Sun Mar 28 23:52:09 PDT 2010


#24227: libzzip destroot fails on Leopard: no files matched glob pattern "*.3"
-------------------------------------+--------------------------------------
 Reporter:  and.damore@…             |       Owner:  ryandesign@…           
     Type:  defect                   |      Status:  assigned               
 Priority:  Normal                   |   Milestone:                         
Component:  ports                    |     Version:  1.8.2                  
 Keywords:  leopard                  |        Port:  libzzip                
-------------------------------------+--------------------------------------
Changes (by ryandesign@…):

 * cc: ryandesign@… (removed)
  * status:  new => assigned
  * owner:  macports-tickets@… => ryandesign@…
  * keywords:  libzzip ppc => leopard


Comment:

 After some more testing, I see that this fails only on Leopard; it works
 fine on Tiger and Snow Leopard.

 libzzip determines whether or not to use the "`-O`" flag to "`pax`" by
 grepping the output of "`pax --help`" for the regexp
 "`pax.*-[[a-zA-Z]]*O`".

 On Tiger the output is as follows:
 {{{
 $ pax --help
 pax: illegal option -- -
 usage: pax [-cdnv] [-E limit] [-f archive] [-s replstr] ... [-U user] ...
            [-G group] ... [-T [from_date][,to_date]] ... [pattern ...]
        pax -r [-cdiknuvDYZ] [-E limit] [-f archive] [-o options] ...
            [-p string] ... [-s replstr] ... [-U user] ... [-G group] ...
               [-T [from_date][,to_date]] ...  [pattern ...]
        pax -w [-dituvHLPX] [-b blocksize] [ [-a] [-f archive] ] [-x
 format]
            [-B bytes] [-s replstr] ... [-o options] ... [-U user] ...
            [-G group] ... [-T [from_date][,to_date][/[c][m]]] ... [file
 ...]
        pax -r -w [-diklntuvDHLPXYZ] [-p string] ... [-s replstr] ...
            [-U user] ... [-G group] ... [-T
 [from_date][,to_date][/[c][m]]] ...
            [file ...] directory
 }}}
 libzzip correctly sees that the "`-O`" option is not listed and does not
 try to use it. This works fine.

 On Leopard the output is as follows:
 {{{
 $ pax --help
 pax: illegal option -- -
 usage: pax [-cdnvzO] [-E limit] [-f archive] [-s replstr] ... [-U user]
 ...
            [-G group] ... [-T [from_date][,to_date]] ... [pattern ...]
        pax -r [-cdiknuvzDOYZ] [-E limit] [-f archive] [-o options] ...
            [-p string] ... [-s replstr] ... [-U user] ... [-G group] ...
               [-T [from_date][,to_date]] ...  [pattern ...]
        pax -w [-dituvzHLOPX] [-b blocksize] [ [-a] [-f archive] ] [-x
 format]
            [-B bytes] [-s replstr] ... [-o options] ... [-U user] ...
            [-G group] ... [-T [from_date][,to_date][/[c][m]]] ... [file
 ...]
        pax -r -w [-diklntuvDHLOPXYZ] [-p string] ... [-s replstr] ...
            [-U user] ... [-G group] ... [-T
 [from_date][,to_date][/[c][m]]] ...
            [file ...] directory
 }}}
 libzzip correctly sees that the "`-O`" option is listed and tries to use
 it, but although it has advertised that it supports the "`-O`" option,
 "`pax`" on Leopard evidently does not actually support it. Therefore this
 fails. There is some confusion here, in that the usage message printed by
 "`pax --help`" differs from the usage message shown in "`man pax`" -- the
 latter does not show the "`-O`" option, but then again the manpage does
 describe the "`-O`" option in detail:

 {{{
      -O      Force the archive to be one volume.  If a volume ends
 prematurely, pax will
              not prompt for a new volume.  This option can be useful for
 automated tasks
              where error recovery cannot be performed by a human.
 }}}

 On Snow Leopard the output is as follows:
 {{{
 $ pax --help
 pax: unrecognized option `--help'
 usage: pax [-0cdjnOvz] [-E limit] [-f archive] [-G group] [-s replstr]
            [-T range] [-U user] [--insecure] [pattern ...]
        pax -r [-0cDdijknOuvYZz] [-E limit] [-f archive] [-G group] [-o
 options]
            [-p string] [-s replstr] [-T range] [-U user] [--insecure]
 [pattern ...]
        pax -w [-0adHijLOPtuvXz] [-B bytes] [-b blocksize] [-f archive]
            [-G group] [-o options] [-s replstr] [-T range] [-U user]
            [-x format] [--insecure] [file ...]
        pax -rw [-0DdHikLlnOPtuvXYZ] [-G group] [-p string] [-s replstr]
            [-T range] [-U user] [--insecure] [file ...] directory
 }}}
 libzzip incorrectly decides that the "`-O`" option is not listed (because
 the list of flags begins with a number, zero) and therefore does not try
 to use it. This works fine. (It would also work fine if libzzip would use
 the "`-O`" option because the "`-O`" option does work with Snow Leopard's
 "`pax`".)

 I believe the strategy should be to introduce a patch which removes the
 checks for the "`-O`" flag from the libzzip configure script, on Leopard
 only.

-- 
Ticket URL: <http://trac.macports.org/ticket/24227#comment:5>
MacPorts <http://www.macports.org/>
Ports system for Mac OS


More information about the macports-tickets mailing list