Status for week of June 16

Text reprint of http://www.linuxbase.org/impl/20030619.html
which may take a little bit to make it out to the website.

-- mats



Document's Title: LSB-si/LSB-appbat Status

Sample Implementation and Application Battery Status

  Week of June 16, 2003

       1. The June 17 call was cancelled; the June 19 call was held.
          Attendance: Wichmann, Anderson, Kraft, Heffler.
       2. Beta lsbdev (base, cc, chroot) packages were released last
week.
       3. Analysis of the Python curses module issue revealed that there
are
          some changes needed to the LSB curses.h header. Mats has sent
out a
          multi-part analysis on the lsb-appbat list; the group agreed
that
          the missing items that are both documented in Xcurses and
          implemented in ncurses 5.2 should be added. The items in
Xcurses
          that are not implemented in ncurses 5.2, even if they appear
in
          ncurses 5.3, will be deferred to a future specification. Mats
will
          reissue the email as a set of specific recommendations.
       4. With the change to the curses header, Python and lynx are
affected.
          Mats will test that with the change (a) Python's curses module
          builds and tests okay, and (b) lynx can build without the
current
          part of the patch that compensates for the absence of a couple
of
          defines.
       5. lsbdev-c++ builds were done by Marvin and Stuart. Marvin has
          uploaded these to the FSG beta directory for ia32, ppc32 and
s390
          (I believe missing the .deb packages). Stuart has uploaded
ia64
          packages to ~anderson on the server.
       6. Appbat packages have also been built and uploaded.
       7. The 'lsb' packages for other architectures can now be built.
The
          package has no contents, just supplies a couple of
dependencies and
          basically initializes the rpm database in the lsbsi. It's
already
          autobuilding successfully, all that's needed is for someone
(with
          access to the build environments) to build packages that look
          released, rather than snapshots.
       8. Progress has been made on lsbsi failure analysis. The ppc32
          tcgetattr failure is identified as belonging to the underlying
          kernel and is not an lsbsi failure. The ppc32 *context
routines are
          also a kernel issue. The glob failure is common with s390 and
          Itanium, and there is a glibc patch available for it.
Preliminary
          testing indicates this patch takes care of the problem at
least on
          Itanium. The list of "known failures" has been revised to
indicate
          44 expected failures, and one new failure introduced by a new
test
          since the last certification test version (1.3.3) - there's an
LSB
          bugreport on this, the spec seems to disagree with current
          implementation.
       9. Mats committed changes to MAKDEV permissions that will take
effect
          with lsbsi 1.3.1 - /dev/MAKEDEV will be installed mode 0755
          (instead of 0754) so that the applicable test passes.
       10. Mats will cvs tag the lsbsi sources, but not until a
determination
          on the glob patch - does it go in, should it go in the glibc
lsb
          patch or be a separate patch.
       11. The glibc symbol versioning issue on powerpc64 remains open;
the
          interested parties are negotiating a solution.
       12. The above indicate that all platforms except ia32 need a
fresh
          lsbsi build and release, even though the changes are minor.
       13. (Carryover). The lsbsi is still missing install_initd and
          remove_initd. These are really failures to conform to the
spec, but
          as there's no test, even an existence test, they aren't
flagged as
          such by the testing procedure. Still looking for volunteers to
work
          on both a sample implementation and a test suite - there was a
          thought that Novell might be interested, to be explored
further. An
          idea raised in the past might be worth considering: the sample
          could perhaps work on a non-standard location so that
"cheaters"
          who try to install a startup script directly instead of using
the
          required tool to install them could get detected by installing
in
          the lsbsi.
       14. Because there have been database changes to symbol versions,
          lsbappchk and lsblibchk need to be reissued in addition to
lsbdev.
          Chris has normally built these, so it falls to him again.
There's
          also a desire to produce an lsbcc-built version of appchk and
          libchk to be using in testing inside the lsbsi, since the
Linux
          dynamic linker is not present in the lsbsi. No owner was
assigned
          to set up these packages.



    --------------------------------------------------------------



Variances



    This section documents the known variances of the lsbsi from LSB
version
    1.3.

    The lsbsi does not provide required tools install_initd and
remove_initd.

    The following are the 44 known internationalization failures in the
    LSB-si running the 1.3.3 test suites. They show non compliance in
