Report for week of June 9

This report will also become available as
http://www.linuxbase.org/impl/20030612.html
when the CVS updates to the website.


Sample Implementation and Application Battery Status

  Week of June 9, 2003

       1. Regular conference calls were held June 10 and 12. Attendance:
          Tuesday - unknown (was there a call?). Thursday - Wichmann,
          Anderson, Kraft, Beattie, Heffler.
       2. Main topic was to identify deliverables and owners. At the top
          level, deliverables are a new appbat release (11 apps x 3
          architectures), and the lsbsi release on ppc32. In addition,
there
          is now a push to add s390 to the released set so s390 appbat
and
          lsbsi are added. Further detail is added below.
       3. Since the Thursday call, beta lsbdev (base, cc, chroot)
packages
          are released.
       4. (Carryover from last time). Mats noted that the issue of the
Python
          curses module not building is still open. There are actually
two
          fails here, one on the curses module and one on the
curses_panel
          module; since the latter requires features not described by
the LSB
          it will be ignored. The Python patch also needs to be
regenerated
          as one addition is no longer needed, now being described by
the
          lsbdev headers. Mats will try to do this before the "official"
next
          appbat build..
       5. lsbdev-c++ needs to be moved towards released status;
currently it
          is in "snapshot" state for a few platforms. With the lsb,
needs to
          move to beta at least for ia32, ia64 and ppc32. Builds can be
done
          once the lsbdev packages are built: Stuart signed up to do
ia64,
          Marvin ia32, ppc32 and s390.
       6. The appbat will be rebuilt to test out the beta lsbdev
packages,
          and the result should also serve as the beta of the next
appbat
          release. Mats has bumped the rpm versions on the eleven
          certification packages, and will tag the appbat cvs tree after
a
          decision on whether a revised Python patch will be generated
or
          not. Stuart signed up to build and upload ia64, Marvin has
ppc32,
          s390 and ia32.
       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. The lsbsi for ppc32 has received considerable analysis.Two
          "unknown" failures remain, a SEGV inglob and a failure in
          tcgetattr. The *context routines are also a remaining issue,
but as
          they're a kernel problem, it's not indicative of an lsbsi
problem.
          To get to this state, a glibc patch had to be applied, so a
rebuild
          of the ppc32 lsbsi will be necessary prior to the next beta.
We
          will call this 1.3.1 since it differs slightly from what was
          released as 1.3.0 on ia32 and ia64. The glob failure is
apparently
          common with s390.
       9. Mats committed changes to MAKDEV permissions that will take
effect
          with 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 error - does it require a change to the si?
       11. The glibc symbol versioning issue on powerpc64 will be
covered in
          a separate meeting on Monday (June 16).. The "official" glibc
base
          version for powerpc64 is GLIBC_2.3, but at least one
distribution
          is working towards a release that will have GLIBC_2.2.5
symbols.
          The archLSB for powerpc64 says 2.2.5 as the symbol versions
were
          presumably drawn from an early version of that distribution.
       12. The s390 lsb-si is built cleanly and the lsb-runtime-test has
been
          run. A failure in glob appears to be in common with ppc32.
There
          are a very small number of additional failures still being
          analyzed. The three fold tests fail, this has been seen
elsewhere.
          A failure in vfwprintf has been fixed in the test suite in
cvs, but
          not in a released test suite.
       13. (Carryover from last time).The lsbsi is still missing
          install_initd/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 45 known internationalization failures in the
    LSB-si running the 1.3.x test suites.. They show non compliance in
the
    upstream packages diffutils (1), grep (3), gettext (1) 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/msgfmt/msgfmt 9 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