On Fri, Mar 8, 2019 at 12:40 PM kcrisman <kcris...@gmail.com> wrote: > > > > On Friday, March 8, 2019 at 3:24:45 AM UTC-5, Dima Pasechnik wrote: >> >> https://trac.sagemath.org/ticket/27388 fixed the permissions, but >> because it's an upgrade from the state where there was a read-only >> file, it breaks (on OSX only) > > > Would that mean that, in general, upgrades from beta4 (which seems to be the > last version without this problem, according to one of the tickets) via git > pull and make will break indefinitely? Should we have a blanket > recommendation to rebuild from scratch?
this is too blanket :-) e.g. in this particular case it suffices to manually remove SAGE_LOCAL/share/gap and rebuild gap spkg (and then run make, naturally...) Certainly there is never a guarantee that a "git pull"+"make" would just work, as the current state could be beyond repair... > Thanks for any advice here - luckily from testing the app version I have some > still working Sage installs, but I like having my devel version separately > working. > > -- > You received this message because you are subscribed to the Google Groups > "sage-release" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-release+unsubscr...@googlegroups.com. > To post to this group, send email to sage-release@googlegroups.com. > Visit this group at https://groups.google.com/group/sage-release. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
