Minutes of July 5 meeting
Andrew Josey <[email protected]>
| Newsgroups | gmane.linux.lsb.test-suite |
|---|---|
| Message-ID | <[email protected]> |
All Enclosed are the notes from this weeks call regards Andrew ---------------------- LSB Test Teleconference July 05 2005 Andrew Josey Mats Wichmann Stew Benedict Marvin Heffler General status: We opened for certification on July 1st . Companies wishing to get certified for LSB 3.0 can begin their preparation (register their companies, commence signature of the TMLA, start registering products). Detailed Status is as follows: For LSB Runtime certification, the following tests are approved: lsb-runtime, lsb-vsw4, and application battery At the meeting we approved lsb-c++ (qm/qmtest) for certification qm 2.2-2 i486, ia64, ppc, ppc64, s390, s390x, x86_64 qmtest_libstdcpp-3.4.3 3.lsb3 i486, ia64, ppc, ppc64, s390, s390x, x86_64 We approved the TET package for release. There is an action on Marvin to move these to the release tree for 3.0. Status of the other tools is as follows: lsblibchk still a problem with dladdr() - variability in results gone, six of seven platforms, have 18 failures (x2) (the same failure reported in two different ways) lsbcmdchk We think this is ready to be built, need to construct a release candidate. For certification it should be run with no switches Andrew has filed a bug on lsbcmdchk Need to log into the journal the command line used for invocation lsbappchk - need a verification on x86_64 We think this is fixed , move to a release candidate lsbpkgchk - This has been updated to report rpm header check errors to the journal. Now causing what we consider to be a conforming package to have 3 errors. lsbarchk - Pending one piece of work to tell it not to complain about source only symbols, it is useable as is. Andrew noted that he needs to enhance tjreport for its network waiver retrieval to be more specific on the type of the journal (although subsequently I now think it does not matter as each waiver has a test suite pathname, and the namespace for these is unique, so I can have multiple waivers for multiple test suites in a single waiver file).