[ python-Bugs-786194 ] posixmodule uses utimes, which is broken in glibc-2.3.2

SourceForge.net noreply at sourceforge.net
Wed Jan 25 09:36:40 CET 2006


Bugs item #786194, was opened at 2003-08-10 11:34
Message generated for change (Comment added) made by doko
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=786194&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Extension Modules
Group: Python 2.3
Status: Closed
Resolution: None
Priority: 7
Submitted By: Matthias Klose (doko)
Assigned to: Neal Norwitz (nnorwitz)
Summary: posixmodule uses utimes, which is broken in glibc-2.3.2

Initial Comment:
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.


----------------------------------------------------------------------

>Comment By: Matthias Klose (doko)
Date: 2006-01-25 09:36

Message:
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.


----------------------------------------------------------------------

Comment By: Neal Norwitz (nnorwitz)
Date: 2006-01-25 07:26

Message:
Logged In: YES 
user_id=33168

Closing due to inactivity.

----------------------------------------------------------------------

Comment By: Neal Norwitz (nnorwitz)
Date: 2005-10-02 07:54

Message:
Logged In: YES 
user_id=33168

Matthias, can this be closed?  Is this still relevant?

----------------------------------------------------------------------

Comment By: Matthias Klose (doko)
Date: 2003-08-10 12:54

Message:
Logged In: YES 
user_id=60903

for an utimes check see
http://lists.debian.org/debian-glibc/2003/debian-glibc-200308/msg00115.html

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=786194&group_id=5470


More information about the Python-bugs-list mailing list