PR0064.html

LSB Problem Report

Problem Report Number 0064 (REJ.0007)
Submitter's Classification Specification Problem (INT)
State Resolved
Resolution Rejected (REJ)
Raised 2004-10-20 16:51
Updated 2004-11-03 17:29
Published 2004-11-03 17:29
Certification Program Linux Standard Base Conformance Release 1.3
Test Suite lsb-runtime PPC32 version 1.3
Test Identification /tset/LI18NUX2K.L1/utils/* (many, see problem text)
Specification Linux Standard Base Specification for PPC32 Architecture 1.3
Location in Spec None.
Linked Problem Reports PR, 0037
Problem Summary The following tests should be treated the same as those in PR 0037 for
the same reasons.
Problem Text See PR 0037.The following larger set of tests from this test
section should waived for the same reason as PR 0037:

/tset/LI18NUX2K.L1/utils/comm/comm,1,FAIL
/tset/LI18NUX2K.L1/utils/comm/comm,2,FAIL
/tset/LI18NUX2K.L1/utils/egrep-tp/egrep-tp,5,FAIL
/tset/LI18NUX2K.L1/utils/fgrep/fgrep,5,FAIL
/tset/LI18NUX2K.L1/utils/grep-tp/grep-tp,5,FAIL
/tset/LI18NUX2K.L1/utils/join/join,3,FAIL
/tset/LI18NUX2K.L1/utils/sed-tp/sed-tp,6,FAIL
/tset/LI18NUX2K.L1/utils/sort/sort,1,FAIL
/tset/LI18NUX2K.L1/utils/sort/sort,3,FAIL
/tset/LI18NUX2K.L1/utils/sort/sort,8,FAIL
/tset/LI18NUX2K.L1/utils/sort/sort,9,FAIL
/tset/LI18NUX2K.L1/utils/sort/sort,16,FAIL
/tset/LI18NUX2K.L1/utils/sort/sort,17,FAIL
/tset/LI18NUX2K.L1/utils/sort/sort,19,FAIL
/tset/LI18NUX2K.L1/utils/sort/sort,24,FAIL
/tset/LI18NUX2K.L1/utils/sort/sort,25,FAIL
/tset/LI18NUX2K.L1/utils/sort/sort,32,FAIL
/tset/LI18NUX2K.L1/utils/sort/sort,33,FAIL
/tset/LI18NUX2K.L1/utils/sort/sort,35,FAIL
/tset/LI18NUX2K.L1/utils/sort/sort,40,FAIL
/tset/LI18NUX2K.L1/utils/sort/sort,41,FAIL
/tset/LI18NUX2K.L1/utils/sort/sort,48,FAIL
/tset/LI18NUX2K.L1/utils/wc/wc,1,FAIL
/tset/LI18NUX2K.L1/utils/wc/wc,2,FAIL
/tset/LI18NUX2K.L1/utils/cpio-fh/cpio-fh,2,FAIL
/tset/LI18NUX2K.L1/utils/cpio-fh/cpio-fh,3,FAIL
/tset/LI18NUX2K.L1/utils/cpio-fh/cpio-fh,4,FAIL
/tset/LI18NUX2K.L1/utils/cpio-fh/cpio-fh,5,FAIL
/tset/LI18NUX2K.L1/utils/cpio-fh/cpio-fh,6,FAIL
/tset/LI18NUX2K.L1/utils/cpio-fh/cpio-fh,7,FAIL
/tset/LI18NUX2K.L1/utils/cpio-fh/cpio-fh,8,FAIL
/tset/LI18NUX2K.L1/utils/cpio-fh/cpio-fh,9,FAIL
/tset/LI18NUX2K.L1/utils/cpio-fh/cpio-fh,10,FAIL
/tset/LI18NUX2K.L1/utils/cpio-fh/cpio-fh,11,FAIL
/tset/LI18NUX2K.L1/utils/cpio-fh/cpio-fh,12,FAIL
/tset/LI18NUX2K.L1/utils/cpio-fh/cpio-fh,13,FAIL
/tset/LI18NUX2K.L1/utils/tar-fh/tar-fh,1,FAIL
/tset/LI18NUX2K.L1/utils/tar-fh/tar-fh,2,FAIL
/tset/LI18NUX2K.L1/utils/tar-fh/tar-fh,3,FAIL
/tset/LI18NUX2K.L1/utils/tar-fh/tar-fh,4,FAIL
/tset/LI18NUX2K.L1/utils/tar-fh/tar-fh,5,FAIL
/tset/LI18NUX2K.L1/utils/tar-fh/tar-fh,6,FAIL
Test Output TEST CASE: comm/comm

TEST PURPOSE #1
* Verify this utility extracts the lines duplicated in file1 and file2
even if these files include multibyte character.

Can't handle multibyte characters.
1 FAIL

TEST PURPOSE #2
* Verify this utility extracts the lines duplicated in file1 and file2
when these files are ordered according to the collating sequence of the
current locale.

Not ordered by the collating sequence.
2 FAIL

TEST CASE: egrep-tp/egrep-tp

TEST PURPOSE #5
* Verify this utility can perform pattern matching in searches without
regard to case if -i option is specified.

Can't handle a pattern "AbcD" with -i.
5 FAIL

TEST CASE: fgrep/fgrep

TEST PURPOSE #5
* Verify this utility can perform pattern matching in searches without
regard to case if -i option is specified.

Can't handle a pattern "AbcD" with -i.
5 FAIL

TEST CASE: grep-tp/grep-tp

TEST PURPOSE #5
* Verify this utility can perform pattern matching in searches without
regard to case if -i option is specified.

Can't handle a pattern "AbcD" with -i.
5 FAIL

TEST CASE: join/join

TEST PURPOSE #3
* When -t option is specified, verify this utility uses given character
as a separator even if the character is multibyte character.

This utility does not join the files.
3 FAIL

TEST CASE: sed-tp/sed-tp

TEST PURPOSE #6
* Verify that 'y' command handle strings per 1 character.

Can't replace correctly.
6 FAIL

TEST CASE: sort/sort

TEST PURPOSE #1
* Verify this utility sorts lines according to the collating sequence of
the current locale.

Can't sort input lines according to the collating sequence.
1 FAIL

TEST PURPOSE #3
* When -d option is specified, verify this utility interprets which
character is a blank character or an alphanumeric character.

Can't interpret blank and alphanumeric character according to the
current locale.
3 FAIL

TEST PURPOSE #8
* When -t option is specified, verify this utility use a character as a
field separator even if the character is a multibyte character.

Can't handle field separator written in a multibyte chaaracter.
8 FAIL

TEST PURPOSE #9
* When -k keydef option is specified, verify this utility is able to
define start/end position even if the lines have multibyte characters
(Especially check about the character position. i.e. 'field.character').

Can't handle key definition when field contains mutibyte characters.
9 FAIL

TEST PURPOSE #16
* When -pos option is specified, verify this utility is able to define
end position even if the lines have multibyte characters (Especially
check about the character position. i.e. 'field.character').

Can't handle key definition when field contains mutibyte characters.
16 FAIL

TEST PURPOSE #17
* When -c option is specified, verify this utility checks the file whose
lines are sorted according to the collating sequence of the current locale.

Can't sort input lines according to the collating sequence.
17 FAIL

TEST PURPOSE #19
* When -c and -d option are specified, verify this utility interprets
which character is a blank character or an alphanumeric character.

Can't interpret blank and alphanumeric character according to the
current locale.
19 FAIL

TEST PURPOSE #24
* When -c and -t option are specified, verify this utility use a
character as a field separator even if the character is a multibyte
character.

Can't handle field separator written in a multibyte chaaracter.
24 FAIL

TEST PURPOSE #25
* When -c and -k keydef option are specified, verify this utility is
able to define start/end position even if the lines have multibyte
characters (Especially check about the character position. i.e.
'field.character').

Can't handle key definition when field contains mutibyte characters.
25 FAIL

TEST PURPOSE #32
* When -c and-pos option are specified, verify this utility is able to
define end position even if the lines have multibyte characters
(Especially check about the character position. i.e. 'field.character').

Can't handle key definition when field contains mutibyte characters.
32 FAIL

TEST PURPOSE #33
* When -m option is specified, verify the outputs this utility makes is
sorted according to the collating sequence of the current locale.

Can't sort input lines according to the collating sequence.
33 FAIL

TEST PURPOSE #35
* When -m and -d option are specified verify this utility interprets
which character is a blank character or an alphanumeric character.

Can't interpret blank and alphanumeric character according to the
current locale.
35 FAIL

TEST PURPOSE #40
* When -m and -t option are specified, verify this utility use a
character as a field separator even if the character is a multibyte
character.

Can't handle field separator written in a multibyte chaaracter.
40 FAIL

TEST PURPOSE #41
* When -m and -k keydef option are specified, verify this utility is
able to define start/end position even if the lines have multibyte
characters (Especially check about the character position. i.e.
'field.character').

Can't handle key definition when field contains mutibyte characters.
41 FAIL

TEST PURPOSE #48
* When -m and -pos option are specified, verify this utility is able to
define end position even if the lines have multibyte characters
(Especially check about the character position. i.e. 'field.character').

Can't handle key definition when field contains mutibyte characters.
48 FAIL

TEST CASE: wc/wc

TEST PURPOSE #1
* When -m option is specified, verify this utility outputs the number of
characters in each input file even if the characters are multibyte
characters.

Can't count number of characters.
1 FAIL

TEST PURPOSE #2
* When this utility writes to the standard output the number of words,
this utility correctly recognizes the boundaries of words. The
boundaries are shown as white-space characters constituted in current
locale.

Can't count number of words.
2 FAIL

TEST CASE: cpio-fh/cpio-fh

TEST PURPOSE #2
* When -o and -v option is specified, verify this utility prints the
names of the affected files which is written in file-system-safe characters.

Can't print file names written in file-system-safe-characters.
2 FAIL

TEST PURPOSE #3
* When -i option is specified, verify this utility handles filenames
which is written in file-system-safe characters.

The archive file can't preserve file contents.
3 FAIL

TEST PURPOSE #4
* When -i option is specified, if extract files is selected in pattern
form, an '*' is matched more than 0 file-system-safe characters.

The archive file doesn't preserve file contents.
4 FAIL

TEST PURPOSE #5
* When -i option is specified, if extract files is selected in pattern
form, '?' is matched 1 file-system-safe characters.

The archive file doesn't preserve file contents.
5 FAIL

TEST PURPOSE #6
* When -i option is specified, if extract files is selected in pattern
form, matching list expression '[...]' is matched any one of the
enclosed file-system-safe characters.

The archive file doesn't preserve file contents.
6 FAIL

TEST PURPOSE #7
* When -i option is specified, if extract files is selected in pattern
form, a range expression '[c-c]' is matched any symbol between the pair
(inclusive). The range expression may not be matched multi-character
collating element and the range expression can be based on code point
order instead of collating element order.

The archive file doesn't preserve file contents.
7 FAIL

TEST PURPOSE #8
* When -i and -d option is specified, verify this utility creates the
directory whose name is written in file-system-safe characters.

The archive file doesn't preserve file contents.
8 FAIL

TEST PURPOSE #9
* When -i and -t option is specified, verify this utility prints the
filename which is written in file-system-safe characters.

Can't print file names written in file-system-safe-characters.
9 FAIL

TEST PURPOSE #10
* When -i and -v option is specified, verify this utility prints the
filename which is written in file-system-safe characters.

Can't print file names written in file-system-safe-characters.
10 FAIL

TEST PURPOSE #11
* When -p option is specified, verify this utility handles directory
name which is written in file-system-safe characters.

Can't handle directory names written in file-system-safe-characters.
11 FAIL

TEST PURPOSE #12
* When -p and -d option is specified, verify this utility creates the
directory whose name is written in file-system-safe characters.

Can't handle directory names written in file-system-safe-characters.
12 FAIL

TEST PURPOSE #13
* When -p and -v option is specified, verify this utility prints the
filename which is written in file-system-safe characters.

Can't print file names written in file-system-safe-characters.
13 FAIL

TEST CASE: tar-fh/tar-fh

TEST PURPOSE #1
* When keyword 'r' is specified, verify this utility attaches files
whose names are written in file-system-safe characters.

The archive file can't preserve file contents.
1 FAIL

TEST PURPOSE #2
* When keyword 'c' is specified, verify this utility packed files whose
names are written in file-system-safe characters into an archive.

The archive file can't preserve file contents.
2 FAIL

TEST PURPOSE #3
* When keyword 't' is specified, verify this utility prints filenames
which is written in file-system-safe characters.

Can't print filenames written in file-system-safe characters.
3 FAIL

TEST PURPOSE #4
* When keyword 'u' is specified, verify this utility appends a given
file if the archive has a file which is same name as the given one and
the given one is newer. The names of these files are written in
file-system-safe characters.

The archive file can't preserve file contents.
4 FAIL

TEST PURPOSE #5
* When keyword 'x' is specified, verify this utility extracts files
whose names are written in file-system-safe characters.

The archive file can't preserve file contents.
5 FAIL

TEST PURPOSE #6
* When keyword 'f' is specified, verify this utility handles the
filename which is written in file-system-safe characters.

Can't handle filenames written in file-system-safe characters.
6 FAIL


Review Information

Review Type SA Review
Start Date 2004-10-20 16:51
Last Updated 2004-11-03 17:27
Completed 2004-11-03 17:27
Status Complete
Review Resolution Rejected (REJ)
Review Conclusion Current LSB 1.3 certified implementations have either passed these tests
or have only the failures listed in PR.0037. The LSB Sample
Implementation has also verified the expected failures in PR.0037. For
this reason we have rejected this request.

 

Copyright 2005, The Free Standards Group, All Rights Reserved