Control: blocks -1 by 1092330

On 16.01.25 Damir R. Islamov (da...@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.

Sorry, to say, but currently the only thing you can do is to
downgrade libmimalloc2.0 and put it on hold. apt-listbugs could be
helpful with pinning.

Hilmar

Attachment: signature.asc
Description: PGP signature

Reply via email to