On 20 April 2017 at 16:25, Scott Kostyshak <[email protected]> wrote: > On Thu, Apr 20, 2017 at 12:23:25PM +0200, Robert Alessi wrote: > > On Thu, Apr 20, 2017 at 10:50:14AM +0100, David Carlisle wrote: > > > The sources are updated but not all the binaries are updated yet > (depends > > > on volunteers compiling on each of the platforms) so if you are not > > > compiling from source but using the binaries from the tl2017 pretest > the > > > fix will appear at different times, depending what platform you are > using, > > > could be a few days or weeks, depending on how much time people have to > > > rebuild. > > > Many thanks, I was not aware of that. As this is fixed, and no > > further testing is required, I think I'll just wait for the updated > > binaries to arrive (32-bit Linux in my case). > > Indeed, good to know, David. Is there a way (e.g. a URL) to check when > this happens? I'm more curious about this in general, not for this > specific issue. >
well for example I use cygwin as a rule and https://www.tug.org/svn/texlive/trunk/Master/bin/x86_64-cygwin/?sortby=date currently shows luatex hasn't changed, whereas linux 64 https://www.tug.org/svn/texlive/trunk/Master/bin/x86_64-linux/?sortby=date shows that the new luatex binary was committed a couple of hours ago. > > And thanks to Robert for testing. > > Scott > David
