Re: [sage-release] 7.1.beta1 released

>> I did not want to increase the version, as it would mean to indicate a >> newer version of cliquer, and it's arguably the same, as far as the >> functionality goes. > > You could have called it dimacliquer-1.21 or something... I think that' s what the .p1, .p2, .p are useful for. So that the

Re: [sage-release] Re: error: Cannot perform incremental update

> It happened again with 7.0. > > Running 'make' a second time, as previously, did the job. Happened again with the latest beta. I'll do a "make dist-clean", hoping that it will not happen again later on. Nathann -- You received this message because you are subscribed to the Google Groups

Re: [sage-release] Re: error: Cannot perform incremental update

> Could you say more precisely *what happened exactly* again. Do you mean more than what I reported in the first message of this thread? Nothing changed since that time as far as I can tell. At each new beta I checkout develop and pull the new commits, then run 'make' and this message happens. If

Re: [sage-release] Re: error: Cannot perform incremental update

> So you're not running "make distclean" at all? No. But I did 5 seconds ago and I am now recompiling everything. Perhaps the problem will not happen again. > Did you verify that you're really on origin/develop, without any other > commits or uncommited changes? Yes yes. I am always on the

Re: [sage-release] Re: error: Cannot perform incremental update

> The definition of insanity is doing the same thing over and over again, but expecting different results ;-) That's what I should answer the next guy who will try the "it's irresponsible to not vote" lecture on me. Nathann > > > > > > > On Sunday, January 24,

Re: [sage-release] Re: error: Cannot perform incremental update

>> I am sure if we were electing the best Sage bugs, you won't abstain... > I vote for http://trac.sagemath.org/ticket/10609 Come on, it's ridiculous alright but you cannot vote for it: it's not even a Sage bug. I'm rather glad, by the way, that being unable to produce such high-quality bugs we

Re: [sage-release] Re: error: Cannot perform incremental update

> I am sure if we were electing the best Sage bugs, you won't abstain... I hope that our first reflex with be to try to fix them instead of voting on them :-P > (and, interestingly, most probably next time the election results would be > different...) The most fitting name for what is called

Re: [sage-release] Re: error: Cannot perform incremental update

> > After this double "make" (the first that fails with the message above, > the second that works) it is a regular directory. If it happens again > I will post here. > It happened again with 7.0. Running 'make' a second time, as previously, did the job. Nathann -- You received this

Re: [sage-release] Re: error: Cannot perform incremental update

> After you run "make distclean & make", is lib64 a symlink? If its not then > its a bug. After this double "make" (the first that fails with the message above, the second that works) it is a regular directory. If it happens again I will post here. Nathann -- You received this message because

Re: [sage-release] Re: error: Cannot perform incremental update

> I guess you mean "make distclean && make" (double ampersand) I did. Nathann -- 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

Re: [sage-release] Re: error: Cannot perform incremental update

> If "make distclean" fails then its not going to do anything, duh. Delete > SAGE_LOCAL by hand or "git clean -f -d -x" 'make distclean' did not fail: only 'make' failed. And I am not stuck: the first call to 'make' fails with the error reported above, but the second worked alright and I am now

Re: [sage-release] error: Cannot perform incremental update

Yo, > This should if and only if you upgrade from Sage <= 7.0.beta1 to Sage >= > 7.0.beta2. It definitely happened several times. > Maybe you just switched between old and new branches? No, the way I work with git this is not possible. Nathann -- You received this message because you are

Re: [sage-release] Sage 7.0.beta0 released

> I added -L${SAGE_LOCAL}/lib to the spkg-install of both > readline and ncurses (for good measure) and this resolves > the linking problem I had with ncurses on OpenSuSE Leap. Thanks ! Adding: LDFLAGS="$LDFLAGS -L${SAGE_LOCAL}/lib" to SAGE_ROOT/build/pkgs/r/spkg-install solved my problem.

Re: [sage-release] Sage 7.0.beta0 released

> I think we should just globally add -L${SAGE_LOCAL}/lib to LDFLAGS, there > shouldn't be any reason to prefer system libraries over libraries in Sage Sounds right. Now, it is not that I don't want to create the ticket/branch, but I am perfectly aware that I do not understand the consequences

Re: [sage-release] Sage 7.0.beta0 released

