#51981: jython: Fix issue upgrading from 2.5.2 to 2.7.0 ------------------------------+-------------------------------- Reporter: aaron+macports@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: haspatch | Port: jython ------------------------------+-------------------------------- As reported on [https://lists.macosforge.org/pipermail/macports- users/2016-August/041280.html macports-users], when upgrading from jython 2.5.2 to 2.7.0 there is a conflict with an existing file in jython's package cache that prevents activation. Analysis by Clemens Lang on the list (for some reason not visible on the web version linked above) is correct:
From the error message if seems that the old jython port didn't install files in /opt/local/share/java/jython/cachedir/packages, but the new version comes with a pre-populated cachedir and now causes these problems if the cache has been generated by other means meanwhile.
I don't know anything about jython, but if somebody more familiar with jython can confirm that this sounds about right, I think I know a way to work around this: Add a pre-activate {} block that deletes these files (since jython should be the only port putting files in this directory if I understand things correctly).
Yeah I know what it says, but I’m afraid to force the activation because I don’t know what else will be affected.
Since these are just cache entries, it should be safe to force activation.
The attached patch addresses the issue. -- Ticket URL: <https://trac.macports.org/ticket/51981> MacPorts <https://www.macports.org/> Ports system for OS X