➜
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2003-08-10 09:34 by doko, last changed 2022-04-10 16:10 by admin. This issue is now closed.
| Messages (6) | |||
|---|---|---|---|
| msg17693 - (view) | Author: Matthias Klose (doko) *  |
Date: 2003-08-10 09:34 | |
Maybe this is category 'Build' ... at least it results in '1970/01/01-01:00:01' timestamps on all files copied by distutils on glibc-2.3.2 based systems (2.3.1 seems to be ok). Disabling the detection of the utimes function in configure works around this. As this function is a wrapper around utime, why not use this one directly? Or check, if utimes correctly works. |
|||
| msg17694 - (view) | Author: Matthias Klose (doko) * |
Date: 2003-08-10 10:54 | |
Logged In: YES user_id=60903 for an utimes check see http://lists.debian.org/debian-glibc/2003/debian-glibc-200308/msg00115.html |
|||
| msg17695 - (view) | Author: Neal Norwitz (nnorwitz) * |
Date: 2005-10-02 05:54 | |
Logged In: YES user_id=33168 Matthias, can this be closed? Is this still relevant? |
|||
| msg17696 - (view) | Author: Neal Norwitz (nnorwitz) * |
Date: 2006-01-25 06:26 | |
Logged In: YES user_id=33168 Closing due to inactivity. |
|||
| msg17697 - (view) | Author: Matthias Klose (doko) * |
Date: 2006-01-25 08:36 | |
Logged In: YES user_id=60903 It is not necessary for glibc-2.3.5 and more recent versions, older glibc versions still have the problem. |
|||
| msg17698 - (view) | Author: Neal Norwitz (nnorwitz) * |
Date: 2006-01-25 08:41 | |
Logged In: YES user_id=33168 Thanks for the comment. I don't think we will try to cater to this bug in glibc. BTW, are you still working on Debian a lot? Are there many outstanding bugs wrt python? |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-10 16:10:34 | admin | set | github: 39040 |
| 2003-08-10 09:34:23 | doko | create | |