Re: [sage-release] Releasing Sage 6.0

On 2013-12-19 15:08, Marco Streng wrote: New machine, new problem. On a mac recently upgraded from 10.8 to 10.9, after downloading and extracting the tarball and typing make, I get the following problem (both sage 5.13 and sage 6.0). sed: /usr/include/sys/cdefs.h: No such file or directory This

[sage-release] Re: Sage 6.1 released

for various (maybe all?) tickets from sage-5.13.beta5 appearing in the changelog, how did that happen? For example, there is (merged in 5.13.beta5) commit 84c206a4d2b0f6fb80ffc14fcb16f1650c85e646 Author: Jeroen Demeyer jdeme...@cage.ugent.be Date: Mon Nov 25 22:57:34 2013 +0100 Trac #15453: Wrap

[sage-release] 6.1.1 release for the sagenb fix?

It has been proposed to make a Sage 6.1.1 release to fix the broken LaTeX in the notebook (#15778). I think that is a good suggestion, what does the release manager think? Jeroen. -- You received this message because you are subscribed to the Google Groups sage-release group. To unsubscribe

[sage-release] Sage 6.1.1 release notes

See http://boxen.math.washington.edu/home/jdemeyer/sage-git/logs/sage-6.1.1.txt -- 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.2.beta2 released

On 2014-02-27 19:19, strogdon wrote: gcc -pthread -c -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -I. -IInclude -I./Include -fPIC -DPy_BUILD_CORE \ -DSVNVERSION=\`LC_ALL=C svnversion .`\ \ -DHGVERSION=\`LC_ALL=C hg id -i .`\ \ -DHGTAG=\`LC_ALL=C hg id -t .`\

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

On 2014-03-05 15:33, Dima Pasechnik wrote: something has happened, surely, but at the end I still see beta2 banner, even though git log says that the latest commit is Works for me. What does ls -l src/bin/sage-banner local/bin/sage-banner say? -- You received this message because you are

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

After upgrading to sage-6.2.beta4, I get sage -t --long src/sage/structure/sage_object.pyx ** File src/sage/structure/sage_object.pyx, line 194, in sage.structure.sage_object.SageObject._ascii_art_ Failed example: shell =

Re: [sage-release] Sage 6.3 released

On 2014-08-15 07:25, kcrisman wrote: IMHO we should just give up on correcting naming errors. If you can't decide on how to write your own name then I would call it a feature that each novel spelling is a first contribution That's silly, especially because often someone else

[sage-release] How are binaries being built?

Are all Sage binaries still built with SAGE_FAT_BINARY=yes and SAGE_INSTALL_GCC=yes? I am asking because of http://trac.sagemath.org/ticket/8049#comment:11 Apparently, we are no longer shipping libgfortran with all binaries. -- You received this message because you are subscribed to the Google

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

On 2014-09-27 20:53, Jean-Pierre Flori wrote: It's the only simple way from my point of view when you want to build on a machine without internet access. +1 I have also used it for this reason. -- You received this message because you are subscribed to the Google Groups sage-release group.

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

On 2014-09-28 14:46, Volker Braun wrote: This is some more fallout from #16858. Jeroen, do you already have a followup ticket for numerical noise? http://trac.sagemath.org/ticket/17063 -- You received this message because you are subscribed to the Google Groups sage-release group. To

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

On 2014-09-28 22:03, Volker Braun wrote: The threshold is a certain fraction of the total doctest time, so it takes the relative speed of computers into account. But it wrongly assumes that doctest time scales linearly with computer speed. -- You received this message because you are

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

I get doctest failures in sagenb: http://trac.sagemath.org/ticket/17268 -- 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.

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

On 2014-10-30 15:12, Volker Braun wrote: * SageNB now can do 3d plots without Java, so it is usable again in chrome. For me, this upgrade breaks 3D graphics to some extent: When issuing the command cube(viewer=jmol) using java version 1.6.0_31 OpenJDK Runtime Environment (IcedTea6 1.13.3)

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

On 2014-11-01 11:04, Francois Bissey wrote: That means you need java 1.7 at the minimum. Is there any chance this could be detected and a better error message given? Surely, I'm not the only one who would have this problem. -- You received this message because you are subscribed to the Google

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

On 2014-11-04 22:02, Jean-Pierre Flori wrote: I think its the way we treat tolerance which changed It's true that the way we treat tolerance has changed, see http://trac.sagemath.org/ticket/16889 But that's not the reason for the failed tests, the reason is

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

On 2014-11-04 22:31, Harald Schilly wrote: On Tue, Nov 4, 2014 at 10:24 PM, Jeroen Demeyer jdeme...@cage.ugent.be wrote: In my opinion, doctest output should be the actual output of a Sage run somewhere and not artificially be adjusted Well, if there are different outputs for the same input

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

On 2014-11-14 16:09, kcrisman wrote: Both the develop and master git branch have been updated to Sage 6.4! Hurrah! Jeroen or whoever, just get me the auto-generated release notes thingie and I'll give it the once-over on name duplicates etc. so that can go up too. This is the

Re: [sage-release] Re: Sage 6.4 on Ubuntu 14.04 LTS (ipython notebook and ssl)

On 2014-11-19 17:28, kcrisman wrote: Please run it again Done. -- 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

Re: [sage-release] Sage 6.4.1 released

On 2014-11-25 06:54, Francois Bissey wrote: It would be easier if you were producing a log while building at -j1 Absolutely. It's very hard to read logs of parallel builds since the actual error could be essentially anywhere in the log. -- You received this message because you are subscribed

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

On 2014-12-04 21:03, François Bissey wrote: gcc 4.0.1 is definitely too old to build 4.9.x. Are you sure about this statement or are you just guessing? -- 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.5.beta3 released

On 2014-12-18 21:10, John H Palmieri wrote: sage -t --warn-long 35.1 src/sage/libs/singular/polynomial.pyx ** File src/sage/libs/singular/polynomial.pyx, line 166, in

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

On 2015-02-09 17:02, kcrisman wrote: Would a build halt if one didn't have TeX? No. It would just fail to build the PARI docs, no problem. -- You received this message because you are subscribed to the Google Groups sage-release group. To unsubscribe from this group and stop receiving emails

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

On 2015-03-13 18:10, William Stein wrote: On 64-bit Ubuntu 14.10, make ptestlong yields one doctest failure. Since it's something that I think absolutely anybody who ran the doctest on any system would see, I guess that means that the buildbots and/or other tests you run before making a beta

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

On 2015-03-13 18:37, William Stein wrote: M = self._new_uninitialized_matrix(self._ncols,B._ncols) It seems that your machine is extremely slow: Sage is still constructing the matrix to contain the answer and the AlarmInterrupt happens in a different block of code, which has the

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

This is the hard part: well-defined subset of the optional packages and tests Once you fill this in, the testing can trivially be done on the buildbot. -- 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] Typos in changelog for 6.5

