Hi, I renamed libapreq2.so.3.8.1 which came with the Debian package libapache2-mod-apreq2 (2.17, buggy as we know),
I recompiled libapreq2.so.3.8.1 from svn trunk, and re-linked libapreq2.so.3 to it; the install script in trunk failed so I simply copied the file into the proper directory Here is the result : ls -l /usr/lib/x86_64-linux-gnu/libapreq2.so.3* lrwxrwxrwx 1 root root 18 Feb 25 15:00 /usr/lib/x86_64-linux-gnu/libapreq2.so.3 -> libapreq2.so.3.8.1 -rwxr-xr-x 1 root root 235328 Nov 27 18:13 /usr/lib/x86_64-linux-gnu/libapreq2.so.3.8.1 -rw-r--r-- 1 root root 63400 Jun 17 2023 /usr/lib/x86_64-linux-gnu/libapreq2.so.3.8.1.dpkg-old After running apt upgrade, I sometimes find that libapreq2.so.3 points to the renamed, old libapreq2.so.3.8.1 : ls -l /usr/lib/x86_64-linux-gnu/libapreq2.so.3* lrwxrwxrwx 1 root root 27 Mar 16 23:35 /usr/lib/x86_64-linux-gnu/libapreq2.so.3 -> libapreq2.so.3.8.1.dpkg-old -rwxr-xr-x 1 root root 235328 Nov 27 18:13 /usr/lib/x86_64-linux-gnu/libapreq2.so.3.8.1 -rw-r--r-- 1 root root 63400 Jun 17 2023 /usr/lib/x86_64-linux-gnu/libapreq2.so.3.8.1.dpkg-old The last upgrade to cause the re-linking only involved libuv1; I noticed this line in the messages, following unpacking : Processing triggers for libc-bin (2.36-9+deb12u4) ... Not sure if this is related? Does anyone have an idea of what causes this? -- Bien à vous, Vincent Veyron https://marica.fr Logiciel de gestion des contentieux juridiques, des contrats et des sinistres d'assurance