On Wednesday 24 August 2005 16:14, you wrote: > Jonathan Oddy wrote: > > expecting : May 14 2002 12:00AM and May 14 2002 8:58AM > > got : Tue May 14 00:00:00 2002 and Tue May 14 08:58:00 2002 > > While the dates may not be the format you expect, the dates themselves > are correct, so I'm not sure how this warrants a bug of "important" > severity. More to the point, however, is that changing interfaces > people have some to rely on (and I'm sure people already have scripts > running on Sarge that rely on this format) during a stable lifecycle is > a no-no. > > Given that this is changes in the latest upstream, and in Debian > unstable, AFAIK, there's probably not much else we can do about this. >
This isn't a bug from upstream. The following actions produce the correct date format: apt-get source libct1 extract freetds_0.61.orig.tar.gz configure (using the same flags as the Debian package) make, make install You'll also have to create a couple of sym links to libct1.so to keep some Debian packages happy. As far as I can tell this date format is unique to the Debian sarge (and possibly unstable (I haven't tried that yet)) packages. This issue has been mentioned at least once on the freetds mailing lists, with the conclusion that this date formatting is not normal behaviour. There seems to be no way to change the date format (setting the format in the locales.conf file has no effect), and many applications rely on the normal libct date format. -- Jonathan Oddy Systems Administrator - ADVFN Plc T: 02070700975 F: 02070700959 www.advfn.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
