Bug#1009367: libnss3 file location changes
On Tue, Apr 19, 2022 at 2:15 PM Stephan Verbücheln wrote: > > Another hint: > > There are hardcoded paths in the following file: > ~/.pki/nssdb/pkcs11.txt > > e.g.: > > library=/usr/lib/x86_64-linux-gnu/nss/libnssckbi.so > > To me it is not clear who creates that file, nss or evolution. I believe libnss3 creates that file and needs to be able to handle it. libnss3 might need to add a symlink directory to handle the old name. I'm uploading a new evolution version and closing this bug. Backup that file. If you still have the bug with evolution 3.44.1-2 with that file (but not with that file moved or removed), I recommend filing a serious bug against libnss3. Note this from the debian/changelog for libsnss3 2:3.72-1 * debian/libnss3.lintian-overrides.in, debian/rules, nss/cmd/shlibsign/shlibsign.c, nss/lib/pk11wrap/pk11load.c, nss/lib/util/secload.c, nss/cmd/shlibsign/Makefile, nss/cmd/shlibsign/manifest.mn: Stop putting freebl, softokn, etc. in a subdirectory. It's a deviation from upstream that is causing more problems than it's worth keeping. Closes: #737855, #846012, #979159. Thanks, Jeremy Bicha
Bug#1009367: libnss3 file location changes
On Sat, Apr 23, 2022 at 6:48 AM Stephan Verbücheln wrote: > This patch is probably also related: > https://sources.debian.org/patches/evolution/3.44.1-1/02_nss_paths.patch/ I guess I'll just drop that patch then. Thank you, Jeremy Bicha
Bug#1009367: libnss3 file location changes
This patch is probably also related: https://sources.debian.org/patches/evolution/3.44.1-1/02_nss_paths.patch/ Regards
Bug#1009367: libnss3 file location changes
Another hint: There are hardcoded paths in the following file: ~/.pki/nssdb/pkcs11.txt e.g.: > library=/usr/lib/x86_64-linux-gnu/nss/libnssckbi.so To me it is not clear who creates that file, nss or evolution. Regards
Bug#1009367: libnss3 file location changes
Control: affects -1 src:nss On Tue, Apr 19, 2022 at 6:09 AM Stephan Verbücheln wrote: > Further analysis shows that it is related to changed file locations > between the libnss3 versions. Some files were moved out of the nss > directory. Would rebuilding evolution fix this issue? There will be a new evolution release on Friday anyway. If it does fix the issue, then maybe we would need to rebuild some or all of the nss reverse dependencies. Thank you, Jeremy Bicha
Bug#1009367: libnss3 file location changes
Further analysis shows that it is related to changed file locations between the libnss3 versions. Some files were moved out of the nss directory. Files in stable (libnss3 2:3.61-1+deb11u2): /usr/lib/x86_64-linux-gnu/libnss3.so /usr/lib/x86_64-linux-gnu/libnssutil3.so /usr/lib/x86_64-linux-gnu/libsmime3.so /usr/lib/x86_64-linux-gnu/libssl3.so /usr/lib/x86_64-linux-gnu/nss/libfreebl3.chk /usr/lib/x86_64-linux-gnu/nss/libfreebl3.so /usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.chk /usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.so /usr/lib/x86_64-linux-gnu/nss/libnssckbi.so /usr/lib/x86_64-linux-gnu/nss/libnssdbm3.chk /usr/lib/x86_64-linux-gnu/nss/libnssdbm3.so /usr/lib/x86_64-linux-gnu/nss/libsoftokn3.chk /usr/lib/x86_64-linux-gnu/nss/libsoftokn3.so /usr/share/doc/libnss3/changelog.Debian.gz /usr/share/doc/libnss3/copyright /usr/share/lintian/overrides/libnss3 Files in unstable (libnss3 2:3.77-1): /usr/lib/x86_64-linux-gnu/libfreebl3.chk /usr/lib/x86_64-linux-gnu/libfreebl3.so /usr/lib/x86_64-linux-gnu/libfreeblpriv3.chk /usr/lib/x86_64-linux-gnu/libfreeblpriv3.so /usr/lib/x86_64-linux-gnu/libnss3.so /usr/lib/x86_64-linux-gnu/libnssckbi.so /usr/lib/x86_64-linux-gnu/libnssdbm3.chk /usr/lib/x86_64-linux-gnu/libnssdbm3.so /usr/lib/x86_64-linux-gnu/libnssutil3.so /usr/lib/x86_64-linux-gnu/libsmime3.so /usr/lib/x86_64-linux-gnu/libsoftokn3.chk /usr/lib/x86_64-linux-gnu/libsoftokn3.so /usr/lib/x86_64-linux-gnu/libssl3.so /usr/share/doc/libnss3/changelog.Debian.gz /usr/share/doc/libnss3/copyright /usr/share/lintian/overrides/libnss3 QUICK FIX Manually creating a nss directory with symlinks to the shared objects appears to fix the problem. However, that is not a good solution as it could have undesired side effects. I am not sure whether it is the job for libnss3 or evolution maintainers to fix this. Regards
