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. Regards, On 26 May 2014 18:00, "Volker Braun" <vbraun.n...@gmail.com> 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+unsubscr...@googlegroups.com. > To post to this group, send email to sage-rele...@googlegroups.com. > 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-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, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
