Bug 907775 - overload arg '+0' is invalid at /usr/share/perl5/vendor_perl/Mail/Message/Field.pm line 29.
Summary: overload arg '+0' is invalid at /usr/share/perl5/vendor_perl/Mail/Message/Fie...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-Mail-Box
Version: 18
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-05 09:05 UTC by Robert Binkhorst
Modified: 2014-02-05 23:25 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-05 23:25:46 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Robert Binkhorst 2013-02-05 09:05:24 UTC
Description of problem:
When calling notmuch in F18 I get the following error:
overload arg '+0' is invalid at /usr/share/perl5/vendor_perl/Mail/Message/Field.pm line 29.

This comes from /usr/share/perl5/vendor_perl/Mail/Message/Field.pm:
     23 use overload
     24     qq("") => sub { $_[0]->unfoldedBody }
     25  , '+0'   => sub { $_[0]->toInt || 0 }
     26  , bool   => sub {1}
     27  , cmp    => sub { $_[0]->unfoldedBody cmp "$_[1]" }
     28  , '<=>'  => sub { $_[2] ? $_[1] <=> $_[0]->toInt : $_[0]->toInt <=> $_[1] }
     29  , fallback => 1;


Version-Release number of selected component (if applicable):
perl-Mail-Box-2.102-4.fc18.noarch

How reproducible:
Configure notmuch and mutt, then call notmuch.

Steps to Reproduce:
1. Configure notmuch with mutt as per: http://upsilon.cc/~zack/blog/posts/2011/01/how_to_use_Notmuch_with_Mutt/
2. Call notmuch
3.
  
Actual results:

Error is thrown:
overload arg '+0' is invalid at /usr/share/perl5/vendor_perl/Mail/Message/Field.pm line 29.

However notmuch seems to function much as before.

Expected results:

No error should be thrown.

Additional info:

Comment 1 Tom "spot" Callaway 2013-02-05 16:02:16 UTC
Pretty sure this is fixed in the update I just pushed a few days ago:

https://admin.fedoraproject.org/updates/FEDORA-2013-1833/perl-Mail-Box-2.107-1.fc18

Please test and let me know if it is not (and give +1 karma if it is).

Comment 3 Fedora End Of Life 2013-12-21 15:53:04 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2014-02-05 23:25:46 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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