Hello, John Palmieri recently helped me with a ticket (#16350) where the > spkg-install > of a package was changed but that was not enough to trigger the necessary > rebuild. That could be accomplished by adding '.p0' to the > package-version.txt > because patch level changes don't change the actual version string of the > package > but still force a rebuild. >
In this case the "offending" ticket was #9493 (authors: Leif and Jean-Pierre, reviewer: me). The actual ECL version was the same, there was just a change in packaging where unneeded stuff was removed from the tarball. The package-version.txt was updated (version number changed by appending a date, patchlevel reset to empty). There was no reason to change the patchlevel of Maxima since nothing changed there. The problem is that Maxima somehow needs to re-register itself as an ECL package so the reinstalled ECL knows that it exists. It may be possible to do this in an easier way than by reinstalling Maxima, but setting SAGE_UPGRADING=yes solved the problem for me. As for making SAGE_UPGRADING=yes the default, I personally keep it unset and only set it to yes when encountering problems such as this (but the patchbot I am running has it set to yes). I would probably keep doing this if the default were changed, to avoid the annoying unnecessary reinstallations mentioned by others. Peter -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
