Aurelien Jarno wrote:
Could you please test with LSB runtime version 2.0, ie the version
targeted for Sarge? If the test succeed with version 2.0, the problem
won't be fixed in Sarge.
The problem is fixed on Etch, which aims LSB 3.0 or 3.1 compliance.
The test did not change from LSB Version 2.0 to 3.1 (there is even no diff).
Also in execution the test results were the same.
This error is also found in a pre-realease-sarge test report: see the
reports at http://people.debian.org/~taggart/lsb/2.0/ and look for
(...)/ctime_X/T.ctime_X.
So it does block sarge LSB 2.0 conformance, too.
Greetings,
Martin
--
Martin Dittmar Linux Information Systems AG
Fon +49 (0)30 72 62 38-15 Ehrenbergstr 19
[EMAIL PROTECTED] D-10245 Berlin
The Migration Company. _______________________________ www.linux-ag.com
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
