Bug 1431128 - Upgrade perl-Mail-Box to 3.002
Summary: Upgrade perl-Mail-Box to 3.002
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-Mail-Box
Version: 26
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1420100
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-10 12:38 UTC by Jitka Plesnikova
Modified: 2017-06-09 19:23 UTC (History)
5 users (show)

Fixed In Version: perl-Mail-Box-3.002-1.fc26
Clone Of:
Environment:
Last Closed: 2017-06-09 19:23:40 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Jitka Plesnikova 2017-03-10 12:38:03 UTC 
Latest Fedora delivers version 2.120. Upstream released 3.001. When you have free time, please upgrade it.

Also please consider enabling release monitoring <https://admin.fedoraproject.org/pkgdb/package/rpms/perl-Mail-Box/> to receive notifications about new versions automatically.
Comment 1 Petr Pisar 2017-04-06 13:13:01 UTC 
There is 3.002 version.
Comment 2 Fedora Update System 2017-06-02 14:32:13 UTC 
perl-Mail-Transport-3.000-2.fc26 perl-Mail-Box-3.002-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-fda53d1ef7
Comment 3 Fedora Update System 2017-06-04 19:41:12 UTC 
perl-Mail-Box-3.002-1.fc26, perl-Mail-Transport-3.000-2.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-fda53d1ef7
Comment 4 Fedora Update System 2017-06-09 19:23:40 UTC 
perl-Mail-Box-3.002-1.fc26, perl-Mail-Transport-3.000-2.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.