IRC channel logs
2025-11-27.log
back to list of logs
<ArneBab_>rlb: may there be a leftover folder from the build that was made readonly and now can’t be removed without trickery (because the clean removal step failed)? <tohoyn>civodul: ok. line number is the same. <tohoyn>I can paste some example code where this line causes problems. <tohoyn>The current version of the check triggers an error iff the bytevector is larger than needed. <dsmith>ArneBab_, Nope. Fails without that dir already in place. It's created, populated, made RO, and then the failure. <dsmith>Oh, and Happy Thanksgiving to those who celebrate it <janneke>wouldn't it be nice if in-vicinity supported an arbitrary number of arguments, like say, string-append? <ArneBab_>dsmith: damn, I had hoped that could fix it … <ArneBab_>And happy thanksgiving from me, too! (though I don’t) <rlb>Actually, I might have broken make distcheck when trying to fix something else a bit back. We'll see. <rlb>OK, I'll revert 6bd70136d96e73542e6725bc490199e17f56ee92. At the time, I was surprised by stale versions, and was "fixing" that, but now I see that allowing stale .versions is intentional --- see build-aux/git-version-gen for the expectations. <rlb>civodul: ^ fwiw (I may also see if there's a good place to mention the .version expectations). <rlb>distcheck is fixed - had to fix another couple of bugs (missing bootstrap.am files); I'll push the changes soonish. <rlb>Certainly, though I'm the one who created the most recent issues in the first place :) (e.g. forgot to add srfi-64/automake.scm to SOURCES, etc.) <ArneBab_>You’re doing the work, so I think you’re entitled to make mistakes :-)