On Friday, March 8, 2019 at 8:18:02 AM UTC-5, Dima Pasechnik wrote:
>
> On Fri, Mar 8, 2019 at 12:40 PM kcrisman <kcri...@gmail.com <javascript:>> 
> 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...) 
>

Weirdly, I had to do this again even after the update mentioned here 
(apparently going from 8.7.beta6 to 8.9.beta6).   Is this likely to happen 
every time we upgrade GAP?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/a06cf450-3b21-44de-be6b-b870dd27d64a%40googlegroups.com.

Reply via email to