Re: [sage-release] 7.1.beta1 released

[Nathann Cohen]

>> 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 name/version does not change, and still match upstream, even
when we touch the tarballs.

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 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.

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

[Nathann Cohen]

> 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 
"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.

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

[Nathann Cohen]

> 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 I type 'make' again right after the
message does *not* appear, and the compilation goes on.

Which is what I did this morning. Right now it is compiling fine.

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 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.

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

[Nathann Cohen]

> 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 upstream develop and nothing else.

> The next time that you try this, can you please keep the complete output of
> what each of these "make" commands produces, together with the output of "ls
> -l . local" from $SAGE_ROOT and the contents of config.log and the output of
> "git status" and "git log|head".

The next report I will send here will contain this information, if the
problem occurs again after the full rebuild. The output of the second
'make', however, is usually very long as the command is successful :-)

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 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.

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

[Nathann Cohen]

> 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, 2016 at 4:21:50 AM UTC-5, Nathann Cohen wrote:
>>
>> > 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 upstream develop and nothing else.
>>
>> > The next time that you try this, can you please keep the complete
output of
>> > what each of these "make" commands produces, together with the output
of "ls
>> > -l . local" from $SAGE_ROOT and the contents of config.log and the
output of
>> > "git status" and "git log|head".
>>
>> The next report I will send here will contain this information, if the
>> problem occurs again after the full rebuild. The output of the second
>> 'make', however, is usually very long as the command is successful :-)
>>
>> 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 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.

-- 
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.

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

[Nathann Cohen]

>> 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 have to import them from elsewhere.

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 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.

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

[Nathann Cohen]

> 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 'democracy' nowadays is a
'probabilistic dictatorship'. You have a pool of 4~5 guys, and at
every election they roll a dice to know which one will be officially
in charge. Of course it's 100% sure that it will be one of these guys,
which makes it a dictatorship.

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 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.

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

[Nathann Cohen]

>
> 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 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.

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

[Nathann Cohen]

> 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 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.

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

[Nathann Cohen]

> 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 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.

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

[Nathann Cohen]

> 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 reviewing #19586 :-)

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 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.

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

[Nathann Cohen]

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 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.

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

[Nathann Cohen]

> 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.

Should I create a branch that does that ?

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 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.

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

[Nathann Cohen]

> 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 of something
like that S if you don't mind I prefer to not be the one who
does it ^^;

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 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.

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

[Nathann Cohen]

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] http://www.steinertriples.fr/ncohen/tmp/r-3.2.3.p0.log

On 23 December 2015 at 12:52, Volker Braun  wrote:
> The diff you mention is in the configure.ac, so you need to reconfigure
> (i.e. run SAGE_ROOT/bootstrap)
>
> On Wednesday, December 23, 2015 at 11:21:39 AM UTC+1, Sébastien Labbé wrote:
>>
>>
>>
>> On Wednesday, December 23, 2015 at 11:16:18 AM UTC+1, François wrote:
>>>
>>> It looks like one ticket for the packages of type `script` wasn’t
>>> included then.
>>
>>
>> But I can see that http://trac.sagemath.org/ticket/19427 merged in
>> sage-7.0.beta0 contains the diff:
>>
>> - echo >&2 "The content of \"$PKG_TYPE_FILE\" must be 'base', 'standard',
>> 'optional', 'experimental' or 'pip'"
>> + echo >&2 "The content of \"$PKG_TYPE_FILE\" must be 'base', 'standard',
>> 'optional', 'experimental', 'script', or 'pip'"
>>
>> Therefore, I guess patchbot are not running sage-7.0.beta0 cleanly...
>
> --
> 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.

-- 
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.

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

[Nathann Cohen]

> 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 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.

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

[Nathann Cohen]

> 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 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.

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

[Nathann Cohen]

> 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)
linux-vdso.so.1 (0x7ffd3afae000)
libtinfo.so.5 => /home/ncohen/.Sage/local/lib/libtinfo.so.5 (0x7fde9a7fe000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fde9a45a000)
/lib64/ld-linux-x86-64.so.2 (0x7fde9ac7c000)

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 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.

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

[Nathann Cohen]

> 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
00013430 T tgetflag

(I removed the -d from 'nm -d', as it complained that -d was an invalid option)

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 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.

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

[Nathann Cohen]

> 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 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.

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

