On Tue, Feb 02, 2010 at 08:05:37PM -0800, mhampton wrote:
> I'm going to give an intro talk on Sage in a couple of days, and I'm
> wondering if anyone has something particularly cool I could demo. I
> already have a lot of examples but perhaps there are some recent
> additions I could highlight th
On Wed, Feb 3, 2010 at 03:47, Minh Nguyen wrote:
> Harald knows more about the mirroring process than I do.
Yes, and we have a problem! They have shut down the master server and
therefore mirroring is broken. Also the new archlinux binary from some
days ago is affected and can't be mirrored out.
Minh Nguyen wrote:
Hi David,
On Wed, Feb 3, 2010 at 12:02 PM, Dr. David Kirkby
wrote:
Could the sage-4.3.0.1 source code, as well as these binaries, be made
available on the Sage web site, and poked out to mirrors.
I have updated the Sage website to account for the Sage 4.3.0.1 source
and
Minh Nguyen wrote:
Hi folks,
I'm happy to announce that Sage 4.3.0.1.alpha3 [1] successfully builds
on t2.math. Due to an unfortunate typo, the version number should be
Sage 4.3.0.2.alpha3 since it's based on Sage 4.3.0.1 [2]. This alpha
release is based on Sage 4.3.0.1.alpha2 [3] and merged the
On 02/01/2010 08:18 AM, xtian wrote:
> As a user, I'd prefer it the other way around, i.e. reset() would
> behave as in Sage 4.3 and before, something like
>
> reset(attached=True)
>
> could then do what the recent changes to attach() were meant
> to do (let there be a keyword for the newly intr
I need to issue updates to the patch on a trac ticket I issued.
What is the correct mode of operation:
open a new ticket referring to this one?
--- clear how to proceed
make a new patch replacing the present one?
--- I have trouble understanding how to do this in mercurial.
Do I backout my pr
On Feb 3, 11:14 am, "Dr. David Kirkby"
wrote:
> > I have updated the Sage website to account for the Sage 4.3.0.1 source
> > and binary tarballs.
>
> Where - I can't find them!
Mirroring is broken because they have shut down the master server days
ago without telling anything and hence it is impo
Robert Bradshaw wrote:
On Sat, Jan 30, 2010 at 10:16 PM, Dr. David Kirkby
wrote:
Faillure to build the haslib module results from a failure to find the
SSL
libraries. Would it not be more sensible to check for these in prereq,
then
exit if they are not found. It would save someone getting h
Harald Schilly wrote:
On Feb 3, 11:14 am, "Dr. David Kirkby"
wrote:
I have updated the Sage website to account for the Sage 4.3.0.1 source
and binary tarballs.
Where - I can't find them!
Mirroring is broken because they have shut down the master server days
ago without telling anything and h
On Wed, Feb 3, 2010 at 5:50 AM, Dima Pasechnik wrote:
> I need to issue updates to the patch on a trac ticket I issued.
> What is the correct mode of operation:
>
> open a new ticket referring to this one?
> --- clear how to proceed
>
> make a new patch replacing the present one?
> --- I have trou
Thanks for the help. It works now. I probably would be good if it was
found automatically.
On Feb 2, 11:12 pm, Robert Bradshaw
wrote:
> On Feb 2, 2010, at 7:40 PM, M. Yurko wrote:
>
> > For the simple example I just used pyximport. For the extension module
> > I used a setup.py script. The start
I'm making some changes to the eclib spkg (a bug fix and some other
useful stuff) which mean that I have to make changes in
sage/libs/mwrank. I am finding that after making edits to files in
that directory, "sage -b" does not seem to result in the rebuilt sage
knowing about the changes made.
I ca
On Wednesday 03 February 2010, John Cremona wrote:
> I'm making some changes to the eclib spkg (a bug fix and some other
> useful stuff) which mean that I have to make changes in
> sage/libs/mwrank. I am finding that after making edits to files in
> that directory, "sage -b" does not seem to resul
Thanks for the suggestion! I think even your first examples require
some patch that isn't in sage-4.3.1, since I get a
"NotImplementedError: 3D plotting of multiple edges or loops not
implemented."
-Marshall
On Feb 3, 3:28 am, "Nicolas M. Thiery"
wrote:
> On Tue, Feb 02, 2010 at 08:05:37PM -080
I made 2 new wiki pages:
http://wiki.sagemath.org/SagemathLive
http://wiki.sagemath.org/UsingSquashFS
I hope this helps.
On 3 Feb., 03:11, William Stein wrote:
> On Tue, Feb 2, 2010 at 6:02 PM, Frank Polte wrote:
>
> >> I use squashfs + unionfs for the virtualbox Sage distribution. Do you
> >
On Feb 3, 12:24 pm, "Dr. David Kirkby"
wrote:
> sage-4.3.0.1-Solaris-10-SPARC-sun4u-or-sun4v.tar.7z
yes, and i'll remove both 3.4.2 toolchain files, ok?
H
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubsc
Peter Jeremy wrote:
On 2010-Jan-31 11:15:08 +, "Dr. David Kirkby"
wrote:
Alex Ghitza wrote:
1) Build sage-4.3.1 with gcc-4.4.2 on Arch Linux; Sage runs fine, passes
doctests, etc. Someone else gets the binary and can use it to run Sage
2) Upgrade gcc to gcc-4.4.3
3) Try to run sage, get
On Wed, Feb 03, 2010 at 04:22:52AM -0800, mhampton wrote:
> Thanks for the suggestion! I think even your first examples require
> some patch that isn't in sage-4.3.1, since I get a
> "NotImplementedError: 3D plotting of multiple edges or loops not
> implemented."
Oops, indeed, with 4.3.1 you need
I have installed version 4.3.0.1 of Sage at
http://t2nb.math.washington.edu:8000/
This is functional. However, any attempt to import the _hashlib module fails
miserably, as you can see from this published worksheet.
http://t2nb.math.washington.edu:8000/home/pub/0/
Python is not finding the l
Harald Schilly wrote:
On Feb 3, 12:24 pm, "Dr. David Kirkby"
wrote:
sage-4.3.0.1-Solaris-10-SPARC-sun4u-or-sun4v.tar.7z
yes, and i'll remove both 3.4.2 toolchain files, ok?
H
Yes, I think they are pretty useless. I know for a fact they have Micheal's
paths hard-coded in them, so I think t
On Wed, Feb 3, 2010 at 17:36, Dr. David Kirkby wrote:
>> yes, and i'll remove both 3.4.2 toolchain files, ok?
> Yes, I think they are pretty useless.
I think that too, but I ask to be sure ;)
I'm also adding links to the two solaris wiki pages on the download
page on the mirrors. Consider it done
On 3 February 2010 11:54, Martin Albrecht wrote:
> On Wednesday 03 February 2010, John Cremona wrote:
>> I'm making some changes to the eclib spkg (a bug fix and some other
>> useful stuff) which mean that I have to make changes in
>> sage/libs/mwrank. I am finding that after making edits to file
Pat LeSmithe wrote:
> This is now v2 at
> http://trac.sagemath.org/sage_trac/ticket/8168
Much appreciated, thanks!
Best regards, xtian
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
Harald Schilly wrote:
On Wed, Feb 3, 2010 at 17:36, Dr. David Kirkby wrote:
yes, and i'll remove both 3.4.2 toolchain files, ok?
Yes, I think they are pretty useless.
I think that too, but I ask to be sure ;)
I'm also adding links to the two solaris wiki pages on the download
page on the mir
Sorry for the noise. It was not recompiling wrap.cc since it found an
error in compiling mwrank.pyx, which it does first, and then quit.
the error in mwrank.pyx was that I had introduced a new function but
had only put in its implementation code, not a separate declaration.
Well, I am learning!
Hi Dima,
On Wed, Feb 3, 2010 at 9:50 PM, Dima Pasechnik wrote:
> If anyone knows
> how to do this exactly, I'd most appreciate hearing details or being
> pointed to a readable manual/howto...)
See tickets #8108 and #8147 for introductory materials on patch
management with Mercurial:
http://t
On Wed, Feb 3, 2010 at 18:21, Dr. David Kirkby wrote:
> http://www.sagemath.org/doc/installation/source.html
>
> also needs updating, ...
That's the Sage documentation -> hence trac (component: documentation)
ticket + patch
> I'd like to ask on comp.unix.solaris to get some others to try Sage,
Hi David,
On Thu, Feb 4, 2010 at 4:21 AM, Dr. David Kirkby
wrote:
> http://www.sagemath.org/doc/installation/source.html
>
> also needs updating, as it says
Ticket #8175 tracks this issue:
http://trac.sagemath.org/sage_trac/ticket/8175
--
Regards
Minh Van Nguyen
--
To post to this group,
Hi Florent,
On Thu, Jan 28, 2010 at 8:08 AM, Florent Hivert
wrote:
> Sure ! Now I know which command triggered the segfault:
>
>> Trying:
>> Integer(1) < l11###line 213:_sage_ >>> 1 < l11
>> Expecting:
>> False
This is now tracked at ticket #8177:
http://trac.sagemath.org/sage_tra
Hi Nicolas,
On Wed, Feb 3, 2010 at 8:16 AM, Nicolas M. Thiery
wrote:
> If that's the case, then the following
> should be a fairly minimal code causing the crash:
This is now tracked at ticket #8177:
http://trac.sagemath.org/sage_trac/ticket/8177
--
Regards
Minh Van Nguyen
--
To post to
> make a new patch replacing the present one?
> --- I have trouble understanding how to do this in mercurial.
> Do I backout my previous patch and make a new one? (I tried this
> and it didn't seem to work. If anyone knows
> how to do this exactly, I'd most appreciate hearing details or being
>
Minh Nguyen wrote:
Hi folks,
I'm happy to announce that Sage 4.3.0.1.alpha3 [1] successfully builds
on t2.math. Due to an unfortunate typo, the version number should be
Sage 4.3.0.2.alpha3 since it's based on Sage 4.3.0.1 [2]. This alpha
release is based on Sage 4.3.0.1.alpha2 [3] and merged the
Minh Nguyen wrote:
Hi folks,
I'm happy to announce that Sage 4.3.0.1.alpha1 [1] successfully builds
on t2.math. Due to an unfortunate typo, the version number should be
Sage 4.3.0.2.alpha1 since it's based on Sage 4.3.0.1 [2]. This alpha
release is based on Sage 4.3.0.1.alpha0 and merged the fol
On Feb 3, 8:03 pm, bump wrote:
> It's a good idea to use a mercurial queues, which bring sanity to
> working on patches.
http://wiki.sagemath.org/MercurialQueues
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+u
Hi David,
On Thu, Feb 4, 2010 at 6:16 AM, Dr. David Kirkby
wrote:
> Latex is not a perquisite, so Sage printing error messages like this should
> not be acceptable.
Indeed. One does not require LaTeX to build the HTML version of the
documentation, which gets built during the compilation proce
On Feb 3, 2:30 pm, Amir wrote:
> The commands to start the build were:
>
> export SAGE_FORTRAN=/usr/local/bin/gfortran
> export SAGE_FORTRAN_LIB=/usr/local/lib/libgfortran.dylib
> make
>
> (gfortran fromhttp://r.research.att.com/tools/)
Just as a point of information; I assume you had a reason
Hi David,
On Thu, Feb 4, 2010 at 6:38 AM, Dr. David Kirkby
wrote:
> I'd like to find the source, and see if I can work out
> what went wrong between alpha2 and alpha3, and find out what is causing this
> kpsewhich error.
See this directory:
http://boxen.math.washington.edu/home/mvngu/sage-sr
Minh Nguyen wrote:
Hi David,
On Thu, Feb 4, 2010 at 6:38 AM, Dr. David Kirkby
wrote:
I'd like to find the source, and see if I can work out
what went wrong between alpha2 and alpha3, and find out what is causing this
kpsewhich error.
See this directory:
http://boxen.math.washington.edu/h
On Thu, Feb 4, 2010 at 6:16 AM, Dr. David Kirkby
wrote:
> Latex is not a perquisite, so Sage printing error messages like this should
> not be acceptable.
This issue is tracked at ticket #8180:
http://trac.sagemath.org/sage_trac/ticket/8180
--
Regards
Minh Van Nguyen
--
To post to this gr
On Feb 3, 2010, at 2:50 AM, Dima Pasechnik wrote:
I need to issue updates to the patch on a trac ticket I issued.
What is the correct mode of operation:
open a new ticket referring to this one?
--- clear how to proceed
Better to post a new patch on this ticket. You can either make a new
pat
On Feb 2, 7:28 pm, Minh Nguyen wrote:
> Hi folks,
>
> I'm happy to announce that Sage 4.3.0.1.alpha3 [1] successfully builds
> on t2.math. Due to an unfortunate typo, the version number should be
> Sage 4.3.0.2.alpha3 since it's based on Sage 4.3.0.1 [2]. This alpha
> release is based on Sage 4.3.
John H Palmieri wrote:
On Feb 2, 7:28 pm, Minh Nguyen wrote:
Hi folks,
I'm happy to announce that Sage 4.3.0.1.alpha3 [1] successfully builds
on t2.math. Due to an unfortunate typo, the version number should be
Sage 4.3.0.2.alpha3 since it's based on Sage 4.3.0.1 [2]. This alpha
release is bas
On Jan 13, 8:08 am, François Bissey wrote:
> On Wed, 13 Jan 2010 22:35:16 Craig Citro wrote:
>
> > > If you work on getting this merged upstream as a bug that's a good
> > > selling point for us. We can produce a patched ebuild and possibly
> > > get it accepted.
> > > Do you have a bug tracking n
On Feb 3, 9:26 am, Minh Nguyen wrote:
> See tickets #8108 and #8147 for introductory materials on patch
> management with Mercurial:
>
> http://trac.sagemath.org/sage_trac/ticket/8108
>
> http://trac.sagemath.org/sage_trac/ticket/8147
To learn more about patch management, please apply the followi
On Feb 3, 12:50 pm, "Dr. David Kirkby"
wrote:
> It seems to have crept in between alpha2 and alpha3, so you will not observe
> it
> in alpha1.
of which release? This is with 4.3.2.alpha1, and I thought you were
working on something derived from 4.3.0. But maybe I misunderstood.
In any case, i
On Feb 3, 11:56 am, kcrisman wrote:
> On Feb 3, 2:30 pm, Amir wrote:
>
> > The commands to start the build were:
>
> > export SAGE_FORTRAN=/usr/local/bin/gfortran
> > export SAGE_FORTRAN_LIB=/usr/local/lib/libgfortran.dylib
> > make
>
> > (gfortran fromhttp://r.research.att.com/tools/)
>
> Just
On Feb 3, 2010, at 8:33 AM, Dr. David Kirkby wrote:
I have installed version 4.3.0.1 of Sage at
http://t2nb.math.washington.edu:8000/
This is functional. However, any attempt to import the _hashlib
module fails miserably, as you can see from this published worksheet.
http://t2nb.math.washi
On Feb 3, 8:30 pm, Amir wrote:
> The commands to start the build were:
>
> export SAGE_FORTRAN=/usr/local/bin/gfortran
> export SAGE_FORTRAN_LIB=/usr/local/lib/libgfortran.dylib
> make
>
> (gfortran fromhttp://r.research.att.com/tools/)
>
> I get the following build error:
>
> gcc -DECLDIR="\"/Use
Hi John,
On Thu, Feb 4, 2010 at 8:08 AM, John H Palmieri wrote:
> In any case, if I want to test this on a system other than t2, what
> versions of Sage are relevant? (I thought the issue arose between
> 4.3.0 and 4.3.1, so trying with 4.3.2.alpha1 might be instructive.)
I think the relevant
On Feb 3, 2010, at 7:10 AM, Dr. David Kirkby wrote:
Peter Jeremy wrote:
On 2010-Jan-31 11:15:08 +, "Dr. David Kirkby" > wrote:
Alex Ghitza wrote:
1) Build sage-4.3.1 with gcc-4.4.2 on Arch Linux; Sage runs fine,
passes
doctests, etc. Someone else gets the binary and can use it to
run S
Hi David,
On Thu, Feb 4, 2010 at 7:13 AM, Dr. David Kirkby
wrote:
> I will probably need your help on how to apply those. None of them look
> likely candidates, but #6820 is perhaps the most likely of them all, as it
> is related to documentation. But the patch looks particularly complicated
>
John H Palmieri wrote:
On Feb 3, 12:50 pm, "Dr. David Kirkby"
wrote:
It seems to have crept in between alpha2 and alpha3, so you will not observe it
in alpha1.
of which release? This is with 4.3.2.alpha1, and I thought you were
working on something derived from 4.3.0. But maybe I misunders
> > > export SAGE_FORTRAN=/usr/local/bin/gfortran
> > > export SAGE_FORTRAN_LIB=/usr/local/lib/libgfortran.dylib
> > > make
>
> > > (gfortran fromhttp://r.research.att.com/tools/)
>
> > Just as a point of information; I assume you had a reason to use a
> > different Fortran? I seem to recall that
Minh Nguyen wrote:
Hi David,
On Thu, Feb 4, 2010 at 7:13 AM, Dr. David Kirkby
wrote:
I will probably need your help on how to apply those. None of them look
likely candidates, but #6820 is perhaps the most likely of them all, as it
is related to documentation. But the patch looks particular
Dr. David Kirkby wrote:
John H Palmieri wrote:
On Feb 3, 12:50 pm, "Dr. David Kirkby"
wrote:
It seems to have crept in between alpha2 and alpha3, so you will not
observe it
in alpha1.
of which release? This is with 4.3.2.alpha1, and I thought you were
working on something derived from 4.3
On Feb 3, 1:49 pm, "Dr. David Kirkby" wrote:
> Dr. David Kirkby wrote:
> > John H Palmieri wrote:
> >> On Feb 3, 12:50 pm, "Dr. David Kirkby"
> >> wrote:
>
> >>> It seems to have crept in between alpha2 and alpha3, so you will not
> >>> observe it
> >>> in alpha1.
>
> >> of which release? This i
On Feb 3, 1:43 pm, kcrisman wrote:
> > > > export SAGE_FORTRAN=/usr/local/bin/gfortran
> > > > export SAGE_FORTRAN_LIB=/usr/local/lib/libgfortran.dylib
> > > > make
>
> > > > (gfortran fromhttp://r.research.att.com/tools/)
>
> > > Just as a point of information; I assume you had a reason to use a
I just tried to compile from source to get a 32-bit version running on
my laptop.
I have:
$gcc -v
Using built-in specs.
Target: i686-apple-darwin10
Configured with: /var/tmp/gcc/gcc-5646.1~2/src/configure --disable-
checking --enable-werror --prefix=/usr --mandir=/usr/share/man --
enable-language
On 02/03/2010 09:11 AM, xtian wrote:
> Pat LeSmithe wrote:
>> This is now v2 at
>> http://trac.sagemath.org/sage_trac/ticket/8168
> Much appreciated, thanks!
No problem. Do you have a Sage trac account?
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from t
On Wed, Feb 3, 2010 at 12:50 PM, Dr. David Kirkby
wrote:
> John H Palmieri wrote:
>>
>> On Feb 2, 7:28 pm, Minh Nguyen wrote:
>>>
>>> Hi folks,
>>>
>>> I'm happy to announce that Sage 4.3.0.1.alpha3 [1] successfully builds
>>> on t2.math. Due to an unfortunate typo, the version number should be
>
Hi all,
I'm very soon going to release mpmath 0.14. One of the most important
changes for Sage is a large speedup due to a faster backend (written in
Cython), to be located in sage.libs.mpmath. For the necessary additions to
sage.libs.mpmath, see this ticket:
http://trac.sagemath.org/sage_trac/tic
These are the only Sun and ia64 machines I have reliable access to.
Can anyone build 4.3.2.alpha1 there?
And if yes, where and how?
(I spent some time trying, without success...)
I'd like to test my patches, in particular on ia64
Thanks,
Dima
--
To post to this group, send an email to sage-d
Hi Dima,
On Thu, Feb 4, 2010 at 1:33 PM, Dima Pasechnik wrote:
> These are the only Sun and ia64 machines I have reliable access to.
> Can anyone build 4.3.2.alpha1 there?
I have tried to build previous versions of Sage on Skynet's Sun
machines. All build attempts failed. As for the IA64 machine
On Feb 3, 5:51 pm, William Stein wrote:
> On Wed, Feb 3, 2010 at 12:50 PM, Dr. David Kirkby
>
>
> wrote:
> > John H Palmieri wrote:
>
> >> On Feb 2, 7:28 pm, Minh Nguyen wrote:
>
> >>> Hi folks,
>
> >>> I'm happy to announce that Sage 4.3.0.1.alpha3 [1] successfully builds
> >>> on t2.math. Due
2010/2/3 Minh Nguyen :
> Hi Dima,
>
> On Thu, Feb 4, 2010 at 1:33 PM, Dima Pasechnik wrote:
>> These are the only Sun and ia64 machines I have reliable access to.
>> Can anyone build 4.3.2.alpha1 there?
>
> I have tried to build previous versions of Sage on Skynet's Sun
> machines. All build attem
a day or so ago I posted here on
"sage-4.3.2.alpha1: building problem on Linux ia64 (divsi3 can't be
found?)"
On Feb 4, 10:38 am, Minh Nguyen wrote:
> Hi Dima,
>
> On Thu, Feb 4, 2010 at 1:33 PM, Dima Pasechnik wrote:
> > These are the only Sun and ia64 machines I have reliable access to.
> > C
William,
can I steal/clone your Sage installation there?
Thanks!
On Feb 4, 10:52 am, William Stein wrote:
> 2010/2/3 Minh Nguyen :
>
> > Hi Dima,
>
> > On Thu, Feb 4, 2010 at 1:33 PM, Dima Pasechnik wrote:
> >> These are the only Sun and ia64 machines I have reliable access to.
> >> Can anyone b
2010/2/3 Dima Pasechnik :
> William,
> can I steal/clone your Sage installation there?
> Thanks!
The sage-4.3.2.alpha0 was built with GCC-4.4.2. Now GCC-4.4.3 is
installed on there, so got to start from scratch.
>
> On Feb 4, 10:52 am, William Stein wrote:
>> 2010/2/3 Minh Nguyen :
>>
>> > Hi D
Hi! I am giving a Python workshop in the uni, and i'd like to include
Sage as a final topic to show Python's potential.
I'd love to tell my students that Sage included everything they liked
about Python and more. But there is one thing missing, and that is
syntax hilighting. People have loved
People seem to like my fractals:
http://christopherolah.wordpress.com/2009/12/19/formation-of-escape-time-fractals/
I'm planning to write a convenience function for these sort of things,
but they're fairly trivial otherwise.
How to make these:
Import (copy paste) William's compose function (it
Mozilla Bespin[1], which is an browser-based IDE with syntax highlighting
etc, recently released an easy way to embed the editor in your own web
pages. I'll look into how hard it would be to use in Sage. It's still
pretty alpha.
- Alex
[1] https://bespin.mozilla.com/
--
To post to this group
Hi folks,
Due to a rather short release schedule [1], I'm releasing an rc0 of
Sage 4.3.2. If there are no show-stoppers, then this would become the
final release candidate. The source tarball is available at
http://boxen.math.washington.edu/home/mvngu/sage-src/sage-4.3.2.rc0.tar
The sage.math bi
Hi,
I hope this is enough of a bug report so that someone can do something
to fix it...
After an hour or so of trying to boil this down to its essence, I
think I have something nice and reproducible. If you apply the
attached patch, it adds a file
"sage/schemes/elliptic_curves/bug_in_parallel.py"
On 02/03/2010 09:33 PM, Alex Leone wrote:
Mozilla Bespin[1], which is an browser-based IDE with syntax
highlighting etc, recently released an easy way to embed the editor in
your own web pages. I'll look into how hard it would be to use in
Sage. It's still pretty alpha.
What about http://tra
Hi folks,
On Thu, Feb 4, 2010 at 4:02 PM, Minh Nguyen wrote:
> Please test and report all problems.
On bsd.math (Mac OS X 10.6.2), I got the usual segfault with the
module sage/structure/element_wrapper.py. This is tracked at ticket
#8177:
http://trac.sagemath.org/sage_trac/ticket/8177
--
On Feb 3, 10:45 pm, Minh Nguyen wrote:
> Please test and report all problems.
As an upgrade, the process halts with a question requiring input from
the user:
cddlib-094f.p2/SPKG.txt
Finished extraction
patching file src/src-gmp/Makefile.am
Reversed (or previously applied) patch detected! Assum
On 4 Feb, 02:51, John H Palmieri wrote:
> On Feb 3, 5:51 pm, William Stein wrote:
>
>
>
> > On Wed, Feb 3, 2010 at 12:50 PM, Dr. David Kirkby
>
> > wrote:
> > > John H Palmieri wrote:
>
> > >> On Feb 2, 7:28 pm, Minh Nguyen wrote:
>
> > >>> Hi folks,
>
> > >>> I'm happy to announce that Sage
Hi Rob,
On Thu, Feb 4, 2010 at 6:12 PM, Rob Beezer wrote:
> cddlib-094f.p2/SPKG.txt
> Finished extraction
>
> patching file src/src-gmp/Makefile.am
> Reversed (or previously applied) patch detected! Assume -R? [n]
This is due to some bad patching practices in the cddlib spkg. The
issue is t
78 matches
Mail list logo
