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

Doing an incremental upgrade from 7.4.beta4, I was getting an error saying one of the eclib .so files was too short. So I did a force rebuild of eclib and another make, and now it is working. So I suspect it is due to #21474. Best, Travis On Friday, September 16, 2016 at 4:18:56 PM UTC-5, Volk

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

I think we should fix %attach before the next stable release, and I would also like %lprun fixed too. Best, Travis -- 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

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

This branch failed for me on linux at lcalc with what looks like linking errors. I reverted https://trac.sagemath.org/ticket/22840 and then I was able to build lcalc. Log file of the failed lcalc attached. Best, Travis On Sunday, April 23, 2017 at 9:04:12 AM UTC-5, Volker Braun wrote: > > As a

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

On Sunday, April 23, 2017 at 6:32:30 PM UTC-5, François wrote: > > Library ordering problem. What version of linux are we talking about? And > in particular what linker. > > > On 24/04/2017, at 11:29, tsc...@ucdavis.edu wrote: > > > > This branch failed for me on linux at lcalc with what loo

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

Does this help? ld -v GNU ld (GNU Binutils for Ubuntu) 2.26.1 Let me know what else I can get or do to help debug this. Best, Travis On Sunday, April 23, 2017 at 6:58:46 PM UTC-5, François wrote: > > > > On 24/04/2017, at 11:54, tsc...@ucdavis.edu wrote: > > > > > > > > On Sunday, April 2

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

FYI - Patchbots are also failing their build at lcalc. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this

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

I've been in the process of getting beta3 to build on Cygwin using --with-blas=atlas and Cygwin's GCC 6.3. Here is what I needed to do: - Python3 was not building due to a 3.4.5-struct.patch in #22666. Erik sent me an revised patch for this. - Pynac was not building, so I "reverted" 22764 by add

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

Another developer and I are also getting the failure in combinat/posets/posets.py. Best, Travis On Sunday, April 30, 2017 at 5:59:55 AM UTC-5, Emmanuel Charpentier wrote: > > On Debian testing runninng on Core I7 + 16 GB RAM, after fetching diffs > over 8.0.beta3, I get three errors : > >

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

I have graphviz installed as well. It does seem odd that graphviz would be the problem. My thought is more of that the DiGraph constructor is getting confused about the input. We might have to specify the input data to the DiGraph. Best, Travis On Thursday, May 4, 2017 at 9:14:28 AM UTC-5, St

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

I was not able to download the tarbal for normaliz from the mirrors (https://trac.sagemath.org/ticket/22684). Best, Travis -- 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 a

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

I was able to build on Cygwin64 with the blockers (and the ECM fix). However, sirocco (libsirocco-2.0.tar.gz) could not be found on the mirrors. Best, Travis -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and s

Re: [sage-release] Re: Sage 8.0.beta10 released

> > t seems that this happens on several machines: > > > > Error installing package gf2x-1.1.p2 > > > > See for example > > > > > https://patchbot.sagemath.org/log/0/LinuxMint/18.1/x86_64/4.4.0-59-generic/rk02-math/2017-06-11%2018:40:38?short > >

Re: [sage-release] Re: Sage 8.0.beta10 released

> Given what I see, you only get this when you set SAGE_TUNE_GF2X=full. > Unsetting SAGE_TUNE_GF2X (which is the default) or putting it to no > will work. At least it looks to me like SAGE_TUNE_GF2X is set to full > from the log, let me know if this assumption is wrong. > > I didn't set SAGE_

Re: [sage-release] Re: Sage 8.0.beta10 released

On Sunday, June 11, 2017 at 11:45:57 PM UTC-5, François wrote: > > On 12/06/17 16:20, tsc...@ucdavis.edu wrote: > > > > Given what I see, you only get this when you set > SAGE_TUNE_GF2X=full. > > Unsetting SAGE_TUNE_GF2X (which is the default) or putting it to no > > will work.

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

> > > Indeed. > > sage -t --long --warn-long 75.4 src/sage/rings/function_field/ > function_field.py > ** > File "src/sage/rings/function_field/function_field.py", line 69, in sage. > rings.function_field.function_field > Warning

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

Hey Simon, > > On 2017-08-17, tsc...@ucdavis.edu > wrote: > > about half of the time is in > > > > {method 'map_coefficients' of > > 'sage.rings.polynomial.polynomial_element.Polynomial' objects} > > > > and subfunction calls. I would say a better solution would include > > improving Poly

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

Addendum: _.__mro__ (, , , , , , , ... -- 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, s

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

Hey Simon, Sorry for my delay, I was on a transpacific flight and recovering from that. > > On 2017-08-17, tsc...@ucdavis.edu > wrote: > >> What kind of polynomials is involved in that test? libsingular? > > > > I believe they are the generic polynomials: > > > > sage: type(M.some_eleme

[sage-release] Re: Sage 8.1.rc4 released

What about https://trac.sagemath.org/ticket/24297? I don't know if this problem materializes on other platforms, but I know Erik will be happy with all tests passing on Cygwin. ;) Best, Travis PS - I saw that https://trac.sagemath.org/ticket/24085 was not closed. On Saturday, December 2, 2017

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

Built without any problem. However, I am no longer able to run doctests on my system (Ubuntu 17.04) with 8.2.beta8: travis@apricot:~/sage-build$ ./sage -btp src/sage/combinat/partitions.pyx cd . && export\ SAGE_ROOT=/doesnotexist

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

> Built without any problem. However, I am no longer able to run doctests on > my system (Ubuntu 17.04) with 8.2.beta8: > > Actually, this seems to be an issue with system as I get a similar error with an older version of Sage. I will instead most the post to sage-devel. Sorry for the noise he

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

I got a failure while building m4ri on an incremental build from 8.3.rc2. Log attached. This succeeded on doing make again. -- 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

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

On Monday, August 6, 2018 at 8:17:08 AM UTC+10, tsc...@ucdavis.edu wrote: > > On another incremental build from 8.3.rc1, I am getting a few things like > this appearing in a few logs: > > [snip] > > So the packages seem to be building. It is just uninstalling the old one is > failing. Logs a

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

I got a report of someone getting an invalid checksum using the configure-280.tar.gz on one of the mirrors (using a fresh git clone): Fastest mirror: http://www.mirrorservice.org/sites/www.sagemath.org/ http: //www.mirrorservice.org/sites/www.sagemath.org/spkg/upstream/configure/configure-280.tar

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

I also sampled a few of the other mirrors and got the same resulting md5sum and checksum, which is different from the one in build/pkgs/configure/checksums.ini. Best, Travis -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from

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

I believe there is a Heisenbug in src/sage/rings/function_field/ideal.py. Here is a specific test that can sometimes fail: sage: K. = FunctionField(GF(3^2)); R. = K[] sage: F. = K.extension(t^3 + t^2 - x^4) sage: Oinf = F.maximal_order_infinite() sage: I = Oinf.ideal(1/y) sage: I.factor() # Thi

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

On Wednesday, October 3, 2018 at 7:35:08 PM UTC+10, Kwankyu Lee wrote: > > > > On Wednesday, October 3, 2018 at 3:14:32 PM UTC+9, tsc...@ucdavis.edu > wrote: >> >> I believe there is a Heisenbug in src/sage/rings/function_field/ideal.py. >> Here is a specific test that can sometimes fail: >> >>