[Nathann Cohen]

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 Updated Sage version to 6.10.beta4
> 68f7f3d Trac #19569: Section "inputs" to "input" in docstrings
> 1ab8c18 Trac #19437: SR.symbol: correct parent in inherting classes of
> SymbolicRing
> fcfc41e Trac #19564: Remove pointers from boost_interface
> 5b69d99 Trac #19549: Get rid of libtool archives (*.la)
> 9129f4d Trac #19545: Mathon's pseudocylic strongly regular graphs.
> 36c1b8a Trac #17447: Clarify and complete documentation of function()
> d5ab06e Trac #18100: Parallelization of computations on tensors on free
> modules
> 6a5513d Trac #19512: is_morphism for maps of products of projective spaces
> c47eac8 Trac #19560: Mpir broken with SAGE_FAT_BINARY
> d4f6764 Trac #19485: Legible legends
> c67dcca Trac #19304: Fix hash function of rationals
> 0af1537 Trac #19550: Parameter name 'method' -> 'algorithm'
> df1fba6 Trac #19546: Graphs: is_cartesian_product with empty and 1-element
> graph
> 299902b Trac #19544: Implement chromatic quasisymmetric functions
> 6298ed8 Trac #19539: make Graphics.plot refuses argument
> b24d1a5 Trac #19535: Use future division in colors
> 30a0f9c Trac #19526: Certain methods fail on immutable graphs
> 416424e Trac #19494: Make finite word method nb_subword_occurences_in much
> faster
> c977b06 Trac #19534: fixing a few bad trac roles, and adding some
> 4c7e4e7 Trac #19382: move elliptic_curve_congruence graph from graphs to
> elliptic_curves
> fdfcffd Trac #18597: Implement m-Cambrian lattices (using delta sequences)
> 9a3540e Trac #19530: Graphs: indentation errors in docstrings
> 1a29192 Trac #18043: Support for HyperbolicPlane() in modform_hecketriangle
> be94746 Trac #19522: Change default for MILP variables to nonnegative=False
> 3dc3aa5 Trac #19497: Improve comparison framework
> df27c1d Trac #19441: broken interact for cluster seeds
> 94635cc Updated Sage version to 6.10.beta3
>
> --
> 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 http://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Nathann Cohen]

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 builds before the
> compilation of updated Cython files is finished? How can the doc of
> those files be correct if they have not even been built yet?
>
> Nathann
>
> On 10 September 2015 at 22:03, Nathann Cohen <nathann.co...@gmail.com> wrote:
>> Thaanks !!!
>>
>> On 10 September 2015 at 22:02, 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
>>>
>>> 559f73b Updated Sage version to 6.9.beta6
>>> fc7a4e6 Trac #19067: Incomplete sentences in the automatically generated
>>> documentation
>>> 03309fe Trac #19011: Add Jones representation of braid groups and Jones
>>> polynomials of braid closures
>>> 80cd325 Trac #19157: Remove trailing whitespace from doc sources
>>> 8f1d706 Trac #19156: Docbuilder intersphinx references have undeterministic
>>>  titles
>>> df7243c Trac #19175: Convert ore_algebra into a new-style package
>>> d0e1f11 Trac #19174: new style database_jones_numfield package
>>> fca2e79 Trac #19173: Get rid of random.pxi
>>> 7b3bdbf Trac #18964: New Method: FiniteStateMachine.kleene_star
>>> c40c260 Trac #19164: Remove GAP3 package
>>> 3f0b4cd Trac #19159: Check if a word is a Christoffel word.
>>> 11fca5a Trac #19161: LatticePoset: faster is_complemented()
>>> cb90e2d Trac #18965: New Method: FiniteStateMachine.concatenation
>>> d5c3067 Trac #19008: Graphs, is_subgraph() documentation polishing
>>> eb018ce Trac #19166: Replace conf.py copies by symlinks
>>> c3c139f Trac #18992: Automaton.determinisation: do not ignore leading
>>> epsilon transitions
>>> 304bd1b Trac #18981: New Method: FiniteStateMachine.completion
>>> 7d8fb5b Trac #18973: New automaton recognizing a word
>>> 2f727c6 Trac #18070: FiniteStateMachine: Moments of waiting time
>>> cb91abd Trac #18987: Parallel computation of number of solutions in dancing
>>> links
>>> 2d90ef5 Trac #18979: avoid Maxima on creation of symbolic matrices
>>> 94e4585 Trac #18857: Install fplll includes in the default location
>>> b5a5321 Trac #19098: implement Taylor 2-graphs for U_3(q) and related srg's
>>> 2c322c6 Trac #19079: ConstructionFunctor: remove __str__
>>> 1761131 Trac #18547: Improve polynomial powering in positive characteristic
>>> 4b26783 Trac #18246: remove naive __hash__ from SageObject
>>> 283c0fe Trac #18859: Change sage -i to install with dependencies --
>>> documentation
>>> c9be94f Trac #19129: Turn off test suite for Python 2
>>> 57cbc03 Trac #19101: Change sage -i to install with dependencies
>>> 6fb16e6 Trac #19146: brial also depends on python
>>> c770aa0 Trac #19133: Three Witt-based strongly regular graphs
>>> 81e09c3 Trac #19104: Parse sage-spkg options in sage-spkg
>>> 1155fbd Trac #19144: brial should depend on pkgconf
>>> 822107a Trac #19115: Rename lib-clean target as sagelib-clean
>>> 7b0f1c8 Trac #17211: m4rie testsuite fails with segfault on OSX 10.10
>>> 4a698a8 Trac #18886: Remove comparison boilerplate - part 3
>>> 8751abc Trac #18814: Polyhedron.delete -> _delete
>>> 6bed172 Trac #18656: Cache rational_diagonal_form()
>>> 4ecc7cc Trac #18186: Add cardinality() to MatrixSpace
>>> 662557a Trac #17151: symbolic Laguerre / associated Laguerre polynomials
>>> f6bde65 Trac #19110: QQ(0)^-1 raises SIGFPE (which is caught)
>>> 70f7b1c Updated Sage version to 6.9.beta5
>>>
>>> --
>>> 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 http://groups.google.com/group/sage-release.
>>> For more options, visit https://groups.google.com/d/optout.

