On 2010-12-05 15:28, Jeroen Demeyer wrote:
> It seems that sage -f sagenb-VERSION doesn't actually do anything. It
> does NOT change the devel/sagenb-main directory. This issue also breaks
> upgrading sage-4.6 to sage-4.6.1.alpha3 for me, because sagenb is not
> actually upgraded. Either I'm doi
On 2010-12-08 16:28, Mitesh Patel wrote:
> I've reproduced this when upgrading "manually" from a copy ('cp -a') of
> vanilla 4.6 to 4.6.1.alpha3 on OS X 10.6 (bsd.math)
>
> http://groups.google.com/group/sage-release/browse_thread/thread/8dbb88f4bb9a6c27/fca9c2ed57255675?#fca9c2ed57255675
>
> and
On 12/05/2010 08:28 AM, Jeroen Demeyer wrote:
> It seems that sage -f sagenb-VERSION doesn't actually do anything. It
> does NOT change the devel/sagenb-main directory. This issue also breaks
> upgrading sage-4.6 to sage-4.6.1.alpha3 for me, because sagenb is not
> actually upgraded. Either I'm
On 2010-12-05 15:28, Jeroen Demeyer wrote:
> It seems that sage -f sagenb-VERSION doesn't actually do anything. It
> does NOT change the devel/sagenb-main directory. This issue also breaks
> upgrading sage-4.6 to sage-4.6.1.alpha3 for me, because sagenb is not
> actually upgraded. Either I'm doi
It seems that sage -f sagenb-VERSION doesn't actually do anything. It
does NOT change the devel/sagenb-main directory. This issue also breaks
upgrading sage-4.6 to sage-4.6.1.alpha3 for me, because sagenb is not
actually upgraded. Either I'm doing something wrong, or I'm making the
sagenb spkg w
