Re: [sage-devel] Re: How much do we support optional packages.

On 2017-09-13 21:56, rjf wrote: Just because a package builds, loads, and passes some tests doesn't mean that it also includes some security attack. Does anyone care about / have any useful thoughts about /. that? What would security even mean for a mathematics program? Sage is not meant for

Re: [sage-devel] Re: Sage 8.0 Build Error on MacOS, [mpir-3.0.0.p0] Error building MPIR.

I'm having the same issue. To get MPIR to compile I had to remove all three of mpn/x86_64/skylake/avx/addmul_1.asm mpn/x86_64/skylake/avx/mul_basecase.asm mpn/x86_64/skylake/avx/sqr_basecase.asm Thanks for working on this, Bill. Best, Robert On Wednesday, 6 September 2017 21:44:21 UTC-4,

[sage-devel] Re: How much do we support optional packages.

Just because a package builds, loads, and passes some tests doesn't mean that it also includes some security attack. Does anyone care about / have any useful thoughts about /. that? Sage includes Maxima and Lisp, which generally provides access to system routines, for example. RJF On

Re: [sage-devel] Trouble while compiling sage---- compiling ends during plot3d

Do you mean https://github.com/sagemath/binary-pkg ? it is only needed in order to be able to make a binary installer. you do not need it to build Sage in place. 4Gb should do. You can also only do make build to skip building docs (they are online anyway) -- You received this message

Re: [sage-devel] How much do we support optional packages.

On 2017-09-13 15:28, Maarten Derickx wrote: So the main questions: do we consider an optional package not building, not passing it's own testsuite or causing sage to have doctest failures a bug? Yes. In the other thread it was mentioned that patchbot failures should be considered blocker

Re: [sage-devel] Trouble while compiling sage---- compiling ends during plot3d

I tried to build the binaries locally but I ran into another error. This time I believe it was during the building of the documentation (is there a way to avoid this using the binary package builder?). At that point I decided it was in my best interest to shell out $7/month for CoCalc.. The

Re: [sage-devel] Re: How much do we support optional packages.

Sided note: as far as I know, these pip packages are not involved in any doctest. On 13/09/2017 16:42, Maarten Derickx wrote: And related to this, how much do we support pip packages. With this I don't mean any random pip package that happens to be on pypi, but just the ones that are returned

[sage-devel] Re: How much do we support optional packages.

And related to this, how much do we support pip packages. With this I don't mean any random pip package that happens to be on pypi, but just the ones that are returned by: sage -optional that happen to be pip packages. At the moment: ['beautifulsoup', 'biopython', 'brian', 'guppy',

[sage-devel] How much do we support optional packages.

Hi Dear fellow sage-developers, The question in the subject is related to the discussion in the Patchbot failures metaticket thread. I remember that I read (somewhere a long time ago so my memory might be off) that

Re: [sage-devel] Trouble while compiling sage---- compiling ends during plot3d

On Monday, September 4, 2017 at 9:16:49 AM UTC+2, Jeroen Demeyer wrote: > > There is the message "Killed" which can normally only happen if > something external kills Sage. I had exactly this "Killed" yesterday and could resolve it by deleting my $HOME/.sage folder. Regards, -- You received

Re: [sage-devel] Patchbot failures metaticket

Hi Vincent, Thanks for pointing out the point of view from a patchbot maintainer, my statement "I think a complete burden is highly exaggerated" was made from my perspective as a developer not knowing how this looks from a patchbot maintainer point of view. And I can see that having to deal

Re: [sage-devel] Trouble while compiling sage---- compiling ends during plot3d

Are you sure? The command "make build" skips the building of the documentation. So you should not be able to get this error which happens during the building of documentation. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from

Re: [sage-devel] Re: git trac is down ?

a reboot of the trac host fixed the problem. On Wednesday, September 13, 2017 at 8:31:11 AM UTC+1, David Roe wrote: > > I haven't been able to find a log and I need to go to sleep. Dima should > have access though > David > > On Wed, Sep 13, 2017 at 3:17 AM, Vincent Delecroix

[sage-devel] trac rebooted, git:// works now

See the subject. I did a reboot, as after logging in I saw "reboot required" MOTD. And it did bring the git:// URLs back to live, so bots must be happy now. Are there any further manual actions to do on the trac host after the reboot? Cheers, Dima -- You received this message because you are

Re: [sage-devel] Trouble while compiling sage---- compiling ends during plot3d

Hi, i am not sure it is completely related, but i also get a recurrent failure while building the doc, at the same position (plot3d). I am trying to run a 32bit patchbot within a VM (which might be the common point). You can get the log at:

Re: [sage-devel] Re: git trac is down ?

I haven't been able to find a log and I need to go to sleep. Dima should have access though David On Wed, Sep 13, 2017 at 3:17 AM, Vincent Delecroix < 20100.delecr...@gmail.com> wrote: > > > On 13/09/2017 09:17, David Roe wrote: > >> On Wed, Sep 13, 2017 at 3:10 AM, Dima Pasechnik

Re: [sage-devel] Re: git trac is down ?

On 13/09/2017 09:17, David Roe wrote: On Wed, Sep 13, 2017 at 3:10 AM, Dima Pasechnik wrote: As I mentioned, this is not under our control which ports are blocked on GCE hosts, and which are not. I think it is (see

Re: [sage-devel] Re: git trac is down ?

On Wed, Sep 13, 2017 at 3:10 AM, Dima Pasechnik wrote: > As I mentioned, this is not under our control which ports are blocked on > GCE hosts, and which are not. > I think it is (see https://cloud.google.com/compute/docs/vpc/using-firewalls), but I'm still confused. If you

Re: [sage-devel] Re: git trac is down ?

As I mentioned, this is not under our control which ports are blocked on GCE hosts, and which are not. Why don't we merely retarget bots to pull branches from github? -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this

Re: [sage-devel] Re: git trac is down ?

On 13/09/2017 08:58, Volker Braun wrote: On Tuesday, September 12, 2017 at 10:00:32 PM UTC+2, Erik Bray wrote: It has *never* supported read-only access via HTTP or HTTPS. Afaik we have always supported git:// access and our documentation explicitly recommends setting it up that way; Its

Re: [sage-devel] Re: git trac is down ?

On Tuesday, September 12, 2017 at 10:00:32 PM UTC+2, Erik Bray wrote: > > It has *never* supported read-only access via HTTP or HTTPS. > Afaik we have always supported git:// access and our documentation explicitly recommends setting it up that way; Its also how the git-trac script configures

Re: [sage-devel] Re: git trac is down ?

On 13/09/2017 08:24, Vincent Delecroix wrote: On 12/09/2017 22:00, Erik Bray wrote: On Tue, Sep 12, 2017 at 9:59 PM, Dima Pasechnik wrote: On Tuesday, September 12, 2017 at 7:35:11 PM UTC+1, vdelecroix wrote: On 12/09/2017 20:32, Dima Pasechnik wrote: ah, right, do

Re: [sage-devel] Re: git trac is down ?

On 12/09/2017 22:00, Erik Bray wrote: On Tue, Sep 12, 2017 at 9:59 PM, Dima Pasechnik wrote: On Tuesday, September 12, 2017 at 7:35:11 PM UTC+1, vdelecroix wrote: On 12/09/2017 20:32, Dima Pasechnik wrote: ah, right, do not use git://, use the same thing,

Re: [sage-devel] Re: git trac is down ?

Am 2017-09-13 um 08:20 schrieb Vincent Delecroix: > On 13/09/2017 08:17, Clemens Heuberger wrote: >> Am 2017-09-12 um 20:48 schrieb Vincent Delecroix: >>> On 12/09/2017 20:46, Clemens Heuberger wrote: Am 2017-09-12 um 20:33 schrieb Vincent Delecroix: > On 12/09/2017 20:32, Dima Pasechnik

Re: [sage-devel] Re: git trac is down ?

On 13/09/2017 08:17, Clemens Heuberger wrote: Am 2017-09-12 um 20:48 schrieb Vincent Delecroix: On 12/09/2017 20:46, Clemens Heuberger wrote: Am 2017-09-12 um 20:33 schrieb Vincent Delecroix: On 12/09/2017 20:32, Dima Pasechnik wrote: ah, right, do not use git://, use the same thing,

[sage-devel] Re: git trac is down ?

In case nobody has noticed, let me insist that this behaviour is currently preventing most (if not all) the patchbots from doing anything. Frederic Le mardi 12 septembre 2017 12:04:42 UTC+2, Frédéric Chapoton a écrit : > > I have access failures to the git repo from trac : > >

Re: [sage-devel] Re: git trac is down ?

Am 2017-09-12 um 20:48 schrieb Vincent Delecroix: > On 12/09/2017 20:46, Clemens Heuberger wrote: >> Am 2017-09-12 um 20:33 schrieb Vincent Delecroix: >>> On 12/09/2017 20:32, Dima Pasechnik wrote: ah, right, do not use git://, use the same thing, g...@trac.sagemath.org:sage.git, for