-- 
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 http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Nathann Cohen]

 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  make doc-clean every time I pull
a release.

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 to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Nathann Cohen]

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 6.9.beta2
 029ecbb Trac #19022: a few badly formatted REFERENCE block
 fd064f2 Trac #19020: random failure with BalancedIncompleteBlockDesign.arc
 5bc9321 Trac #19017: improving the big_oh interface + passing keywords
 99c962c Trac #18931: Boost shortest paths
 f12ad24 Trac #18695: propagate the variable domain to the assumptions
 database
 bb5b286 Trac #18613: Errors with is_isomorphic() for trivial cones
 9b43535 Trac #10224: (new-style) packages for saclib 2.2.6 and qepcad-B.1.69
 c91abb3 Trac #19015: Doc formatting error: Undirected graphs,
 is_triangle_free
 e47e2a8 Trac #18714: Dual bases for finite fields
 df7ec0c Trac #19013: Bug 2 in intersection of polyhedron (generic backend)
 0040782 Trac #19012: Bug in intersection of polyhedron (generic backend)
 60b8835 Trac #18982: New non-existence tests for strongly regular graphs
 c94418a Trac #17425: Rational isometry test for quadratic forms over number
 fields
 d845450 Trac #14846: CycleIndexSeries derivative, integral, exponential
 methods are not combinatorial
 a7676d8 Trac #10951: ecmfactor should take as optional argument the sigma
 value
 f0aaad4 Trac #18568: doctest fix for wrong expansion of (x+sqrt(2)*x)^2
 2955be3 Trac #18360: doctest fix for: symbolic matrices fail operations
 minus and mul
 70023b0 Trac #17542: IncidenceStructure.coloring
 fbbff1c Trac #18998: Add a (175,72,20,36)-strongly regular graph, and two
 more similarly constructed ones
 7cdda8b Trac #18986: IncidenceStructure.is_uniform, is_regular, and
 complement
 6dbe2aa Trac #18929: Include igraph library
 ad5a080 Trac #18953: Replace pipestatus by build/bin/sage-logger
 c28807b Trac #18922: Speedup creation of spin crystals
 560d259 Trac #18996: pyzmq depends on cython
 0a22894 Trac #18995: Approximate LP solving with GLPK: do not raise
 exceptions
 c5e9e81 Trac #18994: Update to setuptools 18.1
 83bef8d Updated Sage version to 6.9.beta1

 --
 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 http://groups.google.com/group/sage-release.
 For more options, visit https://groups.google.com/d/optout.

-- 
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 http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Nathann Cohen]

 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!

Yepyep, precisely. But at least now we notice when it breaks :-P

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 to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Nathann Cohen]

 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:
 G.diameter(method='iFUB')
 Expected:
 0
 Got:
 Exception OverflowError: 'value too large to convert to uint32_t' in
 'sage.graphs.distances_all_pairs.diameter_iFUB' ignored
 0
 **

Odd. This line computes the diameter of a 1-vertex graph 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 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 http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Nathann Cohen]

 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 I see the extra data which was only introduced
 in this last update:

Now that is different.

Could you tell me the output of the following command?

ls SAGE_ROOT/local/var/lib/sage/installed/database_cremona_ellcurve*

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 to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] README.txt

[Nathann Cohen]

 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 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 http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] README.txt

[Nathann Cohen]

 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 email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Nathann Cohen]

 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

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 to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Nathann Cohen]

 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 to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Nathann Cohen]

 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 group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Nathann Cohen]

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 (for the
tests). It can however be useful to leave a simple example with a
not tested flag meant to the users, as examples with only one
solution are often 1) not interesting 2) much more complicated.

This being said, this doctest has been around for a long time. Did you
by any chance install a new LP solver ? This doctest breaks on my
computer too, but that's because of gurobi :-)

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 to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Nathann Cohen]

 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 ?

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 to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 6.3 released

