Bug#204728: python2.3 distutils and glibc-2.3.2: no timestamps set.

[Matthias Klose <doko@cs.tu-berlin.de>]

Package: libc6
Version: 2.3.2-2
Severity: serious

This is strange... I am able to reproduce this. Something to do with
the new glibc (on i386 only?)?

- Packages built yesterday (using python2.3-3) are ok, see gadly in
  http://ftp-master.debian.org/~doko/python/

- The same package built after the upgrade to glibc-2.3.2 has
  timestamps "1970-01-01 01:00:01" on all files and directories
  installed by python setup.py (distutils). And the installer now
  rejects these packages ...

- Builds using python2.1 and python2.2 in the same dpkg-buildpackage
  run have the correct timestamps.

- Downgrading to 2.3.1-17 lets the builds succeed again.

Any hints?

Martin Sjögren writes:
> I uploaded a new version, but it got rejected:
> 
> Rejected: python2.3-pyopenssl_0.5.1-3_i386.deb: has 2 file(s) with a
> time stamp too ancient (e.g.
> usr/lib/python2.3/site-packages/OpenSSL/tsafe.py [Wed Dec 31 19:00:00
> 1969]).
> 
> Apparently, python 2.3's distutils does weird things:
> 
> $ python2.3 setup.py install_py
> creating build
> creating build/lib.linux-i686-2.3
> creating build/lib.linux-i686-2.3/OpenSSL
> copying ./__init__.py -> build/lib.linux-i686-2.3/OpenSSL
> copying ./__init__.py -> build/lib.linux-i686-2.3/OpenSSL
> copying ./tsafe.py -> build/lib.linux-i686-2.3/OpenSSL
> $ ls -l build/lib.linux-i686-2.3/OpenSSL/
> totalt 8
> -rw-r--r--    1 martin   martin        228 1970-01-01 01:00 __init__.py
> -rw-r--r--    1 martin   martin        992 1970-01-01 01:00 tsafe.py
> 
> 
> What on...? Should I just simply put a touch /usr/lib/... in my
> debian/rules, or is there a way to fix this?