Volker Braun wrote:
> On Friday, July 29, 2016 at 6:58:20 PM UTC+2, leif wrote:
>
> Well, while "certificate" is ambiguous (as it can be a verb as well
> as a
> noun),
>
>
> While technically true, "certificate" is not commonly used as a
ell as a
noun), "certify" is not, and for boolean parameters/keywords, we usually
take the imperative from.
So I'd prefer the latter.
(There are of course dozens of instances where one could misguess the
expected type because of this frequent ambiguity, but if we can
disambiguate, w
ompleted a build of Singular where I had forcibly changed all
> instances of -lgmp to -lmpir in the makefiles, and it works now, so
> that's reassuring.
When you're back, you could try building Sage with the optional GMP
package*. I'm curious as to whether you'll then get tw
ow and would need some loving attention to get it
> working again.
>
> I think it still worked one year ago! even on Cygwin.
Last time I tried on Linux (perhaps one or two weeks ago) it
embarrassingly failed...
(Didn't look closer into the issue though, but IIRC some symbols needed
by a
1 (with some previous beta of Sage) on
Cygwin yet, I guess. Otherwise some trouble could come from that, too.
-leif
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from i
Andrew wrote:
> On Wednesday, 27 July 2016 18:13:44 UTC+10, leif wrote:
>
> Andrew wrote:
> > I just installed an optional package but it took me a while to
> remember
> > how to do it. Of course, it is completely straightforward but I just
>
leif wrote:
> It seems I'm again not getting any trac notifications since about 20:00
> UTC yesterday (July 24th).
>
> (And no, I didn't change my preferences...)
Orthogonal to that, but also annoying is that we do no longer get
notifications when a ticket gets close
MB upstream/python-2.7.10.tar.gz
15 MB upstream/ppl-1.2.tar.bz2
15 MB upstream/matplotlib-1.5.1.tar.bz2
12 MB upstream/scipy-0.17.1.tar.gz
11 MB upstream/Pillow-3.3.0.tar.gz
Wondering whether we should delete at least larger binary attachments
from trac after some time (not necessarily im
-pip [...] -- invoke pip, the Python package manager
besides further usage help on other topics.
-leif
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it,
leif wrote:
> Paul Masson wrote:
>> As I recall I did checkout that ticket (21006) by accident when I wanted
>> one (21008) a couple digits away. That's the source of the problem.
>>
>> Why can't the build system recognize an empty folder and pass over it
ls -d ...'.)
But as I said, there's definitely a bug in Sage's top-level 'configure'
we will fix, such that this kind of obscure error will never happen again.
-leif
--
You received this message because you are subscribed to the Google Groups
"sage-devel&quo
figure' later exits normally).
I'll open a ticket unless someone beats me in doing so. (IMHO worth a
blocker, but I don't know how far Volker is in preparing the 7.3 release
candidate.)
-leif
> On Tuesday, July 26, 2016 at 1:20:38 PM UTC-7, Volker Braun wrote:
>
>
William Stein wrote:
> On Tue, Jul 26, 2016 at 11:39 AM, leif wrote:
>> William Stein wrote:
>>> Regarding the above discussion about speed, what combination of
>>> OS/Virtualization/Emulations/Native/etc. is actually fastest is not
>>> something that can be
William Stein wrote:
> On Tue, Jul 26, 2016 at 6:44 AM, leif wrote:
>> Samuel Lelievre wrote:
>>> Maybe we could create packages.sagemath.org?
>>
>> And/or create a trac plug-in which saves uploaded spkgs there/elsewhere,
>> i.e., to a location which
ot; when building with MSVC.)
(Unpredictable?) scheduling on Windows when trying to tune is another
issue, as is in a VM running on top of Windows, according to Bill I think.
-leif
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To
leif wrote:
> Jeroen Demeyer wrote:
>> Got it! Your Makefile is corrupted,
>
> I wouldn't say it's "corrupted", it's misgenerated: All packages
> (alphabetically) starting with ptyprocess are /consistently/ missing.
>
> So apparently already the
DIR in $SAGE_ROOT/build/pkgs/*;
consistently ends too early, as filtered_packages_list() is later called
a couple of times.
-leif
> see this part:
>
> [...]
> inst_pkgconf = $(INST)/pkgconf-0.9.7
> inst_pkgconfig = $(INST)/pkgconfig-1.1.0
> inst_planarity = $(INST)/planar
rever. As long as Microsoft supports it.
>>
>
> OS bashing will not be tolerated.
But company bashing will... ;-)
Microsoft used to have a POSIX layer also; no idea what happened to that
(and how usable it actually was/is).
But it never made it into mainstream Windows AFAIK.
-lei
ly/ true.
W.r.t. "native": Most binaries from Ubuntu won't exploit the
capabilities of modern CPUs though.
-leif
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from
A good example that comes to my
> mind is LaTeX: packages constantly need to reinvent the wheel because
> fixing a broken wheel is backwards-incompatible.
To summarize, TeX is dead (as is m4). ;-)
-leif
--
You received this message because you are subscribed to the Google Groups
&quo
Samuel Lelievre wrote:
> Maybe we could create packages.sagemath.org?
And/or create a trac plug-in which saves uploaded spkgs there/elsewhere,
i.e., to a location which doesn't get backed up [the way trac
attachments currently get].
Erik? :P
-leif
> 2016-07-25 21:33:39 UT
re
for later comparison, rerun ./configure, and see whether you get a
different (especially longer) build/make/Makefile after doing so.
(If it hasn't changed, there's no point in rerunning 'make'.)
-leif
__
* every package after PPL, i.e. ptyprocess pybtex pycrypto pyfl
leif wrote:
> Paul Masson wrote:
>> Ran make again without specifying any jobs, which I understand to be the
>> same as specifying one job. Same error from Atlas this time as well.
>> Here's the contents of that log:
>>
>> Found local metadata for atlas-3.10.
cause, namely that
Sage's Python doesn't get built. (I know how I could manage to get the
same errors, but in your case something else seems to be wrong.)
Could you post your build/make/Makefile somewhere, too? (It's not that
large, but long, ~2900 lines...)
And to go triple-safe
Paul Masson wrote:
> Sorry about that Leif. My bad.
>
> I'm the only person using this machine, so I'm the administrator. The
> directory in the Cython error is a system directory.
Yes, and Sage shouldn't try to write to /that/.
> I think my very first build of 7
loads/GitHub/sage/local/var/lib/sage/installed/atlas-3.10.2.p2]
Error 1
-leif
> On Sunday, July 24, 2016 at 11:54:06 PM UTC-7, Volker Braun wrote:
>
> Whats in the logs?
>
> Did you just apply the most recent OSX update?
>
>
>
> On Monday, July 25, 2016
Dima Pasechnik wrote:
> Yes indeed, we are over the sendgrid quota; I think tomorrow we will get
> another month of 12K free emails.
But the 12KB/month will presumably get eaten up quickly already by the
queued mails... ;-)
Perhaps another good reason to address #19832 [1].
-leif
[1]
It seems I'm again not getting any trac notifications since about 20:00
UTC yesterday (July 24th).
(And no, I didn't change my preferences...)
-leif
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from
ac.sagemath.org/ticket/21093
-leif
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group,
page of the Sage trac wiki, and
at some point we had spkg-upload.googlecode.com for exactly that
purpose, at least for those without a sage.math cluster account, when
everybody's home folder was accessible via HTTP.)
-leif
>> On Monday, July 25, 2016 at 12:43:28 AM UTC+2, Andrey Novoseltsev wrote:
>
al, say
(unless one names them different, as with e.g. python2 and python3, but
the latter are treated specially in the build system, like GMP vs. MPIR,
where on the other hand is no "name clash").
We by the way also still have TOPCOM and topcom.
-leif
--
You received this message bec
leif wrote:
> It's not just that the file isn't mirrored, it's not on the main server
> either. (So the error message is wrong as well.)
>
> I guess it was merged with 7.3.beta8, when fileserver.sagemath.org was
> down, so the package metadata exists (because of
ouldn't be uploaded to the server.
The upstream tarball is here:
http://www.broune.com/frobby/frobby_v0.9.0.tar.gz
(according to [1] at least...)
-leif
[1] https://trac.sagemath.org/ticket/20905
--
You received this message because you are subscribed to the Google Groups
"sage-dev
pple's latest Xcode"
echo "unless you already have it. You can install this using"
echo "the App Store. Also, make sure you install Xcode's"
echo "Command Line Tools -- see Sage's README.txt."
Perhaps we should add an explicit ch
Harald Schilly wrote:
> On Thu, Jul 21, 2016 at 10:25 AM, leif wrote:
>> Could you track this down?
>>
>> I'm really curious.
>
> well, so far no chance. there is definitely nothing LD* related set by
> me, but my hunch is, that it might be a side effect
in. It's also a bit strange,
> because this error seems to come and go erratically. I'll try to see if
> I can notice something more concrete.
Could you track this down?
I'm really curious.
-leif
--
You received this message because you are subscribed to the Google Groups
&q
Volker Braun wrote:
> Please check up on fileserver.sagemath.org, too, while you are at it...
Yes, their IPs differ by just one... ;-)
-leif
> On Thursday, July 21, 2016 at 2:20:17 AM UTC+2, William wrote:
>
> On Wed, Jul 20, 2016 at 12:39 PM, Frédéric Chapoton
&
Francois Bissey wrote:
> Works out of the box on my Mac 10.11 machine. Definitely want logs.
And the analogue of /proc/cpuinfo...
-leif
> François
>
>> On 21/07/2016, at 17:14, Travis Scrimshaw wrote:
>>
>>Another point of reference/FYI, this failed when I was
ound; a better solution for MacOS X (and not just the NTL
package) will come later, on #20779.
#21064 is ready for testing by the way / needs review.
-leif
[1] https://trac.sagemath.org/ticket/21064
--
You received this message because you are subscribed to the Google Groups
"sage-devel&quo
chris wuthrich wrote:
>
> Thanks a lot, leif, for the help.
>
> I will ask the sysadmin to update binutils.
Well, in this case Sage built and used its own GCC (currently 4.9.3)
because at least /the default one/ on your system is outdated as well.
You may ask the sysadmin wheth
leif wrote:
> leif wrote:
>> chris wuthrich wrote:
>>>
>>> Trying to compile sage 7.3.beta8 on CentOS6.8, I ran into a problem
>>> compiling ntl 9.8.1.
>>>
>>> Not sure what to include. Just ask.
>
> You may give us the output of &#
leif wrote:
> chris wuthrich wrote:
>>
>> Trying to compile sage 7.3.beta8 on CentOS6.8, I ran into a problem
>> compiling ntl 9.8.1.
>>
>> Not sure what to include. Just ask.
You may give us the output of 'as --version'.
> Huh, dead old toolchain o
march=native' in NTL. (There's some 'configure' flag to NTL to not
use it...)
-leif
P.S.: That's a known bug (NTL not checking whether the assembler can
cope with GCC's output in case of '-march=native'), but this so far has
hit us only on MacOS X.
> H
gen/pari/doc.py
+++ b/src/sage_setup/autogen/pari/doc.py
@@ -107,6 +107,7 @@ def raw_to_rest(doc):
doc = doc.replace("@[pm]", "±")
doc = doc.replace("@[nbrk]", unichr(0xa0))
doc = doc.replace("@[agrave]", "à")
+doc = doc.replace
leif wrote:
> John Cremona wrote:
>> I have a similar problem, on a machine which has successfully built
>> Sage in the past. Version 7.2 (literally commit f76401f).
>>
>> The last few commainds in history are
>>
>> make distclean
>> ../configure
&
ctory
> Traceback (most recent call last):
> File "", line 1, in
> ImportError: No module named sage_setup.autogen.pari
> make[3]: *** [sage/libs/pari/auto_gen.pxi] Error 1
> make[3]: Leaving directory `/home/lmfdb/sage/src'
Well, which group owns the folder, and does that grou
in. It's also a bit strange,
> because this error seems to come and go erratically. I'll try to see if
> I can notice something more concrete.
R U building as root?!?!??
Never do that, or fix the ncurses package... ;-)
-leif
--
You received this message because you are subscribed t
ing, but
you get that "only" each time you run 'make' (or install a package).
-leif
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to s
it.sagemath.org/sage.git/log/?h=u/paulmasson/9654 (provided you
know the branch).
-leif
> On Tuesday, July 5, 2016 at 1:15:55 PM UTC-7, Dima Pasechnik wrote:
>
> I see errors like MethodNotFound: RPC method "search.branch" not found
>
> in trac log. Er
William Stein wrote:
> On Tue, Jul 5, 2016 at 10:37 AM, leif wrote:
>> Erik Bray wrote:
>>> That could and probably should be fixed though. In this case just
>>> changing decode('ascii') to decode('latin1') will go a long way (will
>>> re
irst and fall back on latin-1 if that
> fails.
We do not even support spaces in the pathname (a common problem for
MacOS X and Windoze users), since that already breaks a couple of
upstream packages.
-leif
> On Tue, Jul 5, 2016 at 5:27 PM, Dima Pasechnik wrote:
>> some parts of Sag
Dima Pasechnik:
> some parts of Sage do not work if Sage is installed in a directory with
> non-ascii characters in its name. And you have that "Téléchargements" there.
> Rename it to something ascii-only..
Đŏŵňłøåďş for example.
-leif
--
You received this message because
delays. We will apply preference and opinion
aggregation techniques [3] to develop a community prioritisation scheme
for bugs and feature requests (which may rely on a reputation scores
technique, such as one used on MathOverflow), and implement this scheme
as a TRAC [39] add-on D7.2. As SAGE is using
bably more.
>>
>> Voting would be restricted to people with a trac account.
>>
>> Any substantial objections to this?
>
> Yes. What is the point of voting for tickets?
Fun.
-leif
--
You received this message because you are subscribed to the Google Groups
"
rac account.
>
> Any substantial objections to this?
Provided we can vote on each comment, no.
But it seems we have no choice anyway... (read on)
-leif
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this gr
ific spkg versions are
now stupidly tied together (even for optional spkgs).
-leif
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel
decisions, or to attract reviewers, but the main
discussion and development happens on trac.
-leif
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sag
Erik Bray wrote:
> On Fri, Jul 1, 2016 at 8:11 PM, leif wrote:
>> Jori Mäntysalo wrote:
>>> On Fri, 1 Jul 2016, Erik Bray wrote:
>>>
>>>> One thing that will help, which has already been discussed up-thread,
>>>> is having Trac help take car
d side as well.
Hint: "*".join(["alpha","beta","gamma"]) gives 'alpha*beta*gamma' for
example.
In your case the list to join is something like
[ "(%s)^%s" % (f[0], f[1]) for f in prod_String ]
so you could replace the five last lines by
cessors [1] (aka syntax highlighting)?
I recall there was some issue displaying /git/ diffs which is fixed now,
but while '#!diff' works on trac pages, e.g. '#!sh' and '#!python' do no
longer work.
-leif
[1] https://trac.sagemath.org/wiki/WikiProcessors#AvailableProce
27;--debug=a') is far too verbose, but e.g. '--debug=bvjm',
probably also with '--trace' may give you a clue what's happening (or
why 'make' /doesn't/ build some targets).
-leif
>> Forgot to ask:
>>
>> How does at all local/var/lib/s
leif wrote:
> Ralf Stephan wrote:
>> On Wednesday, June 1, 2016 at 10:00:34 AM UTC+2, Ralf Stephan wrote:
>>
>> The giac and giacpy packages are now one year optional (#12375). Since
>> pynac-0.6.6 (#20742) has optional support for giac, and uses it to
>>
r.gz
44M giac-1.2.2.37.tar.gz
41K giacpy-0.5.6.tar.gz
Haven't examined why it has grown by 300% in a minor version update though.
Otherwise additional ~12 MB to the Sage tarball would IMHO be ok; it
exploded during the last few years anyway...
-leif
--
You received this message becau
1] isn't complete. (A
separate file / database would be good anyway, and trac already has
something like that.)
We may also change these fields to contain trac account names, but
that's a matter of taste (and tradition), too.
I think Jeroen *did* automate the posts regarding empt
ll using Python's multi-processing though, as
does docbuilding.
Forgot to ask:
How does at all local/var/lib/sage/installed/ look like?
-leif
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiv
iles for the above packages (I do have for many other packages
> though, all of which I guess are installed.)
>
> I'm at a total loss...
$ make --version
?
Did you build in parallel, and if so, does probably building
sequentially fix the problem (such that the missing packages then
Erik Bray wrote:
> On Tue, Jun 28, 2016 at 7:14 PM, leif wrote:
>> Erik Bray wrote:
>>> While we're tinkering with the workflow, I think we need to change the
>>> workflow associated with testing changes.
>>>
>>> Currently the release manager *
inutils or create appropriate symlinks along
PATH (such that 'ar' and 'ranlib' originate from them), but I have no
idea whether that's at all related to your main problem.
If 'ar' etc. fail but that error isn't catched that's of course a bug.
-leif
P
leif wrote:
> Erik Bray wrote:
>> While we're tinkering with the workflow, I think we need to change the
>> workflow associated with testing changes.
>>
>> Currently the release manager *closes* a ticket and marks it as
>
> s/currently the relea
ote that the buildbots do test tickets having positive review, some
also those with "needs review", so with relatively frequent "beta
releases", it's not all that bad.
-leif
--
You received this message because you are subscribed to the Google Groups
"sage-devel
$SAGE_ROOT/logs/pkgs/jmol-*.log after issuing the
> ./sage -i jmol command, unfortunately. So, all I found there was the log
> file being written
> at that time.
Sage doesn't overwrite existing logs, so the log should contain the
output from both attempts.
-leif
> Interest
#x27;s a new Reply-To since about a day...
Seems there's some randomness in the message IDs for the same posts.
-leif
> Moreover, some
> of the e-mails got a reply-to (t...@sagemath.org) and some others not.
> Is there some misconfiguration?
>
> Best
> Vincent
--
You
Dima Pasechnik wrote:
> On Wednesday, June 22, 2016 at 11:24:31 PM UTC+1, leif wrote:
>
> Dima Pasechnik wrote:
> > Trac emails should work now
>
> Yes, thanks.
>
> > (going via sendgrid.net <http://sendgrid.net>).
>
> Why that? I
d this with the sage_trac plugin without
> needing to patch Trac. This is not unprecedented--I used to maintain
> a plugin that was nothing bug fixes for Trac bugs :)
There are at least 17 victims:
a.serrano
aly.deines
andrew.mathas
aram.dermenjian
daniel.disegni
edward.scheinerman
f.poloni
fred
age-flame (and please reply there
if you like):
"Building the car" was one of our mission statements!
SCNR,
-leif
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails fr
on; in our previous version errno wasn't
checked at all, just whether the return value of getcwd() was NULL (then
increasing the size of the buffer until it fits).
-leif
> On Sunday, June 19, 2016 at 12:56:04 AM UTC+2, François wrote:
>
> Hi,
>
> As some of you may kn
getting harder to work around) than a newer version of something
just shipping some high-level library function only for developers'
convenience. This at least used to be also Sage's policy (cf. bash and
pipestatus, shipping GCC, etc.).
-leif
--
You received this message because you
Python 2.7, and probably
also a more recent GCC. I'd personally of course prefer if Sage
required at most Python 2.6 to bootstrap.)
-leif
P.S.: IMHO it's already stupid that building Sage requires some other
Python despite Sage building its own; it would seem even more stupid if
it required
9 2687 sympow-1.018.1/periods.c
204679 8957 sympow-1.018.1/generate.c
165620 8349 sympow-1.018.1/compute2.c
3704 15059 164551 total
But one should probably start with reformatting it before making any
(further) logical changes... ;-)
The GP stuff is redundant, or a
quot;,"w");
> for (j=0;j
> there is also
>
> void txt2bin(int num,char *B,FILE *R)
> {double *P; FILE *F; P=malloc(36*4*num*sizeof(double));
> read_file_mesh(num,P,R); F=fopen(B,"w");
> fwrite(P,sizeof(double),36*4*num,F); fclose(F); free(P);}
... where
t; with the source distribution.
>
> I've never needed such a thing, and I suspect that anything cysignals
> things it needs it doesn't really. But something like that would be
> be a possibility. You shouldn't need the entire machinery of Cython
> just to link some so
s* if it cannot open a file?
That's pretty easy to achieve:
fp=fopen("/youre/not/allowed/to/access/this/folder/foo","w");
/* don't check the return value */
fwrite("booom!",1,6,fp);
You'll normally get a warning because frwite() etc. carry the
warn_un
hether that'll work with
binary_pkg, but it IMHO should.
IIRC the folder has to already exist, so you could create e.g.
/tmp/sage-build and export that. You can safely delete it after the
build has finished.
-leif
> On Tuesday, June 7, 2016 at 12:18:15 PM UTC-4, leif wrote:
>
>
Dima Pasechnik wrote:
> On Tuesday, June 7, 2016 at 5:18:15 PM UTC+1, leif wrote:
>
> Nathan Dunfield wrote:
> > I used the instructions on
> https://github.com/sagemath/binary-pkg
> <https://github..com/sagemath/binary-pkg>
> > <htt
hat's perhaps a bit funny, and I've never seen that before, but TBH, it
wouldn't really surprise me if that was the case... B)
-leif
> I tried building
> 7.3.beta3 on 10.9 via "binary-pkg", but I'm getting this error:
>
> bash-3.2$ make package-sage PAC
ing the older ones.
> So if your system gcc is newer that the current Sage 4.9.3, you're
> most surely stuck with using the new one...
>
>
> Okay, I'm downgrading my gcc to 4.9.3 and I'll run `make` and report
> back. Thanks.
FWIW, the GCC 5.x versions s
emits...
We've seen such a couple of times in the past.
-leif
> François
>
>> On 6/06/2016, at 13:47, Nathan Dunfield wrote:
>>
>> On OS X versions 10.8 (Mountain Lion) and 10.9 (Mavricks), the recently
>> updated NTL package fails to build with the follow
William Stein wrote:
> +1 the version!
Anticipating the next +1, Sage 11.0.
-leif
> On Thursday, December 17, 2015, Francois Bissey
> <mailto:francois.bis...@canterbury.ac.nz>> wrote:
>
> +1
> > On 18/12/2015, at 12:42, Volker Braun > wrote:
&g
John Cremona wrote:
> Why not just link to the main git homepage at http://git-scm.com/
Because there are no cats on that page (only a penguin and a camel).
-leif
> and let people find further links there for learning git?
>
> John
>
> On 15 May 2015 at 15:17, kcrisman wr
y upstream packages from a mirror [1] "manually". (On the
mirrors, the upstream tarballs are in 'spkg/upstream/', not
'packages/upstream/'.)
Or just cherry-pick the changes from #15642 (and probably also #18414);
see also sage-release.
-leif
[1] http://www.sagemath.org/
4-test.patch?view=markup
> is what you want.
Date: Wed Jul 2 12:58:50 2014 +0200
ROFL, did we lose a patch upon upgrading?
> Yes I am a naughty boy not to open a ticket when it cropped up last.
Can you do it now? :P
-leif
>> On 15/05/2015, at 17:50, leif wrote:
>> L
leif wrote:
> Laurent Bakri wrote:
>> Hi all,
>> today I tried to compile from source sage6-6 on the linux mint debian
>> edition ( the binary for debian did not work properly for me : no
>> evaluate button in notebook mode the menu buttons not working neither...)
>&
***/
I'm getting exactly the same failure (note that FLINT's *test suite*
fails) with Sage 6.7.rc0 on Ubuntu 10.04.4 LTS (GCC 4.4.3).
I apparently haven't installed FLINT with SAGE_CHECK=yes for a while...
-leif
--
You received this message bec
)
> sage: f.add_edges([(0,1),(0,2),(0,3),(0,4),(0,5),(1,2),(2,3),(3,4),(4,5)])
> sage: f.tutte_polynomial().subs(x=1,y=1)
> 55
> sage: Matroid(f).tutte_polynomial().subs(x=1,y=1)
> 55
Fixed in Sage 6.7.beta5 (#18366).
-leif
--
You received this message because you are subscribed to
tml/en/reference/*
Well, symlinking the folders in html/en/ on the top level should be
sufficient.
-leif
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
as the log says (also attached).
We need the file
/cygdrive/d/sage/sage-6.6/local/var/tmp/sage/build/polybori-0.8.3/src/config.log
to see why the test failed. (Probably due to a linker error since
libm4ri uses libpng, but that's shooting into the dark.)
-leif
--
You received this mes
hat's presumably the easiest and quickest solution.
-leif
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
Dima Pasechnik wrote:
> On Wednesday, 13 May 2015 20:55:16 UTC+1, leif wrote:
>
> Dima Pasechnik wrote:
> > On Wednesday, 13 May 2015 17:55:17 UTC+1, leif wrote:
> >
> > Volker Braun wrote:
> > > IMHO:
> > >
>
Dima Pasechnik wrote:
> On Wednesday, 13 May 2015 17:55:17 UTC+1, leif wrote:
>
> Volker Braun wrote:
> > IMHO:
> >
> > * The package type (standard/optional/experimental) should be in a
> file
> > inside the package directory
>
&
could help.
Sure. Currently the top-level index.html files on the mirrors refer
back to http://www.sagemath.org/doc/index.html ("Documentation"), FWIW.
-leif
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe
201 - 300 of 1271 matches
Mail list logo