[Nathann Cohen]

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:
 http://boxen.math.washington.edu/home/release/sage-6.3.tar.gz

 sha512sum sage-6.3.tar.gz
 03f8016ddd5029915846be01a6f77c4e1496b2d7751858ef0188fc7229aff107a0fb4d09bc3f2517a1cc69b4025fb96945b404b7686eba0ea8cfbe8b526e
 sage-6.3.tar.gz

 Mini Changelog since 6.3.rc1

 00199fb Updated Sage version to 6.3
 9891a9e Trac #16789: Combinatorial designs use internet during doctest
 d9dbf6f Trac #16766: Improve the doc of combinat/designs/
 b3f1223 Updated Sage version to 6.3.rc1

 Diffstat since 6.2:

 $ git diff --stat=80 6.2 6.3
  .gitignore |3 +
  VERSION.txt|2 +-
  build/deps |   24 +-
  build/install  |1 +
  build/pkgs/atlas/spkg-install  |2 +-
  .../cddlib/patches/lib-src-gmp_Makefile.am.patch   |7 +
  .../cddlib/patches/lib-src-gmp_Makefile.in.patch   |   15 +-
  .../pkgs/cddlib/patches/src-gmp_Makefile.am.patch  |8 +-
  .../pkgs/cddlib/patches/src-gmp_Makefile.in.patch  |   19 +-
  build/pkgs/combinatorial_designs/SPKG.txt  |   29 +
  build/pkgs/combinatorial_designs/checksums.ini |4 +
  .../pkgs/combinatorial_designs/package-version.txt |1 +
  build/pkgs/combinatorial_designs/spkg-install  |4 +
  build/pkgs/configure/checksums.ini |6 +-
  build/pkgs/configure/package-version.txt   |2 +-
  build/pkgs/d3js/SPKG.txt   |   33 +
  build/pkgs/d3js/checksums.ini  |4 +
  build/pkgs/d3js/package-version.txt|1 +
  build/pkgs/d3js/spkg-install   |   15 +
  build/pkgs/d3js/spkg-src   |   41 +
  build/pkgs/database_cremona_ellcurve/checksums.ini |6 +-
  .../database_cremona_ellcurve/package-version.txt  |2 +-
  build/pkgs/database_gap/checksums.ini  |6 +-
  build/pkgs/database_gap/package-version.txt|2 +-
  build/pkgs/ecl/checksums.ini   |6 +-
  build/pkgs/ecl/package-version.txt |2 +-
  build/pkgs/ecl/patches/gmp.patch   |   33 +
  build/pkgs/ecl/spkg-install|7 +
  build/pkgs/ecl/spkg-src|8 +-
  build/pkgs/gap/SPKG.txt|4 -
  build/pkgs/gap/checksums.ini   |6 +-
  build/pkgs/gap/package-version.txt |2 +-
  build/pkgs/gap/patches/osx_10_4.patch  |   36 -
  build/pkgs/gap/patches/sparc_segfault.patch|   25 -
  build/pkgs/gap_packages/checksums.ini  |6 +-
  build/pkgs/gap_packages/package-version.txt|2 +-
  build/pkgs/gap_packages/spkg-install   |2 +-
  build/pkgs/gap_packages/spkg-src   |2 +-
  build/pkgs/git/package-version.txt |2 +-
  build/pkgs/git/spkg-install|1 +
  build/pkgs/graphs/spkg-install |6 +-
  build/pkgs/ipython/SPKG.txt|6 -
  build/pkgs/ipython/checksums.ini   |6 +-
  build/pkgs/ipython/package-version.txt |2 +-
  ...w-InputTransformers-to-raise-SyntaxErrors.patch |  673 
  build/pkgs/jmol/patches/testjava.sh|   13 -
  build/pkgs/jmol/spkg-install   |6 -
  build/pkgs/libgap/SPKG.txt |2 +-
  build/pkgs/libgap/checksums.ini|6 +-
  build/pkgs/libgap/package-version.txt  |2 +-
  build/pkgs/libgap/patches/sparc_segfault.patch |   25 -
  build/pkgs/libgap/spkg-install |3 +-
  build/pkgs/lrcalc/SPKG.txt |   39 -
  build/pkgs/lrcalc/checksums.ini|8 +-
  build/pkgs/lrcalc/package-version.txt  |2 +-
  build/pkgs/lrcalc/patches/lrcalc-1.1.7-jump.patch  |  138 +
  build/pkgs/lrcalc/spkg-install |9 +
  build/pkgs/maxima/SPKG.txt |   62 +-
  build/pkgs/maxima/checksums.ini|6 +-
  build/pkgs/maxima/package-version.txt  |2 +-
  ...id-blowing-the-stack-when-diff-expand-isn.patch |8 +-
  build/pkgs/maxima/patches/matrixexp.patch  |   13 +
  build/pkgs/maxima/patches/maxima_bug_2526.patch|9 +-
  build/pkgs/maxima/spkg-src |6 +-
  build/pkgs/mcqd/SPKG.txt   |   29 +
  build/pkgs/mcqd/checksums.ini  |4 +
  build/pkgs/mcqd/package-version.txt|1 +
  

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

