Bug 228158 - Mutt was built without LibIDN support
Mutt was built without LibIDN support
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: mutt (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: Miroslav Lichvar
: Reopened
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-02-10 16:47 EST by Robert Scheck
Modified: 2014-07-25 09:09 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-07-25 09:09:25 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Robert Scheck 2007-02-10 16:47:40 EST
Description of problem:
Mutt provides LibIDN support which means umlaut domains/e-mail addresses. 
Please add a BuildRequires: libidn-devel and push a --with-idn to %configure.

Version-Release number of selected component (if applicable):
mutt-1.5.13-1.20070126cvs

Actual results:
Mutt was built without LibIDN support.

Expected results:
Mutt should be built with LibIDN support.
Comment 1 Miroslav Lichvar 2007-02-12 12:44:39 EST
Ok, will be in next release.
Comment 2 Miroslav Lichvar 2007-02-15 11:24:47 EST
Support for libidn enabled in mutt-1.5.13-2.20070212cvs.fc7.
Comment 3 Robert Scheck 2007-02-15 11:31:07 EST
Thank you *very* much! :)
Comment 4 jpacner 2014-07-23 10:08:15 EDT
List of patches present on mutt-1.5.20-6.20091214hg736b6a.el6:
http://pkgs.devel.redhat.com/cgit/rpms/mutt/commit/?h=rhel-6.6&id=2b1e992892699aa337c0ec860bbeb0a4a675704e
Comment 5 Robert Scheck 2014-07-23 12:45:32 EDT
Why has this been reopened?

$ rpm -q --requires mutt-1.5.20-4.20091214hg736b6a.el6_5.x86_64 | grep libidn
libidn.so.11()(64bit)  
libidn.so.11(LIBIDN_1.0)(64bit)  
$
Comment 6 jpacner 2014-07-25 09:09:25 EDT
Let me apologize, it was caused by our update script which accidentaly grabbed a bad bug number.

Note You need to log in before you can comment on or make changes to this bug.