Control: block -1 by 1094177 On 16.01.25 Hilmar Preusse (hille42@web.de) wrote: > On 16.01.25 Damir R. Islamov (damir@secretlaboratory.ru) wrote: Hi Damir, > > $ ldd /usr/bin/luametatex > > linux-vdso.so.1 (0x00007f08df695000) > > libmimalloc.so.2 => not found > > libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f08df57e000) > > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f08df00a000) > > /lib64/ld-linux-x86-64.so.2 (0x00007f08df697000) > > > > luametatex depends on libmimalloc2.0 (>= 2.1.7+ds). > > Current libmimalloc2.0 package ships libmimalloc.so.3, but not libmimalloc.so.2. > > Thus, luametatex should be rebuild against new libmimalloc2.0. > > > > No, that's not how it works. I could trigger a rebuild, but this would > break luametatex for all people, who did not uprade mimalloc to > version 3.0.0. At first the mimalloc people have to sort out the > issue (#1092330 ff.). After libmimalloc3.0 exists I can test if > luametatext works with that version and then trigger an binNMU. > Good news: the mimalloc people did exactly this, there is a libmimalloc3 package now (carrying the libmimalloc.so.3 lib) and I triggered a rebuild using that new libmimalloc3 in #1094177. I did some minimal tests using the libmimalloc3 package and hope that everything works fine. Hilmar
Attachment:
signature.asc
Description: PGP signature