[Nathann Cohen]

 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 like that just do not translate.

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 to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Nathann Cohen]

 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 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 http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Nathann Cohen]

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 download the tarball
 at http://boxen.math.washington.edu/home/release/sage-6.3.beta4.tar.gz

 Mini-changelog:

 920c16e Updated Sage version to 6.3.beta4
 1162c3d Trac #16488: upgrade to IPython 2.1
 6084949 Trac #16303: 'make doc-clean' calls system-wide 'git', which may
 break 'make distclean'
 e9dd721 Trac #15137: Implement right-angled Artin groups
 27ea650 Trac #16476: New difference family (25,4,1) and cleanup in bibd.py
 f132b47 Trac #16373: OA(18,273), OA(12,474), OA(33,993)
 afe1c47 Trac #16482: Update developer manual for git's push-url feature
 0231de9 Trac #16424: is_triangular_number() cleanup
 ef64a29 Trac #16487: Fix ascii art of tableaux
 fa45133 Trac #16361: OA(7,66), OA(7,68), OA(8,69), OA(7,74) and OA(8,76)
 9e9652d Trac #16461: Difference families... and more BIBD
 88ffbc7 Trac #16223: Removes the Graph Theory constructions pages
 d23f8bf Trac #9107: Nested class name mangling can be wrong in case of
 double nesting
 1af722a Trac #16472: get rid of PermutationsNK
 a1f24f9 Trac #10534: Cleanup in choose_nk, split_nk, subword, subset
 15b5595 Trac #16455: Update zeromq and pyzmq to recent version and new git
 layout
 cb92c74 Trac #16260: Python 2.7.7
 47bb4d8 Trac #16440: GAP 4.7.5
 d150838 Trac #16415: Ignore case in package directory
 0cc2c53 Trac #16291: Fixing associativity of FormalCompositeMap
 149db41 Trac #15639: Random failure in integer_vector
 7b1b00e Trac #16464: cyclotomic_cosets for any finite ring
 23073ae Trac #14364: The jmol spkg contains testjava.sh
 2659b96 Trac #16469: some_code.random_element() does not return immutable
 elements
 8f8af5f Trac #15493: qqbar.ANRoot creates tons of copies of interval fields
 7edf205 Trac #16391: Helper functions for OA constructions
 7e95177 Trac #16460: a cache for OA/TD/MOLS existence
 5579f4f Trac #16356: MOLS for n=18,57,154,276,298,342
 7752f87 Trac #16295: Faster is_orthogonal_array
 99533b2 Trac #16462: Segfault in factorization of multivariate polynomials
 (Singular 3.1.6)
 de1deb6 Trac #16458: Braid group creates elements in wrong class
 c794e8b Trac #16383: Can't evaluate a polynomial on a finite field if
 representation is not poly
 46dc3f1 Trac #16438: Use d3js package if available
 eeb700c Trac #13528: ymin is not respected in logarithmic plots
 1dd3939 Trac #16431: sync-build is broken
 fa04b13 Trac #16374: better two_squares, three_squares, four_squares for
 small input
 7c0e90d Trac #15547: Fix the creation of tikzpictures of projections of
 polytopes
 a4cf855 Trac #16452: Making the reference manual's introduction more concise
 d6a65a0 Trac #16445: load and attach need parentheses
 39f86db Trac #16319: Implement k-closures for matroids
 cfd79dc Trac #11215: Periods for Modular Forms
 0cab68b Trac #16394: bijection from Dyck words to triangulations + random
 Dyck word
 666d724 Trac #16370: OA(k,n) strongly regular graphs
 addcf21 Trac #16067: Python 3 preparation: The semantic of filter() function
 is changed
 8c06d03 Trac #2952: Multivariate LaurentPolynomial can have coefficients in
 the wrong ring
 25b260f Trac #14306: regression in solve
 3162199 Trac #15494: Deprecate the _boundary parameter
 22ffb07 Trac #16388: Specify the values of k,n in the exceptions
 5d4858d Trac #16434: Package d3.js
 179a520 Trac #15595: Shuffle Product
 ac9e526 Trac #16433: clique_with_loops.is_strongly_regular() is True
 c5dfb9a Trac #16101: Python backend for Polyhedra

 --
 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 http://groups.google.com/group/sage-release.
 For more options, visit https://groups.google.com/d/optout.

-- 
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 http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 6.2 released

[Nathann Cohen]

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 
 /var/folders/k8/nj0z1bkd11dcs1v5hbh_tknc92p43w/T/sphinx-err-LRSqym.log, if 
 you want to report the issue to the developers.

That's exactly the bug I had ! I was advised to run this :

sage -f ecl  sage -f maxima  sage -b

 I've had more trouble with building doc since the git switch than I can shake 
 a stick at.

I *LOVE* this expression.

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 to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Nathann Cohen]

 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 sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Nathann Cohen]

 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 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 http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Nathann Cohen]

 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 default,
 I don't know what the opposite target should be called;
 'quick-and-dirty-upgrade-not-really-rebuilding-dependent-packages' perhaps,
 or 'unsafe-rebuild'.)

