On Tuesday, May 27, 2014 6:02:20 AM UTC+2, Ralf Stephan wrote:
>
> 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.
>
That's basically what sertting SAGE_UPGRADING=yes would do.
The problem is that it may not be necessary if the new ecl was binary 
compatible (if fthat makes sense for lisp stuff) with the previous one.
And as William (IIRC...) ranted, it would also trigger a rebuild of ATLAS 
in case python was itself updated because python is needed to interpret 
ATLAS's spkg-install.

Or you meant, that the one who updated ECL should have updated Maxima's 
package-version.txt?

> Regards, 
> On 26 May 2014 18:00, "Volker Braun" <vbrau...@gmail.com <javascript:>> 
> wrote:
>
>> 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). 
>>
>>
>>
>> On Monday, May 26, 2014 3:23:32 PM UTC+1, Jean-Pierre Flori wrote:
>>>
>>>
>>>
>>> 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.
>>>
>>  -- 
>> 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...@googlegroups.com <javascript:>.
>> To post to this group, send email to sage-r...@googlegroups.com<javascript:>
>> .
>> Visit this group at http://groups.google.com/group/sage-release.
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Reply via email to