@DavidCarlisle ;-). Why do I get hyperref test failures from xetex test? Did something change in the build.lua? The one test can never have worked with this engine.
@DavidCarlisle yes but the failures are quite expected with xetex. The question is why suddenly xetex is used here. Somehow the checkengines setting has been commented.
@UlrikeFischer oh it's OK,, see the log updates to doc and build after comments from @pablgonz we can blame @PabloGonzálezL
@UlrikeFischer it was using a shell script for the build and just used l3build for checking but now it uses l3build for building as well but something must have slipped.
@UlrikeFischer see the block commented as -- temp settings disable checks while testing ctan build that was supposed to be temporary settings while getting the new build code working (skipping checks) it's only been partially reverted but it should all be deleted now)
@UlrikeFischer You really can't trust @JosephWright he's always breaking tests
@DavidCarlisle lots of failures now in the pdf-tests because of the change in the font numbering. I will recreate them in the afternoon. Have to do some shopping now.
> The Globe ran out of room for its obituaries on Sunday, and had to modify the layout for the paper. "We said, ‘Twenty pages — that’s got to be enough; there’s no way it’s going to go over that. And then to see that it went over. . . it’s terrifying.”
@AlanMunn That would be a problem. Given the complete lack of usefulness of the CapsLock, I remapped it to Compose ;-) --- I'd have problems even to reboot with that one stuck.
@HaraldHanche-Olsen I wrote all my Fortran code in lower case, and freaked out all the engineers I worked with. :) I took a course in COBOL once, but that was all on punch cards.