Why would we need a buggy upgrade script ?

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 to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Nathann Cohen]

 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 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 http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Nathann Cohen]

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
 because its spkg-install is a * Python instead of a shell script.  There
 are lots of similar situations [where you know rebuilding isn't necessary].

That's what I meant by I don't know how to fix such things. I did
not know this was involved :-/

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 to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Nathann Cohen]

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 source tarball at
 http://boxen.math.washington.edu/home/release/sage-6.3.beta1.tar.gz

 Mini-changelog:

 36af814 Trac #16265: transducers.weight: new common transducer
 bbc23e1 Trac #15099: Implement numeric evaluation of zetaderiv
 cf5d0ef Trac #16211: Implement Hadamard 3-Designs
 bfdc6bd Trac #16266: FiniteStateMachine: option to show empty final word
 out labels
 a0c2366 Trac #16237: IncidenceStructureFromMatrix bug
 f570746 Trac #16236: Five mutually orthogonal latin squares of order 12
 a8d46e6 Trac #16241: New MOLS shared by Ian Wanless
 b9e5ab4 Trac #13525: PALP Normal Form
 62cdef5 Trac #16279: BIBD from Transversal Designs
 76cc2cb Trac #16257: Unnatural syntax of G.relabel()
 4daeef7 Trac #15896: integration of polynomials in several variables is
 buggy
 6e63e7d Trac #16235: A pair of orthogonal latin squares of order 10
 65f5404 Trac #16286: Allow k=None in MOLS/TD/OA
 9bfc378 Trac #16277: MOLS constructions rom the Handbook of Combinatorial
 Designs
 7e8936b Trac #15036: Speed up matrix repr for matrices larger than 20
 0e865af Trac #16314: Allows to construct subclasses of labelled tree from
 a labelled tree
 c8419d0 Trac #16284: Remove some deprecated code
 cabf93b Trac #6637: standardize the interface to TransitiveIdeal and
 friends
 5c3a089 Trac #16328: Add a category parameter for Module
 bf9d925 Trac #16307: Fix small bug in G.strong_orientation()
 ac40f14 Trac #16251: Polynomials with unhashable coefficients should be
 unhashable
 9b70b5f Trac #15970: j_invariant_qexp won't allow substitution
 fedf214 Trac #15897: UniqueFactory for QuaternionAlgebras
 1ff Trac #16253: FiniteStateMachine: Introduce final_word_out
 5da2b22 Trac #16248: Some trivial Orthogonal Arrays (when n=1)
 bfbd34c Trac #16244: Simplify TestSuite's some_elements role and logic (no
 random sampling)
 b66ec41 Trac #16272: redesign transversal designs
 da70f288 Trac #15704: Stupid waste of time in graphs 1
 d5a5f2b Trac #15018: add recover_formula and prefix_to_infix functions to
 logicparser.py
 ddfcd0d Trac #13445: Cuspidal subspace of modular forms over finite field
 contains forms that are not cus
 faef6e8 Trac #11475: improve prime_pi (speedup + small fixes)
 58184a6 Trac #16315: Modify the header of the tests for k-Schur book
 de4ce33 Trac #11719: Add is_monomial() to power series and laurent series
 ring elements
 b9dfe03 Trac #15780: Increase Performance in Projective Morphism
 acf040a Trac #16326: spring cleanup for dyck_word.py
 0a6c3b4 Trac #16297: followup to #16196: strip multiple 'sage:' prompts
 d54a991 Trac #16300: upgrade setuptools to 2.2b1

  --
 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 http://groups.google.com/group/sage-release.
 For more options, visit https://groups.google.com/d/optout.


-- 
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 http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Nathann Cohen]

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 :

Exception in thread Thread-7:
Traceback (most recent call last):
  File /home/ncohen/.Sage/local/lib/python/threading.py, line 808, in
__bootstrap_inner
self.run()
  File /home/ncohen/.Sage/local/lib/python/threading.py, line 761, in run
self.__target(*self.__args, **self.__kwargs)
  File /home/ncohen/.Sage/local/lib/python/multiprocessing/pool.py, line
325, in _handle_workers
pool._maintain_pool()
  File /home/ncohen/.Sage/local/lib/python/multiprocessing/pool.py, line
229, in _maintain_pool
self._repopulate_pool()
  File /home/ncohen/.Sage/local/lib/python/multiprocessing/pool.py, line
222, in _repopulate_pool
w.start()
  File /home/ncohen/.Sage/local/lib/python/multiprocessing/process.py,
line 130, in start
self._popen = Popen(self)
  File /home/ncohen/.Sage/local/lib/python/multiprocessing/forking.py,
line 121, in __init__
self.pid = os.fork()
OSError: [Errno 12] Cannot allocate memory

And well.. I was not running anything else at that time ^^;

Nathann


