jaeger changed the topic of #crux-devel to: CRUX (https://crux.nu/) development channel | Logs: https://libera.irclog.whitequark.org/crux-devel/
<farkuhar> heh, void finally got around to rebuilding their texlive package to fix the zlib-1.3 breakage: https://github.com/void-linux/void-packages/issues/45986 Interestingly, our revdep tool does NOT detect the breakage; I only discovered it when trying to run lualatex a few days ago.
<beerman> their texlive 2021? damn.. if a rebuild helps then I can bump the release in a bit.
groovy2shoes has quit [Ping timeout: 260 seconds]
chrcav has quit [Quit: leaving]
<farkuhar> rebuilding texlive will fix it for sure. But I'm curious whether revdep can be improved too, so that it doesn't give false negatives (`revdep -vvv texlive` says everything is ok, even before a rebuild).
<beerman> yeah, absolutely
<beerman> would be great if it can improve that way
groovy2shoes has joined #crux-devel
<ukky> farkuhar: Do you know which texlive binary/library fails at runtime? If you upload a failing binary/library to some host, I can try to reverse-engineer it and try to find why revdep fails
<farkuhar> ukky: The only one I tried (before rebuilding to fix them all) was lualatex (a symlink to /usr/bin/luahbtex). I'd have to downgrade zlib and rebuild texlive in order to produce the failing binary for you, because the old package has since been overwritten.
<ukky> You might have previous release build in texlive port directory, or in PKGMK_PACKAGE_DIR
<farkuhar> nah, I didn't bother to bump the release or to backup the old package. And my CRUX 3.7 system is not old enough to have accumulated builds from previous versions; texlive is on a once-a-year release cycle.
<beerman> this should contain it
<beerman> https://dpaste.org/yRZib can reproduce it
<beerman> https://dpaste.org/z7KbT these are the arara directives used in the document, though it looks like that doesn't matter
<ukky> beerman: 1.3 GiB?
<beerman> yeah
<beerman> that package is a chonkers alright