Bug#1099185: courier-imap needs rebuild against courier-unicode, links against old libcourier-unicode.so.4

[Andre Naujoks]

Package: courier-imap
Version: 5.2.10+1.3.13-10
Severity: important

Dear Maintainer,

It seems courier-unicode introduced a major version bump in libcourier-unicode.so from 4 to 8.

I got the following line in my logfiles every time I try to access IMAP (journalctl -u courier-imap-ssl.service):
/usr/lib/courier/courier/imaplogin: error while loading shared libraries: libcourier-unicode.so.4: cannot open shared object file: No such file or directory

For now I just symlinked the installed version of libcourier-unicode.so.8 to 4 (ln -s libcourier-unicode.so.8 libcourier-unicode.so.4) and all seems to work for now.

The initial error was thunderbird not being able to interact with the server because of some weird nonsensical invalid certificate error. It turned out it seems to not have gotten the cert from the server at all because of the above error.

Best regards
Andre

Ps.: This report is not done from the machine it occurs on, thus removing package infos below.

[Andre Naujoks]

Control: reassign 1099185 courier-unicode 2.3.1-1

This might be a bug with courier-unicode actually. Lets see if I can
reassign this myself.

The libcourier-unicode4 package needs to either be renamed to
libcourier-unicode8 or the lib (and its so-name) needs to be changed
back to .4

Andre

[Eduard Bloch]

Package: libcourier-unicode4
Version: 2.3.1-1
Followup-For: Bug #1099185
Severity: serious

Maybe we should tag this as release critical and no just "important",
because it does break packages like MAILDROP!

Straight after an apt-get-full-upgrade today:

$ maildrop
maildrop: error while loading shared libraries: libcourier-unicode.so.4: cannot open shared object file: No such file or directory

$ ldd /usr/bin/maildrop
linux-vdso.so.1 (0x00007fafaa714000)
libpcre2-8.so.0 => /lib/x86_64-linux-gnu/libpcre2-8.so.0 (0x00007fafaa5e2000)
libidn2.so.0 => /lib/x86_64-linux-gnu/libidn2.so.0 (0x00007fafaa5af000)
libgdbm.so.6 => /lib/x86_64-linux-gnu/libgdbm.so.6 (0x00007fafaa59b000)
libcourier-unicode.so.4 => not found
libcourierauth.so.0 => /lib/libcourierauth.so.0 (0x00007fafaa589000)
libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fafaa200000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fafaa55a000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fafaa00a000)
libunistring.so.5 => /lib/x86_64-linux-gnu/libunistring.so.5 (0x00007fafa9e22000)
/lib64/ld-linux-x86-64.so.2 (0x00007fafaa716000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fafaa46a000)


Best regards,
Eduard.

-- System Information:
Debian Release: trixie/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'oldoldstable'), (500, 'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.13.1 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libcourier-unicode4 depends on:
ii libc6 2.41-3
ii libgcc-s1 14.2.0-17
ii libstdc++6 14.2.0-17

libcourier-unicode4 recommends no packages.

libcourier-unicode4 suggests no packages.

-- no debconf information

--
SOLDAT: _S_oll _o_hne _l_anges _D_enken _a_lles _t_un.

[Soren Stoutner]

Andre,

This is pretty serious. Thanks for catching it.

I am going to spend some time today figuring out the best way to
handle the problem, but I wanted to respond quickly so that everyone
knows it is being looked at.

[Chris Hofstaedtler]

Control: severity -1 serious

Post by Soren Stoutner
This is pretty serious. Thanks for catching it.

Indeed it it serious. It also violates policy 8.1.
Raising severity, /also/ to prevent testing migration until this is
fixed.

Post by Soren Stoutner
I am going to spend some time today figuring out the best way to
handle the problem, [..]

I assume you already know that you need a trip through binNEW to
introduce libcourier-unicode8, best done via experimental.

In the meantime I suspect people would appreciate a revert of the
existing package in unstable

Best,
Chris

[Soren Stoutner]

Post by Chris Hofstaedtler
Control: severity -1 serious

Post by Soren Stoutner
This is pretty serious. Thanks for catching it.

Indeed it it serious. It also violates policy 8.1.
Raising severity, /also/ to prevent testing migration until this is
fixed.

Indeed. I really shouldn’t have missed the library transition in this upload, but somehow I
did.

Post by Chris Hofstaedtler

Post by Soren Stoutner
I am going to spend some time today figuring out the best way to
handle the problem, [..]

I assume you already know that you need a trip through binNEW to
introduce libcourier-unicode8, best done via experimental.

Yes, I should have an upload prepared for experimental this afternoon.

Post by Chris Hofstaedtler
In the meantime I suspect people would appreciate a revert of the
existing package in unstable

Agreed. I uploaded a reverted version to unstable a few minutes ago.