2009/6/18 Craig Citro <craigci...@gmail.com>:
>
> Hi all,
>
> Here's rc3, which *should* be the last rc for this release cycle. I've
> tested it on my laptop and the build farm, and I've had no troubles at
> all, and it's currently going on a few other machines, so hopefully
> that'll turn out fine, too. Please test it and let me know if you run
> into anything at all.
>
> Source and sage.math binary are here:
>
> http://sage.math.washington.edu/home/craigcitro/release/sage-4.0.2.rc3.tar
>
> http://sage.math.washington.edu/home/craigcitro/release/sage-4.0.2.rc3-x86_64-Linux.tar.gz
>
> I believe that the necessary upgrade bits are sitting here, but I
> haven't tried it:
>
> http://sage.math.washington.edu/home/craigcitro/release/sage-4.0.2.rc3/
>
> I think Minh will hopefully reply with a list of changes, but I want
> to mention one that I'm excited about: I added the merge script that I
> wrote with Nick Alexander. (It doesn't have an official review yet --
> shh! :) ) I need to sit down and write more documentation, but here's
> a quick summary: use sage -merge <ticket_number> to test the patches
> on a trac ticket. There's a -t option for deciding which files to
> test, -n to decide the number of threads to use, -r for which
> repository to commit things to. By default, it pops all patches after
> you're done. With -l, it leaves them in the queue, and with -f it
> commits them to the repository on a successful test (f for finish, as
> in qfinish). (These two can't be combined, of course, because that
> doesn't make any sense.) There's -d to save the patches to another
> directory (it currently uses a temp directory), and -o to overwrite
> the patch files when it finds them (it won't by default). Finally, -c
> by itself lists all patches with positive review on trac, and -a
> instead of a ticket number does the above to all patches listed by -c.
> I said more about this in my last message on the rc1 thread.
>
> -cc
I wanted to try out this feature. Here is what happened. I built
4.0.2.rc3 from scratch, made a clone called test, cd'd into
devel/sage-test, initialised MQ by "sage -hg qinit". And then:
j...@host-57-89%sage -merge -c
Traceback (most recent call last):
File "/home/jec/sage-current/local/bin/sage-apply-ticket", line 20,
in <module>
import sage.misc.hg as hg
File "/home/jec/sage-4.0.2.rc3/devel/sage-tests/sage/misc/hg.py",
line 43, in <module>
from misc import tmp_filename, branch_current_hg, embedded
File "/home/jec/sage-4.0.2.rc3/devel/sage-tests/sage/misc/misc.py",
line 28, in <module>
import sage.misc.prandom as random
File "/home/jec/sage-4.0.2.rc3/devel/sage-tests/sage/misc/prandom.py",
line 56, in <module>
from sage.misc.randstate import current_randstate
ImportError: No module named randstate
Similar error with any other sage -merge command. Am I doing something wrong?
John
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
