Bug 1304362 - perl-Verilog-Perl-3.418 is available
perl-Verilog-Perl-3.418 is available
Product: Fedora
Classification: Fedora
Component: perl-Verilog-Perl (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Jitka Plesnikova
Fedora Extras Quality Assurance
: FutureFeature, Triaged
Depends On:
  Show dependency treegraph
Reported: 2016-02-03 07:19 EST by Upstream Release Monitoring
Modified: 2016-02-03 10:34 EST (History)
3 users (show)

See Also:
Fixed In Version: perl-Verilog-Perl-3.418-1.fc24
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-02-03 10:34:32 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
[patch] Update to 3.418 (#1304362) (906 bytes, patch)
2016-02-03 07:20 EST, Upstream Release Monitoring
no flags Details | Diff

  None (edit)
Description Upstream Release Monitoring 2016-02-03 07:19:53 EST
Latest upstream release: 3.418
Current version/release in rawhide: 3.416-1.fc24
URL: http://search.cpan.org/dist/Verilog-Perl/

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

Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.
Comment 1 Upstream Release Monitoring 2016-02-03 07:20:13 EST
Created attachment 1120735 [details]
[patch] Update to 3.418 (#1304362)
Comment 2 Upstream Release Monitoring 2016-02-03 07:32:59 EST
Scratch build completed http://koji.fedoraproject.org/koji/taskinfo?taskID=12801629

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