I failed to build this latest release because of the 'R' package (see logfile [1]). It fails at this step: configure: error: --with-readline=yes (default) and headers/libs are not available I am running "debian testing", with libreadline-dev installed. Nathann [1]

Re: [sage-release] Sage 7.0.beta0 released

> R's own config.log, not the Sage config.log... Sorry, I misunderstood. It is there: http://www.steinertriples.fr/ncohen/tmp/config.log Nathann -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving

Re: [sage-release] Sage 7.0.beta0 released

> Can you post the config.log? It does the right thing on my machine: SAGE_ROOT/config.log is there: http://www.steinertriples.fr/ncohen/tmp/config.log Thanks, Nathann -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this

Re: [sage-release] Sage 7.0.beta0 released

> ldd -r on that readline library may reveal a lack of rpath. Err Does the following "talks" to you ? :-P (d|✔)~/.Sage/local/lib$ ldd -r libreadline.so ./libreadline.so: /home/ncohen/.Sage/local/lib/libtinfo.so.5: no version information available (required by ./libreadline.so)

Re: [sage-release] Sage 7.0.beta0 released

> Is libtinfo.so.5 a proper library or a symlink? And what does > nm -d libtinfo.so.5 | grep tgetflag > reports? (d|✔)~/.Sage/local/lib$ ls -lsh libtinfo.so.5 0 lrwxrwxrwx 1 ncohen ncohen 15 Dec 23 09:38 libtinfo.so.5 -> libtinfo.so.5.9 (d|✔)~/.Sage/local/lib$ nm libtinfo.so.5 | grep tgetflag

Re: [sage-release] Sage 7.0.beta0 released

> So it looks like an ncurses problem: Hm O_o But it is using Sage's readline package, and I was compiling after a 'distclean' O_o Nathann -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop

Re: [sage-release] Sage 6.10.beta4 released

Thaanks ! Nathann On 12 November 2015 at 07:13, Volker Braun wrote: > As always, you can get the latest beta version from the "develop" git > branch. Alternatively, the self-contained source tarball is at > http://www.sagemath.org/download-latest.html > > 0d3caa0

Re: [sage-release] Sage 6.9.beta6 released

My mistake: the compilation of Cython files just finished, and some doc building jobs started. So nothing to worry about, sorry. And good night :-) Nathann On 10 September 2015 at 22:21, Nathann Cohen <nathann.co...@gmail.com> wrote: > A small question: is it normal that the doc buil

Re: [sage-release] Re: Sage 6.9.beta3 released

I agree, just running make (the default target) should execute doc-clean before building the documentation. I'm doing this on the buildbot by hand since otherwise lots of builds fail. Do you think it would make sense to trigger a 'make clean' every time you switch to a new beta? I also do

Re: [sage-release] Sage 6.9.beta2 released

Thanks ! On 13 August 2015 at 23:14, Volker Braun vbraun.n...@gmail.com wrote: As always, you can get the latest beta version from the develop git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html 314664c Updated Sage version to

Re: [sage-release] Sage 6.8.rc0 released

sage -t --long src/sage/graphs/generators/smallgraphs.py # 1 doctest failed This one is my fault. It has been fixed there: http://trac.sagemath.org/ticket/18911 and is perhaps caused by the fact that I do have gap_packages installed, so this test is run, but then the output is wrong!

Re: [sage-release] Sage 6.8.beta7 released

When running on a ppc64 machine, I get: sage -t --warn-long 97.8 src/sage/graphs/distances_all_pairs.pyx ** File src/sage/graphs/distances_all_pairs.pyx, line 1205, in sage.graphs.distances_all_pairs.diameter Failed example:

Re: [sage-release] Re: Sage 6.8.beta3 released

No, that version really is installed. I know that because (1) $ cat build/pkgs/database_cremona_ellcurve/package-version.txt 20150519 I was trying to convince you that this, in particular, does *not* mean that you have the latest version installed on your computer. and (2) when I run Sage

Re: [sage-release] README.txt

The src/README.txt files on sage mirrors, e.g. http://files.sagemath.org/src/README.txt are out of date. Is that a know problem? Is this list the right place to report it? I think that Harald is the only one who can do something about that. Nathann -- You received this message because

Re: [sage-release] README.txt

I could put that link onto the download page. Then it's still there (in some sense) and zero maintenance. +1 Nathann -- 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

Re: [sage-release] Re: sage releases - DOI number?

