I have reread this thread and I'm asking myself if the ecl upgrade
shouldn't have simply bumped the package-version.txt of maxima at
patchlevel, thus forcing a rebuild. I mean the author of that ticket surely
had the same fail when testing, and the reviewer too?
Please tell what I'm missing.
Reg
You have my attention. We can of course wait with any future releases until
somebody fixes this.
In an ideal world we would have reliable library versioning, so you
wouldn't need to rebuild maxima UNLESS the ecl library version changes in
an incompatible way (which can be read off from the name
Nathann Cohen wrote:
Yoo !!
Why would we need a buggy upgrade script ?
Backwards compatibility. And I personally don't want ATLAS to get rebuilt
just because someone decided to change the spkg-install script of readline
such that Python gets rebuilt upon which unfortunately ATLAS
Nathann Cohen wrote:
(And I originally only wanted to add an additional target 'upgrade', setting
the variable to 'yes' and depending on 'build'. When 'yes' is the default,
I don't know what the opposite target should be called;
'quick-and-dirty-upgrade-not-really-rebuilding-dependent-packages'
Yoo !!
>> Why would we need a buggy upgrade script ?
>
> Backwards compatibility. And I personally don't want ATLAS to get rebuilt
> just because someone decided to change the spkg-install script of readline
> such that Python gets rebuilt upon which unfortunately ATLAS depends, just
On Monday, May 26, 2014 4:14:56 PM UTC+2, Nathann Cohen wrote:
>
> > Open a ticket and someone might feel less lazy :)
>
> I don't believe in opening tickets without writing the patch and
> setting them to needs_review :-P
>
Set them to "blocker".
That will get the release manager attention.
Nathann Cohen wrote:
E.g. by simply adding the lines
SAGE_UPDGRADING ?= yes
export SAGE_UPGRADING
I know how to fix "my" problem, I just don't know how to fix Sage.
To the top-level *Makefile* that is. ('?=' is not [ba]sh syntax AFAIK.)
(And I originally only wanted to add an additional
> Open a ticket and someone might feel less lazy :)
I don't believe in opening tickets without writing the patch and
setting them to needs_review :-P
Nathann
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and st
On Monday, May 26, 2014 3:39:33 PM UTC+2, Nathann Cohen wrote:
>
> > Whether we should make it the default in the top-level Makefile has been
> > discussed a couple of times in the past years, and IIRC most agreed we
> > should do so, but so far even 'sudo open a ticket' failed.
>
> I really d
> E.g. by simply adding the lines
>
> SAGE_UPDGRADING ?= yes
> export SAGE_UPGRADING
I know how to fix "my" problem, I just don't know how to fix Sage.
> (And I originally only wanted to add an additional target 'upgrade', setting
> the variable to 'yes' and depending on 'build'. When 'yes' is t
Nathann Cohen wrote:
Whether we should make it the default in the top-level Makefile has been
discussed a couple of times in the past years, and IIRC most agreed we
should do so, but so far even 'sudo open a ticket' failed.
I really do not know how such things are changed ...
E.g. by simply a
> Whether we should make it the default in the top-level Makefile has been
> discussed a couple of times in the past years, and IIRC most agreed we
> should do so, but so far even 'sudo open a ticket' failed.
I really do not know how such things are changed ...
Nathann
--
You received this mess
Nathann Cohen wrote:
Alternatively, build with SAGE_UPGRADING=yes (this will check dependencies
and reinstall Maxima after ECL has been updated).
What is the reason for not making this the default ?
I cannot currently edit your ~/.bashrc (nor your ~/.sage/sagerc *) ...
Whether we should mak
> Lazyness?
You are not lazy, and neither am I. Do we change that ? It seems that
setting this to False does not help in any way, least of all if it is
the default behaviour.
My problem is that I do not know how to change such things. Do you ?
Nathann
--
You received this message because you a
On Monday, May 26, 2014 3:17:18 PM UTC+2, Nathann Cohen wrote:
>
> > Alternatively, build with SAGE_UPGRADING=yes (this will check
> dependencies
> > and reinstall Maxima after ECL has been updated).
>
> What is the reason for not making this the default ?
>
Lazyness?
--
You received this m
> Alternatively, build with SAGE_UPGRADING=yes (this will check dependencies
> and reinstall Maxima after ECL has been updated).
What is the reason for not making this the default ?
Nathann
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To un
Alternatively, build with SAGE_UPGRADING=yes (this will check dependencies
and reinstall Maxima after ECL has been updated).
Peter
Op maandag 26 mei 2014 13:23:37 UTC+1 schreef Nathann Cohen:
>
> > sage -f ecl, followed by sage -f maxima did it for me.
>
> Did the job for me. Thanks ! :-)
>
>
> sage -f ecl, followed by sage -f maxima did it for me.
Did the job for me. Thanks ! :-)
nathann
--
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+
I had the same problem. As I was in no hurry I just did a distclean
(doc-clean was not sufficient).
John
On 26 May 2014 11:58, Ralf Stephan wrote:
> sage -f ecl, followed by sage -f maxima did it for me.
>
> On 26 May 2014 12:41, "Nathann Cohen" wrote:
>>
>> Hello !!
>>
>> With this release I
sage -f ecl, followed by sage -f maxima did it for me.
On 26 May 2014 12:41, "Nathann Cohen" wrote:
> Hello !!
>
> With this release I cannot building the doc ends with this :
>
> [calculus ] Exception occurred:
> [calculus ] File "ecl.pyx", line 337, in sage.libs.ecl.ecl_safe_eval
> (sage/libs/e
> Would need the maxima build log as that kind of stuff means that building
> maxima.fas and
> installing it failed.
O_o
I do not remember the install saying that anything went wrong... O_o
Will give you this asap.
Nathann
--
You received this message because you are subscribed to the Google
Would need the maxima build log as that kind of stuff means that building
maxima.fas and
installing it failed.
Francois
On 26/05/2014, at 22:41, Nathann Cohen wrote:
> Hello !!
>
> With this release I cannot building the doc ends with this :
>
> [calculus ] Exception occurred:
> [calculus ]
Hello !!
With this release I cannot building the doc ends with this :
[calculus ] Exception occurred:
[calculus ] File "ecl.pyx", line 337, in sage.libs.ecl.ecl_safe_eval
(sage/libs/ecl.c:4352)
[calculus ] RuntimeError: ECL says: Module error: Don't know how to REQUIRE
MAXIMA.
[calculus ] The f
23 matches
Mail list logo
