Bug 895022 - Test-Email-0.07 is avaliable
Summary: Test-Email-0.07 is avaliable
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-Test-Email
Version: 19
Hardware: All
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Ralf Corsepius
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-14 10:06 UTC by Account closed by user
Modified: 2013-07-18 17:30 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-07-18 17:30:40 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Account closed by user 2013-01-14 10:06:40 UTC
Revision history for Perl extension Test::Email.

0.07  Oct 23, 2008
    - diag, thanks to Chia-liang Kao

0.06  Jun 27 2007
    - parts_ok
    - mime_type_ok

Comment 1 Petr Pisar 2013-03-11 08:19:31 UTC
Why won't fix? This approach without explanation is not helpful.

Comment 2 Ralf Corsepius 2013-03-11 09:33:23 UTC
I have no idea what has happened to this BZ, nor didn't I close it:
http://lists.fedoraproject.org/pipermail/perl-devel/2013-March/064590.html

Comment 3 Ralf Corsepius 2013-03-11 10:21:12 UTC
OK, this package is in a weird (broken?) state in CPAN:

* cpan-command-line tools report Test-Email-0.04.tar.gz to be the current version.
* http://search.cpan.org reports Test-Email-0.07.tar.gz to be the current version.

That said, unless somebody can come up with a complelling reason to upgrade to 0.07, I'll stay with 0.04.

Comment 4 Fedora End Of Life 2013-04-03 19:41:48 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19


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