The new feature, oops, bug is the show() command in 6.6 . Simply don't render correctly the output. The same command and examples still working in version 6.5. I've used a fresh Ubuntu and Fedora latest installation. A related discussion on #18289: http://trac.sagemath.org/ticket/18289

Re: [sage-release] sage releases - DOI number?

Task force. The Sage guys Nathann -- 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

Re: [sage-release] Re: Sage 6.5.beta1 released

We upgraded glpk O that's right ! Nathann -- 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

Re: [sage-release] Re: Sage 6.5.beta1 released

Hello ! Hence another question : shouldn't the doctests either avoid multiple solutions problem if multiple solutions exist, or test against the whole solution (set of all acceptable solution, if it can be finitely expressed) ? We should indeed try to find examples with a unique solution

Re: [sage-release] Sage 6.4.beta4 released

Good, I hope somebody will clean up some of the unnecessarily long doctests This is not the only occasion for which we need something between reporting an error or saying nothing. What about a bit red warning when running the tests on a file, that would show the list of very long doctests ?

Re: [sage-release] Sage 6.3 released

Helloo !! Does that mean that the online doc will also be updated ? Nathann On 10 August 2014 17:31, Volker Braun vbraun.n...@gmail.com wrote: Both the master and develop git branch have been updated to the 6.3 release. Source tarball:

Re: [sage-release] Sage-6.3.rc0 released

Weaseling out of things is what separates us from the animals. Well, except the weasel. - Homer J Simpson I was already aware that Homer J Simpson was one of the world's greatest thinkers, but I wouldn't have imagined missing so much by not always watching the original version. Pearls

[sage-release] Re: Sage 6.3.beta8 released

Doctesting shouldn't require a web connection, at least as long as you don't specify --optional=internet... NATHANNN ;-) Sorry T_T Nathann -- You received this message because you are subscribed to the Google Groups sage-release group. To unsubscribe from this group and stop

Re: [sage-release] Sage 6.3.beta4 release

Heelll yeah ! More designs O_O_O_O_O_O_O_O_O http://youoffendmeyouoffendmyfamily.com/wordpress/wp-content/uploads/2013/08/20050121_v_homer-simpson4.jpg Nathann On 19 June 2014 15:26, Volker Braun vbraun.n...@gmail.com wrote: As usual, get your fix from the develop git branch or

Re: [sage-release] Sage 6.2 released

Hello ! [calculus ] Exception occurred: [calculus ] File ecl.pyx, line 337, in sage.libs.ecl.ecl_safe_eval (sage/libs/ecl.c:4352) [calculus ] RuntimeError: ECL says: Module error: Don't know how to REQUIRE MAXIMA. [calculus ] The full traceback has been saved in

Re: [sage-release] Re: Sage 6.3.beta2 released

sage -f ecl, followed by sage -f maxima did it for me. Did the job for me. Thanks ! :-) nathann -- 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

Re: [sage-release] Re: Sage 6.3.beta2 released

Lazyness? You are not lazy, and neither am I. Do we change that ? It seems that setting this to False does not help in any way, least of all if it is the default behaviour. My problem is that I do not know how to change such things. Do you ? Nathann -- You received this message because you

Re: [sage-release] Re: Sage 6.3.beta2 released

E.g. by simply adding the lines SAGE_UPDGRADING ?= yes export SAGE_UPGRADING I know how to fix my problem, I just don't know how to fix Sage. (And I originally only wanted to add an additional target 'upgrade', setting the variable to 'yes' and depending on 'build'. When 'yes' is the

Re: [sage-release] Re: Sage 6.3.beta2 released

Open a ticket and someone might feel less lazy :) I don't believe in opening tickets without writing the patch and setting them to needs_review :-P Nathann -- You received this message because you are subscribed to the Google Groups sage-release group. To unsubscribe from this group and stop

Re: [sage-release] Re: Sage 6.3.beta2 released

Yoo !! Why would we need a buggy upgrade script ? Backwards compatibility. And I personally don't want ATLAS to get rebuilt just because someone decided to change the spkg-install script of readline such that Python gets rebuilt upon which unfortunately ATLAS depends, just

Re: [sage-release] Sage 6.3.beta1 released

