Issue1205206

classification
Title: Bad cachefile paths in packages.idx
Type: Severity: normal
Components: None Versions:
Milestone:
process
Status: closed Resolution: accepted
Dependencies: Superseder:
Assigned To: bzimmer Nosy List: bzimmer
Priority: normal Keywords: patch

Created on 2005-05-19.18:51:35 by anonymous, last changed 2005-05-19.18:51:39 by nobody.

Files
File name Uploaded Description Edit Remove
jython_amd_problem.patch nobody, 2005-05-19.18:51:39 CachedJarsPackageManager.java patch
Messages
msg2444 (view) Author: Nobody/Anonymous (nobody) Date: 2005-05-19.18:51:35
When the jar file in packages.idx exists, but the cache 
file path that it maps to is bad, jython complains that it 
cannot write a new cachefile.

This fix causes jython to regenerate the path for the 
cachefile (using cachedir and the jar filename) rather 
than reusing the bad path in the .idx file.

The code assumed that if a jar existed in the .idx, its 
associated cachefile path should be reused to write a 
new cachefile.  This is a bad assumption if you run 
jython on the same set of jars, but your cachedir is in 
an automounted directory.  The automounted directory 
can be different depending upon the machine you are 
running from
History
Date User Action Args
2005-05-19 18:51:35anonymouscreate