Closed GoogleCodeExporter closed 9 years ago
issue with package manager when the package already exists.
This might be a bigger problem for core developers but there is the possibility
that someone would get a package from a friend as a zip file and then there
would be a conflict. Perhaps we can parse the library dir and recreate the
list of installed packages from that?
REDRCORE:DEBUG :
############################################################
Unhandled exception of type WindowsError occured at 2011-02-23 22:19:33.655000:
Traceback:
File: redRPackageManager.py, line 82 in installRRP
Code: os.mkdir(installDir) ## make the directory to store the zipfile into
WindowsError: [Error 183] Cannot create a file when that file already exists: u'C:\\Python26\\Lib\\site-packages\\RedRTrunk\\libraries\\RedRReshape'
############################################################
Original comment by kylecovi...@gmail.com
on 24 Feb 2011 at 4:21
this may be an issue if you dont have admin access to the file, which
is unlikely if you use our installer.
the other issue is if you are trying to delete an svn controlled dir.
.svn needs admin access to delete.
Original comment by anup.parikh
on 24 Feb 2011 at 5:19
I don't really understand this response. I have admin access to my computer
and Red-R is running as admin. I imagine that this could get really annoying
for developers testing our system.
Also does this require that packages be installed using our package manager
system?
Original comment by kylecovi...@gmail.com
on 26 Feb 2011 at 11:50
every time I start Red-R I get a message that new packages are available. I
tried to put the new versions on my machine but always get errors because I
have that package already (actually it's my own package so I know I have the
most up to date version).
Anyway, I want to be able to either ignore the new packages, reject them, or
something because it's really annoying to have to close the window every time.
A agree that users should be pushed to update to newer packages but developers
may be actually working on those packages.
Original comment by kylecovi...@gmail.com
on 28 Feb 2011 at 2:42
fixed, compare version numbers as floats instead of strings, don't prompt to
update if the local version is higher than or equal to the repository version.
Original comment by kylecovi...@gmail.com
on 4 Jun 2011 at 3:07
Original issue reported on code.google.com by
anup.parikh
on 12 Feb 2011 at 11:12