On 2015-02-27 11:13, Nicolas M. Thiery wrote: Dear changelog writers, Here is a report from a colleague on the changelog for Sage 6.5. For the record, I have fixed the typo for Nicolas Thierry on the relevant ticket (#17424), and the other typos seem to be already fixed on trac. I am

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

I get a doctest failure and created http://trac.sagemath.org/ticket/17672 sage -t src/sage/combinat/designs/orthogonal_arrays.py ** File src/sage/combinat/designs/orthogonal_arrays.py, line 1191, in

Re: [sage-release] Sage 6.6 released

On 2015-04-21 09:29, Justin C. Walker wrote: I just noticed that (on my 10.6.8 system), sage-banner in 6.6 refers to 6.6.beta3! I double-checked, and the tarball, from which I installed 6.6, has the correct banner. Anyone have a clue how the wrong banner crept into my 6.6 tree? Did you

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

On 2015-04-23 21:47, Emmanuel Charpentier wrote: Or, more precisely, this tarball + any standard package tarball installed in upstream/ The Sage source tarball should contain all tarballs for standard packages in upstream/. If this is not the case, that's a bug. Jeroen. -- You received this

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

Did you run make ptestlong or make ptestall? make ptestlong finishes with 220 files having failing doctests File ptestall.log available on request (it is 20M). -- You received this message because you are subscribed to the Google Groups sage-release group. To unsubscribe from this group

Re: [sage-release] Re: Error building sagenb

On 2015-04-07 13:31, Vincent Delecroix wrote: sage -f pip is not enough. Python itself must be compiled with ssl support. So after installing libssl-dev you need to do sage -f python make sage -f pip Since pip depends on Python, the following should be enough: sage -f python make --

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

On 2015-06-12 15:19, kcrisman wrote: If I understand correctly, this version (and perhaps some previous ones) have fixed the optional business. Not yet, wait for Sage 6.8.beta4 -- You received this message because you are subscribed to the Google Groups sage-release group. To unsubscribe from

[sage-release] Sage 6.6 and 6.7 changelogs

- James Propp [first contribution] - Jan Keitel - Jean-Philippe Labbé - Jean-Pierre Flori - Jernej Azarija - Jeroen Demeyer - Jessica Striker - Johan Bosman - Johan Sebastian Rosenkilde Nielsen - John Cremona - John Palmieri - Jori Mäntysalo - Josh Swanson [first

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

See http://trac.sagemath.org/ticket/18535 -- 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

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

On 2015-07-17 12:50, Dima Pasechnik wrote: anyhow, there has to be a way to purge things related to such (non)packages from a Sage install. One must have an option of removing that spurrious blah from whatever record it was recorded in... rm -rf logs -- You received this message because you

Re: [sage-release] Sage 6.10.beta3 releasaed

These tickets are not closed on Trac: On 2015-11-06 01:02, Volker Braun wrote: 25e78b9 Trac #19524: fixing a few bad trac roles, and adding some 9abaac4 Trac #19498: Random failure in Integers(15).fraction_field() -- You received this message because you are subscribed to the Google Groups

Re: [sage-release] Sage 6.9 released

On 2015-10-14 17:25, kcrisman wrote: Still annoying: builds fine from scratch and passes all tests. BUT then: $ ./sage -bdist Sage version 6.9, release date 2015-10-10 rm -rf config configure build/make/Makefile-auto.in Attempting to download package configure-119.tar.gz from mirrors Context

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

On 2015-10-08 08:10, Clemens Heuberger wrote: make; ./sage -i ccache; ./sage -b; make Why so complicated? It's kind of strange since you install ccache *after* you build all of Sage, which makes ccache pointless. It's better to run SAGE_INSTALL_CCACHE=yes make but none of this should affect

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

On 2015-10-05 22:56, Eric Gourgoulhon wrote: But the problem is still there: ./sage -n jupyter results in the same error message. OK, first verify that you're on the correct Sage version: $ cat VERSION.txt This should output something like Sage version 6.9.rc1, released 2015-10-01 Next,

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

On 2015-09-09 05:58, Anne Schilling wrote: On Tuesday, September 8, 2015 at 1:46:54 PM UTC-7, Volker Braun wrote: does a "make distclean && make" fix it? You have both gap-database and gap_database, that can't be good. Probably you are running into one of the many razor-sharp edges

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

On 2015-09-17 22:11, Volker Braun wrote: is it reproducible? No, I just got it once. Since that doctest was changed in this beta, I assume the failure was genuine. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this

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

On 2015-09-28 22:05, William Stein wrote: Agreed. Jereon want to do something about this? It's reported upstream to PARI. -- 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

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

On 2015-09-28 20:00, William Stein wrote: In Sage-6.7 this library (which is *pure python*) works well: https://github.com/datasift In Sage-6.9.beta6 (for me) this library crashes with the following weird traceback. Any ideas? Should be fixed upstream and in Sage at

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

I can confirm that there is indeed a problem with docbuilding. When looking at the patchbot, I saw a similar problem. On 2015-09-26 09:58, Clemens Heuberger wrote: ubuntu 14.04, 64 bit, 4 GB RAM: make -j4 ran out of memory while building documentation, last line in logfile: [tutorial ]

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

On 2015-09-26 14:48, Volker Braun wrote: Though afaik our docs say that you need 2gb per process, so you were quite a bit below that. It could just be slightly different order of execution that blows things up now even though memory consumption didn't increase. The question is: did it really

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

On 2015-10-05 09:46, kcrisman wrote: That's not good either. Also, just setting the env var to blank didn't seem to negate it, currently trying with unsetting it. That's probably my ignorance of bash, though. Aagh, it's *still* trying to download it, even though the env var

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

Got the same error (not reproducible) on a different machine (Linux x86_64) On 2015-09-17 21:59, Jeroen Demeyer wrote: sage -t --long src/sage/categories/fields.py ** File "src/sage/categories/fields.py"

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

Right. You bug report actually shows 3 independent bugs: * GCC shouldn't be downloaded in the first place * The failed download of the mirror_list doesn't give an error message * The blank line without failed packages The first one is fixed at #19347. The third one was fixed at #18731, but the

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

On 2015-12-07 19:05, Daniel Krenn wrote: RuntimeError: In order to initialize the database, /local/dakrenn/sage/6.10.beta7/local/share/conway_polynomials/conway_polynomials.sobj must exist. This might be a missing dependency. I will check it. -- You received this message because you are

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

Since we are apparently in the "rc" phase, I created a 6.11 milestone. I moved #19616 to the new milestone since a sagenb upgrade is something which needs proper beta testing. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe

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

On 2015-12-12 18:42, Emmanuel Charpentier wrote: It seems that the build system can build conway_polynomials, but fails to download it if not present, and (worse), fails *silently* Are you seeing any evidence that the build of conway_polynomials failed? Most likely, the download/build of

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

On 2015-12-16 01:01, Dima Pasechnik wrote: this was a result of b2094a8a (Jeroen Demeyer 2015-11-18 15:53:34 +0100 1402) which did change description = G._gap_().StructureDescription().__str__() to description = str(G._gap_().StructureDescription()) but these calls

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

On 2016-01-08 08:04, Henri Girard wrote: I have compiled sage-7.0 beta 2 allright. But beta 3 doesn't compile. Log files please... -- 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

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

On 2015-12-30 16:59, Volker Braun wrote: As mentioned before, there are no incremental updates from 6.x. There are even no incremental updates from 7.0.beta0 or 7.0.beta1: you need "make distclean" again. -- You received this message because you are subscribed to the Google Groups

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

On 2015-12-22 22:13, Volker Braun wrote: You need to compile from scratch Could you elaborate a bit on why this is the case. I tried not doing "make distclean" and I immediately got Traceback (most recent call last): File "/usr/local/src/sage-config/build/bin/sage-download-file", line 25,

Re: [sage-release] Sage 6.10 released

On 2015-12-18 20:58, Volker Braun wrote: Does anybody know a way to programmatically post to sage-release? https://docs.python.org/2/library/email.html#module-email https://docs.python.org/2/library/smtplib.html#module-smtplib -- You received this message because you are subscribed to the

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

This worries me: missing cimport in module '.': ./sage/rings/rational.pxd missing cimport in module '.': sage/rings/rational.pxd It might mean that some dependencies are not correctly picked up by Cython. -- You received this message because you are subscribed to the Google Groups

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

On 2016-06-05 19:16, Volker Braun wrote: 8c68331 Trac #20721: Unpack all upstream tarballs into 'src' directory Is it possible that this made uncompressing a lot slower? On one machine, the GCC tarball is taking already 16 minutes CPU time to uncompress... -- You received this message

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

On 2016-01-14 07:32, Nathann Cohen wrote: Hello everybody, For the latest beta releases, each time 'git pull && make' produced the following message: ... config.status: /home/ncohen/.Sage/local/lib64 is not a symlink, see Trac #19782 config.status: error: Cannot perform

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

On 2016-01-14 09:15, Volker Braun wrote: After you run "make distclean & make", is lib64 a symlink? If its not then its a bug. I guess you mean "make distclean && make" (double ampersand) -- You received this message because you are subscribed to the Google Groups "sage-release" group. To

Re: [sage-release] 7.1.beta1 released

cliquer-1.21.p3 Setting up build directory for cliquer-1.21.p3 Finished set up [...] Applying patches... Configuring... ./spkg-install:

Re: [sage-release] 7.1.beta1 released

This problem was caused by running sage-fix-pkg-checksums on 7.1.beta0 with a newer version of cliquer in upstream/ So, it's perhaps not really a bug but it's annoying that there are 2 cliquer tarballs in upstream/ with the same version number. I think the version number of cliquer should

Re: [sage-release] 7.1.beta1 released

On 2016-01-30 06:34, Dima Pasechnik wrote: 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... -- You received this message

Re: [sage-release] 7.1.beta1 released

On 2016-01-30 11:45, Volker Braun wrote: The mapping package <-> tarball is uniquely determined by checksums.ini and package_version.txt, no guessing required. But the checksums.ini file is *generated* by sage-fix-pkg-checksums. So this cannot really work. -- You received this message

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

On 2016-01-24 10:04, Nathann Cohen wrote: 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. So you're not running "make distclean" at all? Did

Re: [sage-release] Sage 7.0 virtual appliance

On 2016-01-26 16:04, Volker Braun wrote: it also gives you easy access to a shell inside the VM without cryptic key combinations. Is this using terminado (which we currently don't ship with Sage, but perhaps we should)? -- You received this message because you are subscribed to the Google

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

On 2016-01-24 16:01, Dima Pasechnik wrote: I am sure if we were electing the best Sage bugs, you won't abstain... I vote for http://trac.sagemath.org/ticket/10609 -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group

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

On 2016-02-27 11:48, Daniel Krenn wrote: Cloned into new directory, installation with "make -j4" hang. Last line printed was Finished installing singular-3.1.7p1.p0.spkg (didn't continue for at least an hour or so). Are you sure it did hang? On some machines, ATLAS can take a long time to

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

On 2016-04-12 18:21, kcrisman wrote: In the meantime, are the only ways to get my upgrade to finish doing "make -k" Can you try make openssl-clean # mark openssl as not installed touch configure# force reconfiguration make # the usual build command or remove all openssl

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

On 2016-04-12 18:21, kcrisman wrote: Sure, just one moment... http://www.math-cs.gordon.edu/~kcrisman/openssl-1.0.2g.log Seems to be a known issue: https://mta.openssl.org/pipermail/openssl-dev/2016-March/005605.html with a known fix:

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

On 2016-04-12 17:46, kcrisman wrote: I'm having trouble upgrading due to http://trac.sagemath.org/ticket/20143 - apparently once you've installed an optional package you have to keep it installed. I can't figure out easily (without using some git skills I don't have time to look up right now)

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

On 2016-03-07 13:35, Jean-Philippe Labbé wrote: A colleague has a error in the compilation of Sage 7.0: First of all, make sure that this colleague downloaded the *source* tarball of Sage if he wanted to compile from source. Second, please send the contents of the files

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

On 2016-03-08 13:59, pevdeco...@gmail.com wrote: Dear Jeroen, The tarball I downloaded was source. Below are the last bits of my log files. Thanks, but I have no idea what happened. Just to be sure, could you try make distclean; make and see if that changed anything? -- You received this

[sage-release] Reverting blacklisting of GCC 4.8 (#20231)

Hello Volker, would it be okay for you to revert Trac #20231 in Sage 7.2? The reason for blacklisting GCC 4.8 was to support #20226, but that's not going to be merged in Sage 7.2. So maybe it's best to still support GCC 4.8 in Sage 7.2 (maybe with a deprecation warning in configure.ac).

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

This now crashes Sage: sage: alarm(1) -- 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

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

On 2016-08-12 12:10, Jeroen Demeyer wrote: This now crashes Sage: sage: alarm(1) Reported upstream: https://github.com/ipython/ipython/pull/9867 -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this grou

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

On 2017-02-04 10:34, Jean-Philippe Labbé wrote: Before that it was building the doc, and before that installing the jupyter client. Logs please... ignore the "python" thing, it's most likely not the reason for the failure. -- You received this message because you are subscribed to the

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

This is 3 doctest runs concatenated. I will just look at the last one (if you remember for next time: better just post the log of one run). Those issues are because of pip. Did you manually upgrade pip in that installation? -- You received this message because you are subscribed to the

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

On 2017-01-24 10:54, John Cremona wrote: Quite possibly. If I use pip to install something and it tells me that my pip os out of date I usually obey instructions and update it. Should I not have done? Depends. If you want all doctests to pass: no, you should not have done that. And what

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

On 2017-01-24 13:09, John Cremona wrote: OK, I am doing that and then make and make ptestlong, and we'll see what happens no, same errors. Minor comment: if you are going to run "make ptestlong" anyway, there is no point in running "make" separately. In other words, "make && make

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

On sage4, I get one failure: sage -t --long src/sage/symbolic/expression.pyx ** File "src/sage/symbolic/expression.pyx", line 9627, in sage.symbolic.expression.Expression.to_gamma Failed example: binomial(m,n).to_gamma()

Re: [sage-release] Re: Why is gcc built?

On 2017-02-22 14:50, Simon King wrote: Hi Jeroen, On 2017-02-22, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote: The reason that I asked you to run ./configure is just to answer the *why* question. Since I am not patient enough to wait till the build has finished: Shouldn't the

Re: [sage-release] Re: Why is gcc built?

On 2017-02-24 10:31, Erik Bray wrote: On Thu, Feb 23, 2017 at 5:26 PM, Dima Pasechnik wrote: one can still have something like: --with-everything # build everything --with-everythingneeded # build missing etc... to encode the most usual cases. Yes, I think this goes

Re: [sage-release] Re: Why is gcc built?

Sorry, but I do not like your idea. I don't feel like being forced to run ./configure --with-gcc --with-zlib --with-mpir --with-r --with-glpk --with-git --with-ppl --with-pari --with-libgap ... # 80 packages more just because I don't have those packages on my system. -- You received this

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

This is a bug in Pynac, see * https://trac.sagemath.org/ticket/22421 * https://github.com/pynac/pynac/issues/231 On 2017-02-22 08:16, Jeroen Demeyer wrote: sage -t --long src/sage/symbolic/expression.pyx ** File "src

Re: [sage-release] Re: Why is gcc built?

Looks fine to me... On 2017-02-22 18:31, Simon King wrote: configure:5266: checking for gfortran configure:5282: found /usr/bin/gfortran configure:5293: result: gfortran configure:5319: checking for Fortran compiler version configure:5328: gfortran --version >&5 GNU Fortran (Ubuntu

Re: [sage-release] Re: Why is gcc built?

On 2017-02-22 16:50, Simon King wrote: In other words, I still don't see why gcc should be rebuilt (unless the developer's manual needs update). Can you post the config.log file? -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe

Re: [sage-release] Re: Why is gcc built?

On 2017-02-22 16:50, Simon King wrote: So, it seems that the problem lies in Fortran compiler, right? But I did do sudo apt-get install gcc-fortran following the advice of the manual. To verify, run gfortran --version -- You received this message because you are subscribed to the Google

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

sage -t src/sage/modular/pollack_stevens/padic_lseries.py ** File "src/sage/modular/pollack_stevens/padic_lseries.py", line 199, in sage.modular.pollack_stevens.padic_lseries.pAdicLseries.__ne__ Failed example: L != L

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

On 2017-01-23 17:50, John Cremona wrote: ptestlong.log available on request. Yes please. -- 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 7.6.beta3 released

On 2017-02-13 14:32, Sébastien Labbé wrote: On Ubuntu 16.06, make ptestlong with MAKE="make j6" had one failing test which I can not reproduce: See https://trac.sagemath.org/ticket/15585 -- You received this message because you are subscribed to the Google Groups "sage-release" group. To

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

On 2017-02-26 19:49, Volker Braun wrote: 0dff673 Trac #22177: Implement SVG plotting in pari_jupyter This tarball is not mirrored: [pari_jupyter-1.2.2] ERROR [transfer|run:135]: [Errno 404] Not Found: '//sagepad.org/spkg/upstream/pari_jupyter/pari_jupyter-1.2.2.tar.bz2' [pari_jupyter-1.2.2]

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

On 2016-09-02 08:47, Volker Braun wrote: f4c9a93 Trac #21256: Upgrade and fix ipywidgets This breaks the sage4 patchbot because of https://github.com/jupyter/jupyter_core/issues/87 -- You received this message because you are subscribed to the Google Groups "sage-release" group. To

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

On 2016-08-31 17:03, Ralf Stephan wrote: Does anyone else get these segfaults in the kernel log? I think that's pretty normal. Some doctests intentionally segfault. And maybe some build tests also do that. -- You received this message because you are subscribed to the Google Groups

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

On 2016-08-27 01:08, Johan S. H. Rosenkilde wrote: I had to do make distclean: the Pari upgrade complained. Do you have more details? -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails

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

On 2016-11-07 11:43, Emmanuel Charpentier wrote: and read the logs I've attached. It's a long thread with many posts of you, I am getting lost. Can you please reboot the discussion at #21812? And attach a log file showing why you think that #21812 does not work. -- You received this

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

On 2016-11-07 08:31, Emmanuel Charpentier wrote: Well, a serial recompilation with pip 8.x works (see enclosed logs). That test failure is #15585 which is totally unrelated to pip. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To

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

On 2016-10-19 20:00, Emmanuel Charpentier wrote: After upodating my "develop" branch to 7.4 and merging it with my local branch (was 7.4beta6, and contained trac#20523 (R.3.3.1), trac#21231 (enhancemens to fricas interface) and trac#21622 (pari/perl)), I get a bunch of compilation problems :

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

I have a very strange problem: sage -t src/sage/ext/memory.pyx ** File "src/sage/ext/memory.pyx", line 9, in sage.ext.memory Failed example: 2^(2^63-2) Expected: Traceback (most recent call last): ...

  1   2   >