the
    upstream packages diffutils (1), grep (3) and textutils (40). The
choice
    is made to leave these unpatched, although the li18nux website, does
have
    patches available, to highlight the status of the upstream packages.

    /tset/LI18NUX2K.L1/utils/diff/diff 2 FAIL
    /tset/LI18NUX2K.L1/utils/egrep-tp/egrep-tp 5 FAIL
    /tset/LI18NUX2K.L1/utils/fgrep/fgrep 5 FAIL
    /tset/LI18NUX2K.L1/utils/fold/fold 1 FAIL
    /tset/LI18NUX2K.L1/utils/fold/fold 2 FAIL
    /tset/LI18NUX2K.L1/utils/fold/fold 3 FAIL
    /tset/LI18NUX2K.L1/utils/grep-tp/grep-tp 5 FAIL
    /tset/LI18NUX2K.L1/utils/join/join 3 FAIL
    /tset/LI18NUX2K.L1/utils/join/join 4 FAIL
    /tset/LI18NUX2K.L1/utils/pr/pr 1 FAIL
    /tset/LI18NUX2K.L1/utils/pr/pr 3 FAIL
    /tset/LI18NUX2K.L1/utils/pr/pr 4 FAIL
    /tset/LI18NUX2K.L1/utils/pr/pr 5 FAIL
    /tset/LI18NUX2K.L1/utils/pr/pr 6 FAIL
    /tset/LI18NUX2K.L1/utils/sort/sort 8 FAIL
    /tset/LI18NUX2K.L1/utils/sort/sort 9 FAIL
    /tset/LI18NUX2K.L1/utils/sort/sort 10 FAIL
    /tset/LI18NUX2K.L1/utils/sort/sort 11 FAIL
    /tset/LI18NUX2K.L1/utils/sort/sort 12 FAIL
    /tset/LI18NUX2K.L1/utils/sort/sort 13 FAIL
    /tset/LI18NUX2K.L1/utils/sort/sort 14 FAIL
    /tset/LI18NUX2K.L1/utils/sort/sort 15 FAIL
    /tset/LI18NUX2K.L1/utils/sort/sort 16 FAIL
    /tset/LI18NUX2K.L1/utils/sort/sort 24 FAIL
    /tset/LI18NUX2K.L1/utils/sort/sort 25 FAIL
    /tset/LI18NUX2K.L1/utils/sort/sort 26 FAIL
    /tset/LI18NUX2K.L1/utils/sort/sort 27 FAIL
    /tset/LI18NUX2K.L1/utils/sort/sort 28 FAIL
    /tset/LI18NUX2K.L1/utils/sort/sort 29 FAIL
    /tset/LI18NUX2K.L1/utils/sort/sort 30 FAIL
    /tset/LI18NUX2K.L1/utils/sort/sort 31 FAIL
    /tset/LI18NUX2K.L1/utils/sort/sort 32 FAIL
    /tset/LI18NUX2K.L1/utils/sort/sort 40 FAIL
    /tset/LI18NUX2K.L1/utils/sort/sort 41 FAIL
    /tset/LI18NUX2K.L1/utils/sort/sort 42 FAIL
    /tset/LI18NUX2K.L1/utils/sort/sort 43 FAIL
    /tset/LI18NUX2K.L1/utils/sort/sort 44 FAIL
    /tset/LI18NUX2K.L1/utils/sort/sort 45 FAIL
    /tset/LI18NUX2K.L1/utils/sort/sort 46 FAIL
    /tset/LI18NUX2K.L1/utils/sort/sort 47 FAIL
    /tset/LI18NUX2K.L1/utils/sort/sort 48 FAIL
    /tset/LI18NUX2K.L1/utils/unexpand/unexpand 1 FAIL
    /tset/LI18NUX2K.L1/utils/uniq/uniq 2 FAIL
    /tset/LI18NUX2K.L1/utils/uniq/uniq 3 FAIL

    There is an additional failure that occurs in beta
    runtime test 1.3.5, which adds some new tests. This
    failure is listed separately since it is not yet
    detected by an official certification release. The
    program is part of the gettext package, and the issue
    is the subject of LSB bug 703372.

    /tset/LI18NUX2K.L1/utils/msgfmt/msgfmt 9 FAIL