Bug 1019134 - perl-Test-Mock-LWP-0.08 is available
Summary: perl-Test-Mock-LWP-0.08 is available
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-Test-Mock-LWP
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-15 08:20 UTC by Upstream Release Monitoring
Modified: 2015-06-24 14:55 UTC (History)
2 users (show)

Fixed In Version: perl-Test-Mock-LWP-0.08-1.fc20
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-24 14:55:42 UTC
Type: ---


Attachments (Terms of Use)

Description Upstream Release Monitoring 2013-10-15 08:20:19 UTC
Latest upstream release: 0.07
Current version/release in Fedora Rawhide: 0.06-7.fc20
URL: http://search.cpan.org/dist/Test-Mock-LWP/

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring

Comment 1 Upstream Release Monitoring 2013-10-20 10:51:05 UTC
Latest upstream release: 0.08
Current version/release in Fedora Rawhide: 0.06-7.fc20
URL: http://search.cpan.org/dist/Test-Mock-LWP/

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring

Comment 2 Upstream Release Monitoring 2015-06-06 06:23:28 UTC
jplesnik's perl-Test-Mock-LWP-0.08-4.fc23 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=642897

Comment 3 Upstream Release Monitoring 2015-06-18 06:37:17 UTC
ausil's perl-Test-Mock-LWP-0.08-5.fc23 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=657451


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