On 23 March 2014 21:56, Volker Braun vbraun.n...@gmail.com wrote:

 The develop branch on git has been updated to 6.2.beta5. Alternatively,
 you can download the source tarball:


 http://boxen.math.washington.edu/home/release/sage-6.2.beta5/sage-6.2.beta5.tar.gz

 $ git log --first-parent develop ^6.2.beta4 --oneline
 9db8c5c Updated Sage version to 6.2.beta5
 cca671d Trac #15975: FiniteStateMachine.determine_alphabets: corrected
 description of parameter reset
 76d428a Trac #15286: Latin squares
 e0eee52 Trac #15907: Improvements for affine factorization crystal
 ebd2c00 Trac #15331: Do not try to create embedded number field morphisms
 for non-embedded number fields
 5e64ce2 Trac #15925: Use Brzozowski' algorithm as default for minimizing
 non-deterministic automata
 6fdfd13 Trac #15924: Allow non-hashable output labels in
 FiniteStateMachine.prepone_output
 671feb5 Trac #15923: Incorrect TypeError in
 FiniteStateMachine.add_from_transition_function
 3065fe6 Trac #15922: Allow list of transitions in
 FiniteStateMachine.add_transistions_from_function
 25361b7 Trac #13774: Irreducible Cartan types created as reducibles
 8bd99a7 Trac #13609: symbolic arithmetic errors
 4f70b4d Trac #15973: Allow GAP to compile on OS X 10.4
 25255ca Trac #15824: Remove deprecated code from matrix/
 2092418 Trac #15940: Improve printing for rigged configurations
 cde5f2c Trac #15952: import statements with both absolute and (implicit)
 relative imports
 47403f6 Trac #15960: New function: FiniteStateMachine.set_coordinates
 cb44fb9 Trac #15849: Default ordering of States and Transitions in
 FiniteStateMachine
 0c33fd1 Trac #15848: Simplification for non-deterministic transducers via
 Moore's algorithm
 20c4867 Trac #15847: Do deepcopy + reset label in
 FiniteStateMachine.quotient instead of creating a new state
 6f65fec Trac #15966: Fix paralle_iter
 d242c97 Trac #15951: Fix last string exception for python3
 d59db5b Trac #12661: Include GMP 5.1.3 as an optional package
 f105b3c Trac #13174: Wrong documentation for methods @cached_method
 0c10a1b Trac #15937: Singular won't compile with latest Xcode (5.1, build
 5B130a)
 c8cf92e Trac #15979: Toric varieties can be tricked into accepting base
 rings that are not fields
 de53f11 Trac #14993: Upgrade matplotlib to 1.3.1
 21255d6 Trac #15918: Update FLINT to 2.4.2
 9acfe5e Trac #9524: Nasty bug with polynomial arithmetic and NTL contexts
 0fd9907 Trac #15815: rational preimages for projective morphisms returns
 incorrect points
 33eb663 Trac #13048: __floordiv__ does not work when dividing polynomials
 over QQbar by a constant
 82f6e16 Trac #15627: (disjoint) Union of graphs with multiple edges
 7ebf80e Trac #14844: Implement cluster algebras with universal coefficients
 07baf37 Trac #15910: Fix doctest in root_systems/coxeter_group.py when
 coxeter3 is install
 426c91d Trac #15888: CC - PARI: return t_REAL for real numbers
 cd7dff2 Trac #15890: EllipticCurve_number_field.is_isogenous() raises
 error for non-minimal models
 4d888e6 Trac #15895: Bug in Graph.subdivide_edge
 a28a9b1 Trac #15908: guava must be explicitly loaded
 c88356c Trac #15521: Deprecations: default LP variables will become real
 instead of nonnegative
 7890f8a Trac #15333: remove the imports of is_* from modules/all.py and
 structure/all.py
 807f60d Trac #15306: partial_fraction_decomposition over QQ[] wrong
 d694634 Trac #8573: prod(primes_first_n(64)).divisors() crashes
 955c1ab Trac #15599: Improve support for PARI series (t_SER)
 3464296 Trac #15843: Add reduced Burau representation, Alexander
 polynomial to Braid

  --
 You received this message because you are subscribed to the Google Groups
 sage-release group.
 To unsubscribe 

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

[Nathann Cohen]

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 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 http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Nathann Cohen]

 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 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 http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Nathann Cohen]

 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 will not have
Sage on my computer until it works.

Or maybe I should learn to use my head for a change ?...

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 to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Nathann Cohen]

(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 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 will not have
 Sage on my computer until it works.

 Or maybe I should learn to use my head for a change ?...

 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 to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Nathann Cohen]

 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

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 to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.
Found local metadata for scipy-0.12.0.p1
Attempting to download package scipy-0.12.0.p1
 Trying to download http://www.sagemath.org/packages/upstream/scipy/scipy-0.12.0.tar.bz2
[]
Checksum: d596b721a041b887613f225e07c27514a16a2e37 vs d596b721a041b887613f225e07c27514a16a2e37
scipy-0.12.0.p1

Setting up build directory for scipy-0.12.0.p1
Finished set up

Host system:
Linux grotte 3.0.0 #34 SMP Fri Aug 16 20:28:20 CEST 2013 x86_64 GNU/Linux

C compiler: gcc
C compiler version:
Using built-in specs.
COLLECT_GCC=/usr/bin/gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.8/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 4.8.2-16' --with-bugurl=file:///usr/share/doc/gcc-4.8/README.Bugs --enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.8 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.8 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --disable-libmudflap --enable-plugin --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64 --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.8-amd64 --with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc --enable-multiarch --with-arch-32=i586 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 4.8.2 (Debian 4.8.2-16) 

Note: CFLAGS, CXXFLAGS and SHAREDFLAGS are taken from distutils,
  so their current settings are ignored.
Traceback (most recent call last):
  File setup.py, line 165, in module
setup_package()
  File setup.py, line 145, in setup_package
from numpy.distutils.core import setup
  File /home/ncohen/.Sage/local/lib/python2.7/site-packages/numpy/__init__.py, line 137, in module
