Your message dated Sun, 01 Mar 2026 10:18:26 +0000
with message-id <[email protected]>
and subject line Bug#1129221: fixed in simdjson 4.3.1+really4.2.4-1
has caused the Debian Bug report #1129221,
regarding libsimdjson29: soname changed but package not renamed to libsimdjson30
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1129221: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1129221
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: simdjson
Version: 4.3.1-1
Severity: grave
X-Debbugs-Cc: Jérémy Lal <[email protected]>
Control: affects -1 libsimdjson29 src:thunderbird

https://buildd.debian.org/status/logs.php?pkg=thunderbird&ver=1%3A140.8.0esr-1

...
 0:18.61 checking for nodejs... /usr/bin/node: error while loading shared 
libraries: libsimdjson.so.29: cannot open shared object file: No such file or 
directory
...


Due to:
$ dpkg -L libsimdjson29
...
/usr/lib/x86_64-linux-gnu/libsimdjson.so.30.0.0
...
$

--- End Message ---
--- Begin Message ---
Source: simdjson
Source-Version: 4.3.1+really4.2.4-1
Done: Jérémy Lal <[email protected]>

We believe that the bug you reported is fixed in the latest version of
simdjson, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jérémy Lal <[email protected]> (supplier of updated simdjson package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sun, 01 Mar 2026 11:02:38 +0100
Source: simdjson
Architecture: source
Version: 4.3.1+really4.2.4-1
Distribution: unstable
Urgency: medium
Maintainer: Mo Zhou <[email protected]>
Changed-By: Jérémy Lal <[email protected]>
Closes: 1129221
Changes:
 simdjson (4.3.1+really4.2.4-1) unstable; urgency=medium
 .
   * Reintroduce libsimdjson29 to fix the mess I've made.
     Closes: #1129221
Checksums-Sha1:
 7ca6f17e689854cd2c39bd78fd05b7728b385188 2116 simdjson_4.3.1+really4.2.4-1.dsc
 8b686750ef33af5510d267863ccaa0b71d3adb55 6042123 
simdjson_4.3.1+really4.2.4.orig.tar.gz
 fd5f171a508e0accd6f979489e06bd4d07e95427 6840 
simdjson_4.3.1+really4.2.4-1.debian.tar.xz
 52dfe39ba4bb846b21237ee07a0f71d2f7c8d632 7806 
simdjson_4.3.1+really4.2.4-1_source.buildinfo
Checksums-Sha256:
 389b27997faa69bca29e47e328f0baacc108daafc1b2920544a91cecb57abcb1 2116 
simdjson_4.3.1+really4.2.4-1.dsc
 c5205b260d9fe911f891ca9210040f364c6b12f9aa0c10ff0cad7626fac4ce78 6042123 
simdjson_4.3.1+really4.2.4.orig.tar.gz
 1dd5654786bbd19bc23b3abe70ffa11651483c6a792b99461148802206761112 6840 
simdjson_4.3.1+really4.2.4-1.debian.tar.xz
 49e17ea5fdd1cf6b417c55f50e565866971e0ec88165c92edd552e9d3e71dba0 7806 
simdjson_4.3.1+really4.2.4-1_source.buildinfo
Files:
 750581fb36993828b7b4ec9de62a0275 2116 libs optional 
simdjson_4.3.1+really4.2.4-1.dsc
 77ac0700a6122ecaa8f328ac6338d2ab 6042123 libs optional 
simdjson_4.3.1+really4.2.4.orig.tar.gz
 70c43d349d49808280acca07dfa7a4da 6840 libs optional 
simdjson_4.3.1+really4.2.4-1.debian.tar.xz
 9dbe805626d2367e4e6e5ee2d437c405 7806 libs optional 
simdjson_4.3.1+really4.2.4-1_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJGBAEBCAAwFiEEA8Tnq7iA9SQwbkgVZhHAXt0583QFAmmkD54SHGthcG91ZXJA
bWVsaXgub3JnAAoJEGYRwF7dOfN0mjwP/Rw+wJKs0MSWgehYHBIcLGuUwts93h3h
iSzyUthKoYSLpbeWCg8t5R9d7uNKDRo+17AzhGx7eexQSDlp5osbdtucsTnHRru/
J41wKKK3ty45+mym/aIoHWYkh+hyW/nGGRDY3cGnB7scI1+PF8DUhBfpw9BPjKBb
7W1WzxNNWa0hWVn+YiZVnDAxfe8qyQJkYAA+sUCiTDIItvmDNzdGNGDbH95fnNob
4Nc5AZXSJ9EI+/suL15A5CQl/Qqf5+Xqh6feXqOq9rTOqZd0GZksRFlUb9Y2Gbgj
5j0VtZXCu1c4c7EcaCteONpQxQ+LVRV7nFER3dIhMlImFd5pEVgw4HavsSuOuKMe
j7B4Hs3uK/XHyntcoRAtsQ+/st1i8iPZn//iEhYx7CVG9e4YJC1FBMRwZCXPD53k
8I2mGbWmb8zD/Ra61hfkj5v31KMb7sR5AkH45Mj6FYxSF/GJOqIdwvw3BqkU0fHs
lxwQCmyohCkBRhdfHJCaXj+rEsfRXJgE4SXcPQ4XIAXTpgQCRcN/Ms4uusRe89Mg
DixdvrHSOfCfHdR0PIiZr+/KzGUbLH4MwwxarCY1GJ27c6rdtyRxHbmB8bOwcmeN
iL3OMkUJLYTM9PgwlmK+UazK4Uh08H3y3QWgbaiXF0Fn8C/7LcKD6xbctLJumBie
aP9E3w17d5Le
=uIQU
-----END PGP SIGNATURE-----

Attachment: pgpc8jCv7UCn4.pgp
Description: PGP signature


--- End Message ---

Reply via email to