for the record, i have re-uploaded MyghtyUtils generated from a  
windows machine and it resolves this issue.  i think the issue is  
some combination of a bug in tarfile.py combined with the fact that  
setuptools seems to be calling a private method on the tarfile module  
in the stack trace.  unfortuantely googling for this error message  
returns no hits at all (besides this thread).


On Jul 11, 2006, at 10:32 PM, primco wrote:

>
> There's a glitch in the published dev trunk setup process.
>
> I use this page http://pylonshq.com/docs/0.8.2/pylonsdev.html
>
> to install the latest trunk
> "python ez_setup.py -U http://pylonshq.com/svn/Pylons/trunk";
>
> and everything works fine until MyghtyUtils
>
> Some of the last bits of the traceback:
>
>   File
> "c:\python24\lib\site-packages\setuptools-0.6b4-py2.4.egg\setuptools 
> \arch
> ive_util.py", line 192, in unpack_tarfile
>     tarobj._extract_member(member,dst)  # XXX Ugh
>   File "C:\Python24\lib\tarfile.py", line 1440, in _extract_member
>     self.utime(tarinfo, targetpath)
>   File "C:\Python24\lib\tarfile.py", line 1572, in utime
>     raise ExtractError, "could not change modification time"
> tarfile.ExtractError: could not change modification time
>
> I can get around this (and have now, 5 or 6 times) if i download the
> MyghtyUtils-0.52.tar.gz from
> http://www.python.org/pypi/MyghtyUtils/0.52
> expand it with winrar and then, while in the folder, run "ez_setup ."
> It will install properly.
>
> I can run another "python ez_setup.py -U
> http://pylonshq.com/svn/Pylons/trunk";
> after the manual install and everything finishes correctly.
>
> davep
>
>
> >


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/pylons-discuss
-~----------~----~----~----~------~----~------~--~---

Reply via email to