On Tue, Oct 21, 2014 at 10:02 AM, kcrisman <kcris...@gmail.com> wrote:
> > > >> What port does the Sage upgrade use so that IT can add a firewall rule >> for me to upgrade Sage? >> >> > Hi! I'm not sure what you mean; usually the easiest thing to do to > upgrade Sage is either > 1) download a new binary manually and just use that one, since the > metadata is not in the Sage binary > I meant #sage -upgrade . The only reason I am not downloading and exploding the binary package is that it does not claim support for Yosemite. My old 6.2 is working, but I figured it stood a better chance of working correctly if I natively compile it in OS X 10.10. > 2) recompile a Sage you have already built from scratch by pulling from > the latest git repository > Also, though I am scared to try this nowadays, > Might run into the same firewall issue. > 3) In theory I think "sage -upgrade" still works... > It worked for 6.2. > > Thanks, Chris -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
