> 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...) 
Great, thanks!  Apparently that sufficed.

> Certainly there is never a guarantee that a "git pull"+"make" would 
> just work, as 
> the current state could be beyond repair... 
Yes, of course!  In this case I had a working Sage install at beta1 or 
beta2, though.

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.

Reply via email to