import add_newdocs
  File /home/ncohen/.Sage/local/lib/python2.7/site-packages/numpy/add_newdocs.py, line 9, in module
from numpy.lib import add_newdoc
  File /home/ncohen/.Sage/local/lib/python2.7/site-packages/numpy/lib/__init__.py, line 13, in module
from polynomial import *
  File /home/ncohen/.Sage/local/lib/python2.7/site-packages/numpy/lib/polynomial.py, line 17, in module
from numpy.linalg import eigvals, lstsq, inv
  File /home/ncohen/.Sage/local/lib/python2.7/site-packages/numpy/linalg/__init__.py, line 48, in module
from linalg import *
  File /home/ncohen/.Sage/local/lib/python2.7/site-packages/numpy/linalg/linalg.py, line 23, in module
from numpy.linalg import lapack_lite
ImportError: /home/ncohen/.Sage/local/lib/python2.7/site-packages/numpy/linalg/lapack_lite.so: undefined symbol: zungqr_
Error building scipy.

real	0m0.197s
user	0m0.044s
sys	0m0.012s

Error installing package scipy-0.12.0.p1

Please email sage-devel (http://groups.google.com/group/sage-devel)
explaining the problem and including the relevant part of the log file
  /home/ncohen/.Sage/logs/pkgs/scipy-0.12.0.p1.log
Describe your computer, operating system, etc.
If you want to try to fix the problem yourself, *don't* just cd to
/home/ncohen/.Sage/local/var/tmp/sage/build/scipy-0.12.0.p1 and type 'make' or whatever is appropriate.
Instead, the following commands setup all environment variables
correctly and load a subshell for you to debug the error:
  (cd '/home/ncohen/.Sage/local/var/tmp/sage/build/scipy-0.12.0.p1'  '/home/ncohen/.Sage/sage' --sh)
When you are done debugging, you can type exit to leave the 

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

[Nathann Cohen]

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.
Not building any matplotlib graphical backends.
patching file setupext.py
basedirlist is: ['/home/ncohen/.Sage/local']

BUILDING MATPLOTLIB
matplotlib: 1.2.1
python: 2.7.5 (default, Mar 10 2014, 14:13:21)  [GCC 4.8.2]
  platform: linux2

REQUIRED DEPENDENCIES
 numpy: no
* You must install numpy 1.4 or later to build
* matplotlib.
Error building matplotlib package.

real0m0.203s
user0m0.100s
sys 0m0.020s

Error installing package matplotlib-1.2.1


Somehow, when make fails and I re-type make immediately after, it seems 
that Sage does not do exactly what it failed to do before. But maybe that's 
normal because the previous make did compile some dependencies after all.

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 to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Nathann Cohen]

~/.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, the latter is probably
 easy
  since some packages can trip over headers that were left over by old /
  incomplete installs.
 
  The report above was obtained by erasing SAGE_ROOT, cloning the source
  from trac (not github as it was down for me, for some reason) then
  typing make. Nothing should have been left from the previous install.

 You have ~/.Sage/ mentioned...
 I've never seen this.

 I recall ~/.sage/ contents spoiling things during updates in some way,
 though.

 Dima


 --
 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 javascript:;.
 To post to this group, send email to 
 sage-release@googlegroups.comjavascript:;
 .
 Visit this group at http://groups.google.com/group/sage-release.
 For more options, visit https://groups.google.com/d/optout.


-- 
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 http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Nathann Cohen]

 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
branch into it, i.e. above develop.

Or you can do it in two times

git fetch trac u/ncohen/whatever:local_branch_name
look at local_branch_name to see if it is already based on the latest beta
git checkout local_branch_name # if no merge is needed, i.e. the
branch is up to date
git checkout -b local_updated_branch; git merge local_branch_name # if
the branch was too old

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 to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Nathann Cohen]

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 
/home/ncohen/.Sage/src/doc/output/doctrees/en/reference/sets/environment.pickle
cat: 
/home/ncohen/.Sage/src/doc/output/doctrees/en/reference/sets/environment.pickle:
No such file or directory

H O_O;;;

Nathann

On 6 March 2014 16:50, Dima Pasechnik dimp...@gmail.com wrote:
 On 2014-03-06, Volker Braun vbraun.n...@gmail.com wrote:
 I've never seen that error. The documentation is built at the end, so that
 means that Sage was built without errors. Can you try running the doctests?
 Perhaps some component is not working and somehow makes the
 numeric/environment.pickle invalid?

 If all fails, run make distclean  make...

 Tried make distclean  make, with no luck (!).
 I'm going to get the tarfile of beta3 and compare the sources,
 something must be fishy out there...


 --
 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 http://groups.google.com/group/sage-release.
 For more options, visit https://groups.google.com/groups/opt_out.

-- 
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 http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Nathann Cohen]

 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 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 http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Nathann Cohen]

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 working
on), and then git pull. And make, which is not always necessary
(when spkg were updated if I make no mistake).

If something happens, then it works. If you get an error message, share it :-D

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 to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/groups/opt_out.

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

[Nathann Cohen]

 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 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 http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/groups/opt_out.