Your message dated Sun, 28 Jul 2024 23:55:07 +0200 with message-id <[email protected]> and subject line fortunes: Symbol Lookup Error for rpl_malloc has caused the Debian Bug report #1076370, regarding fortunes: Symbol Lookup Error for rpl_malloc 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.) -- 1076370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076370 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: fortunes Version: 1:1.99.1-7.3 Severity: grave Justification: renders package unusable Dear Maintainer, today I ran a full upgrade of my Debian Testing as part of my daily routine. Since then, I cannot run `fortune` anymore. The error message I get is fortune: symbol lookup error: /lib/x86_64-linux-gnu/librecode.so.0: undefined symbol: rpl_malloc I tried to uninstall and then reinstall `fortunes` and `fortunes-de`, but to no avail. Obviously, I'd expect fortunes to work. In particular, I am worried about the lookup error. I wouldn't be surprised if the issue belongs to a different package, but I did not know which. Best -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.9.9-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fortunes depends on: ii fortunes-min 1:1.99.1-7.3 Versions of packages fortunes recommends: ii fortune-mod 1:1.99.1-7.3 fortunes suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Version: 3.6-29 This was fixed in that version, but forgot to close the bug. Thanks.
--- End Message ---
