- Package:
- release.debian.org
- Source:
- release.debian.org
- Submitter:
- Andrius Merkys
- Date:
- 2026-11-11 10:07:02 UTC
- Severity:
- normal
- Tags:
Hello, I want to request binNMU of coot to rebuild it against librdkit-dev >= 202603.2-1: nmu coot_1.1.18+dfsg-5 . amd64 arm64 loong64 ppc64el riscv64 . unstable . -m "Rebuild with librdkit-dev >= 202603.2-1" Thanks, Andrius
Why is the rebuild needed? Cheers
Hi, I expect this is in reaction to bug #1139447 with is about rdkit not migrating (due to autopkgtest regression). Looking in the log I see: 69s /usr/libexec/coot-1: symbol lookup error: /usr/lib/x86_64-linux-gnu/coot/libcoot-lidia-core.so.0: undefined symbol: _ZN5RDKit17common_properties8_CIPRankB5cxx11E Usually that means an ABI breakage and rebuilds paper over that. Paul
Hi, Paul is right, there was an ABI breakage in rdkit, rebuilding coot will cure its autopkgtests and allow rdkit to migrate. Andrius
No, this will only paper over the issue in rdkit (as Paul also said). ABI breakage in rdkit needs to be fixed in rdkit. Cheers
This needs to be fixed in rdkit, reassigning.
Hi, https://github.com/rdkit/rdkit/pull/8765#issuecomment-5114438834 But I am wondering what to do here in case upstream is not planning to bump their API, it has been a while and we shipped a few releases with the dropped/renamed(?) symbols. I guess the options are: 1. Hold our nose, rebuild coot as requested and add versioned deps. Are there any other reverse deps of librdkit1t64? I don't think so. 2. Bump librdkit1t64 to librdkit1d (would that work? do we need something like librdkit1z to sort after 1t64?). 3. Drop the shared libraries, because we are dealing with scientific software. I'll see what the rdkit guys say first. Michael
Hi, That was fast: |we do not guarantee ABI stability from one release to the next. One |should assume that dependencies that link against RDKit shared libs will |need to be rebuilt against a new RDKit release. Code changes should, |however, generally not be required. Any time that is the case, it will |be covered in the release notes So I guess we should go with option 3 above? Michael
Hi, Seems so. We will have to switch to static libraries in bin:librdkit-dev, and, in turn, adapt src:coot and src:votca to use them. Andrius
Hello, Bug #1138824 in rdkit reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debichem-team/rdkit/-/commit/0354a5d6a5b8c90da52a50225db76f05c5dd0c6b (this message was generated automatically) -- Greetings https://bugs.debian.org/1138824
Hello, I created branch 'switch-to-static' on Salsa to attempt switching rdkit to static libraries only. I successfully replaced dynamic libraries with static ones and made postgres cartridge link statically. What I wasn't able to do is to switch to static linking in Python bindings. Hence tag:help. Best, Andrius
Hello, I have managed to switch rdkit to static-only libraries in branch 'switch-to-static' on Salsa. The package is uploaded to experimental for trying it out. Most of the packages depending on python3-rdkit rebuild as before. Only two packages declare dependency on librdkit-dev: coot and votca. The latter, src:votca, does not seem to need this dependency in first place (#1149310), but there are problems with src:coot which fails by complaining about faulty rdkit-targets.cmake. This is most likely true as I did not inspect the installed *.cmake definitions - will do it when I have time. I would like to ask the co-maintainers to review the resulting package in experimental. Are my changes OK, does the package look maintainable? I had to patch the buildsystem a bit to statically link python wrappers, but the patch is rather small. Best, Andrius
Hello, Recently version 202609.1 has been released and I had to update rdkit to it in order to make it build with the newest boost. Alas, my branch with static libraries no longer builds when updated to 202609.1. I am investigating the issue at the moment. Andrius
We believe that the bug you reported is fixed in the latest version of rdkit, 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 1138824@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrius Merkys <merkys@debian.org> (supplier of updated rdkit 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 ftpmaster@ftp-master.debian.org) Format: 1.8 Date: Wed, 11 Nov 2026 04:41:19 -0500 Source: rdkit Architecture: source Version: 202609.1-2 Distribution: unstable Urgency: medium Maintainer: Debichem Team <debichem-devel@lists.alioth.debian.org> Changed-By: Andrius Merkys <merkys@debian.org> Closes: 1138824 Changes: rdkit (202609.1-2) unstable; urgency=medium . [ Christoph Berg ] * Fix passing Python_EXECUTABLE to cmake invocations. . [ Andrius Merkys ] * Drop shared library (Closes: #1138824) Checksums-Sha1: 37f916e5859004720c52d658677bca1104942ebe 2496 rdkit_202609.1-2.dsc 00f96f5f07bded11219fc0e9871f281fd5dc54ec 51012 rdkit_202609.1-2.debian.tar.xz 52ba3f2f502fc36ed5ec8d92da1b58423dcf5663 17844 rdkit_202609.1-2_source.buildinfo Checksums-Sha256: 990b621348a80bb3212019d5952584bdf0db7bf84f280d317c6d7e4d69512d15 2496 rdkit_202609.1-2.dsc 3d0acae1127802d5f83c00c3899d5978f48963a043a5a8d9f849f2fe9554b4d0 51012 rdkit_202609.1-2.debian.tar.xz eb63f3dd97400256c9b0a460e341a87fe41d0a2388a4b92a07ca72cbf5bc3542 17844 rdkit_202609.1-2_source.buildinfo Files: 7022850787da70e7e63f104406227215 2496 science optional rdkit_202609.1-2.dsc cd155ce9a259160bd490c617341d340a 51012 science optional rdkit_202609.1-2.debian.tar.xz 5964aa4866912a172c30772b88b0e35c 17844 science optional rdkit_202609.1-2_source.buildinfo -----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQQ9mT++eHAQdiuDyvHYokBlilUePQUCavQ6qAAKCRDYokBlilUe PQcXAP0WuROQifHk503I/I+9hh+lfnkLFDC3ofBhaN8IRRVlTAEA8xF5ILIcbUTc Or0/YZ74QHlpBJw9xRj2lfrEzV4wrwY= =Li7c -----END PGP SIGNATURE-----