Home • About Us • A-Z Index • Search * Contact Us • Register • Login • Press • Shop

The Open Brand -- Problem Reporting and Interpretations System

Problem Report 2481 Details

Help Show help | Quick Search | Submit a Test Suite Support Request | Click here to view your privileges

This page provides all information on Problem Report 2481.

Report 2481 Actions

    Problem Report Number 2481
    Submitter's Classification Test Suite problem
    State Resolved
    Resolution Rejected (REJ)
    Problem Resolution ID REJ.X.0673
    Raised 2005-10-07 01:29
    Updated 2005-10-13 19:31
    Published 2005-10-13 19:31
    Product Standard Commands and Utilities V4 (UNIX 03)
    Certification Program The Open Brand certification program
    Test Suite VSC version 5.2.7
    Test Identification /tset/POSIX.cmd/pax/pax.ex 245 Failed
    /tset/POSIX.cmd/pax/pax.ex 247 Failed
    Specification Shell and Utilities Issue 6
    Problem Summary pax.ex 245 and 247 fail on use of -o path=pax_245_newfile.
    The test cases are written incorrectly. The name of the
    file to be extracted must be the original name, not the changed name.
    Problem Text The test creates a file
    echo 'a regular file' > pax_245_file

    creates a pax archive containing the file

    pax -w -x pax -f pax_245_arc.pax pax_245_file

    Then tries to extract the file, setting a different group, user, and
    filename.

    ExecWithPriv ALLPRIV pax -r -o
    "gname=$VSC_NON_MEMBER_GRP,uname=$VSC_OTHER_USER_NAME,path=pax_245_newfile"
    -f pax_245_arc.pax pax_245_newfile > $CT_STDOUT 2> $CT_STDERR

    The problem here is that the new filename is used as the filename to
    search the archive for, pax cannot find this file and exits
    unsucessfully with error.

    If the command is run like this

    ExecWithPriv ALLPRIV pax -r -o
    "gname=$VSC_NON_MEMBER_GRP,uname=$VSC_OTHER_USER_NAME,path=pax_245_newfile"
    -f pax_245_arc.pax pax_245_file > $CT_STDOUT 2> $CT_STDERR

    It will succeed, extracting the file and renaming it.

    pax will extract the file and rename it, but it needs to
    have the name as it is in the archive in order to match it for extraction.
    Test Output tset/POSIX.cmd/pax/pax.ex 245 Failed


    Test Information:
    Assertion #245 (A):
    Expected exit code = 0; Received 1
    Command failed: 'test -f pax_245_newfile'
    Command failed: 'pax_245_fgroup="`GetFileGroup pax_245_newfile`"'

    /tset/POSIX.cmd/pax/pax.ex 247 Failed
    Assertion #247 (A):
    Expected exit code = 0; Received 1
    Command failed: 'test -f pax_247_newfile'
    Command failed: 'pax_247_fgroup="`GetFileGroup pax_247_newfile`"'
    *** (#1 of 1): 2005-09-15 19:24:35 PDT eric.ahlberg@sun.com

    Review Information

    Review Type TSMA Review
    Start Date 2005-10-07 01:29
    Last Updated 2005-10-07 18:11
    Completed 2005-10-07 18:11
    Status Complete
    Review Recommendation Rejected (REJ)
    Review Response The tests are correct, and this pax implementation does not comply with
    the standard. The standard describes the pax read mode as follows:

    read
    In read mode (when -r is specified, but -w is not), pax shall
    extract the members of the archive file [...] with pathnames
    matching the specified patterns.

    The question is what is the "pathname" that is matched against the
    pattern pax_245_newfile.

    The description of the pax -o option includes:

    keyword=value
    [...] When used in read or list mode, these keyword/value
    pairs shall act as if they had been at the beginning of the
    archive as typeflag g global extended header records.

    So, because a -o option with path=pax_245_newfile is specified, pax
    should handle the input file as if it had a typeflag g header containing
    "path=pax_245_newfile" at the start.

    The "path" keyword is defined as follows:

    The pathname of the following file(s). This record shall override
    the name and prefix fields in the following header block(s).

    Since this keyword specifies the pathname of the following file(s),
    overriding the name and prefix fields in the normal header, it is that
    pathname (pax_245_newfile) that the pattern is matched against.

    A similar argument applies for test 247 and "path:=pax_247_newfile".

    Review Type SA Review
    Start Date 2005-10-07 17:11
    Last Updated 2005-10-08 01:43
    Completed 2005-10-08 01:43
    Status Complete
    Review Resolution Rejected (REJ)
    Review Conclusion The SA concurs with the TSMA that the test as written is consistent
    with the PAX usage defined in the standard and appears not to be in
    error. This PR is thus rejected as a TSD. The submitter may appeal
    this decision if it is believed that the SA and TSMA analysis of the
    test code is incorrect.

    Problem Reporting System Options:

     

    Back   

Contact the Certification Authority