Hello all. Clemens's analysis is correct; if you haven't been monkeying
around in ${prefix}/share/java/jython (and you would know if you had been)
then it is safe to force-activate.I have submitted a patch with Clemens's suggested fix, which does solve the issue in my testing: https://trac.macports.org/ticket/51981 -Aaron On Mon, Aug 8, 2016 at 5:24 AM Clemens Lang <c...@macports.org> wrote: > [re-sending from the address subscribed to the list] > > Hi Carlo, > > On Sat, Aug 06, 2016 at 06:34:26PM -0400, Carlo Tambuatco wrote: > > From running > > > > $> sudo port activate jython > > I committed a patch from https://trac.macports.org/ticket/51682 to > update Jython, but didn't see this problem (likely because I didn't have > the previous version installed when testing). I've put the patch author > on Cc, maybe he has an idea. > > > Error: org.macports.activate for port jython returned: Image error: > /opt/local/share/java/jython/cachedir/packages/MRJToolkit.pkc already > exists and does not belong to a registered port. Unable to activate port > jython. Use 'port -f activate jython' to force the activation. > > Please see the log file for port jython for details: > > > /opt/local/var/macports/logs/_opt_local_var_macports_registry_portfiles_jython-2.7.0_0_cd2dbc950d41a937798a03a6a2017ecdc4ee698a8850a64ac74d1d4c0b0b4cdf-2841/jython/main.log > > Warning: Failed to execute portfile from registry for jython > @2.7.0_0+installer > > ---> Activating jython @2.7.0_0+installer > > Error: port activate failed: Image error: > /opt/local/share/java/jython/cachedir/packages/MRJToolkit.pkc already > exists and does not belong to a registered port. Unable to activate port > jython. Use 'port -f activate jython' to force the activation. > > 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. > > -- > Clemens >
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
