Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#25518 - [heirloom-mailx] throws error when sending mail

Attached to Project: Arch Linux
Opened by Mihael Pranjić (tux) - Thursday, 11 August 2011, 20:37 GMT
Last edited by Stéphane Gaudreault (stephane) - Tuesday, 13 September 2011, 12:31 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Stéphane Gaudreault (stephane)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Using the latest mentioned packages, and trying to send a mail results in following error for me:
error while loading shared libraries: libdb-5.1.so: cannot open shared object file: No such file or directory

Creating a symlink is obviously a bad thing, I still tried linking libdb-5.1 to the existing libdb-5.2.so. Still throws an error as the package is not compiled against that version of the library.
I used the arch rollback machine to find db-5.1.25-1. Installing that version of the package didn't conflict with any other package for me, so using the old version of the core/db package fixes the problem for me.

Most likely heirloom-mailx just needs to be compiled against db-5.2.28

Additional info:
* db 5.2.28-1
* heirloom-mailx 12.5-2


Steps to reproduce:
Use the above mentioned packages in that exact versions. Try sending an email.
This task depends upon

Closed by  Stéphane Gaudreault (stephane)
Tuesday, 13 September 2011, 12:31 GMT
Reason for closing:  No response
Additional comments about closing:  No response from the reporter for a month.
Comment by Stéphane Gaudreault (stephane) - Friday, 12 August 2011, 13:07 GMT
heirloom-mailx is not linked against libdb. The problem might be located elsewhere. What smtp-forwarder are you using ?

Loading...