That's what I call a Combinatorial Designs Release :-P Helll YEAH Nathann P.S. : Thaaanks Volker ! ;-) On 13 May 2014 17:34, Volker Braun vbraun.n...@gmail.com wrote: Get it from the updated develop git branch or the

Re: [sage-release] Sage 6.2.beta5 released

Hellooo ! Updated and recompiled with make. Everything went fine, except that building the doc never terminates. It just does nothing after a while, probably some multithreading problem. I typed make doc-clean make, same result. ... Oh. I just noticed this by scrolling up a bit :

Re: [sage-release] Sage 6.2.beta5 released

Hellooo !! How much RAM do you have? 4GB Do you set SAGE_NUM_THREADS? Whats the value of SAGE_NUM_THREADS in a Sage shell? It is set to 4. Nathann -- You received this message because you are subscribed to the Google Groups sage-release group. To unsubscribe from this group and

Re: [sage-release] Sage 6.2.beta5 released

That should be enough if your swap is set up correctly. How much swap space do you have? (e.g. output of top) Ahem. 0GB. I don't believe in SWAP. Okay, so I should change the number of threads to 3 or 2 ? :-P Nathann -- You received this message because you are subscribed to the Google

Re: [sage-release] Re: Sage 6.2.beta3 released

Ah, ok. There is currently a race with the installation of setuptools-using Python packages (which includes matplotlib dependencies). This looks very much like it. It will be fixed by http://trac.sagemath.org/ticket/13201, I hope... H,... I will probably give this branch a try, as I

Re: [sage-release] Re: Sage 6.2.beta3 released

(the trac ticket says that the branch cannt be automatically merged, by the way. It appears in red) On 11 March 2014 10:42, Nathann Cohen nathann.co...@gmail.com wrote: Ah, ok. There is currently a race with the installation of setuptools-using Python packages (which includes matplotlib

Re: [sage-release] Re: Sage 6.2.beta3 released

Just try make again, its likely to not hit that particular race all the time. Or build in serial. Hmmm.. I built from scratch after pulling branch #13201 and I got an error while building scipy. But perhaps it is because I fixed the merge conflict in a bad way. Hmmm... Still no Sage. :-P

[sage-release] Re: Sage 6.2.beta3 released

Because Sage would not start anymore after I finally achieved to reproduce this bug, I tried to recompile Sage from scratch... And ended up with that : NOTE: Set SAGE_MATPLOTLIB_GUI to anything but 'no' to try to build the Matplotlib GUI.

Re: [sage-release] Sage 6.2.beta3 released

~/.Sage is my SAGE_ROOT. Nathann On Monday, 10 March 2014, Dima Pasechnik dimp...@gmail.com wrote: On 2014-03-10, Nathann Cohen nathann.co...@gmail.com javascript:; wrote: By this bug, you mean even after a make distclean it does not compile? Or just get to a step where make doesn't work

Re: [sage-release] Re: Sage 6.2.beta2 released

How can one merge the latest release into a branch, before first checking out that branch? git checkout trac/develop # or whatever the name of develop is on your install git checkout -b new_branch git pull trac u/ncohen/whatever This creates an empty branch on develop, then merges the distant

Re: [sage-release] Re: Sage 6.2.beta3 released

H I typed make then make doc-clean then make again, and I now have exactly the same problem as Dima O_o OSError: [reference] WARNING: Unable to fetch /home/ncohen/.Sage/src/doc/output/doctrees/en/reference/sets/environment.pickle make: *** [doc-html] Error 1 ~/.Sage$ cat

Re: [sage-release] Re: Sage 6.2.beta3 released

Nathann, congratulations on creating the first Sage-docs tree eating git worm ;-) Come on, I just used git commit --amend to change a commit message. I didn't kill anyone (I hope) :-P Nathann -- You received this message because you are subscribed to the Google Groups sage-release group. To

Re: [sage-release] Re: Sage 6.2.beta3 released

Hell !! suppose I previosuly had beta2 installed from the tarball. What is the git way to get the update? Would 'git pull' followed by 'make' be enough? Yep. First make sure that your current branch is actually the beta2 release (and not some ticket's branch, or something you are

Re: [sage-release] Re: Sage 6.1 released

Those are the multi-threaded (pthread) versions. It is preferable if you have them, though we can of course just work with the single-threaded version. Oh. I see. Do I patch the manual then ? Nathann -- You received this message because you are subscribed to the Google Groups sage-release