Bug 1417611

Summary: lua-5.3.4 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: luaAssignee: Tim Niemueller <tim>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: athmanem, drjohnson1, michel, tcallawa, tim
Target Milestone: ---Keywords: FutureFeature, Reopened, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: lua-5.3.4-1.fc25 lua-5.3.4-1.fc24 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-02-22 17:50:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Rebase-helper rebase-helper-debug.log log file. See for details and report the eventual error to rebase-helper https://github.com/phracek/rebase-helper/issues. none

Description Upstream Release Monitoring 2017-01-30 12:16:39 UTC 
Latest upstream release: 5.3.4
Current version/release in rawhide: 5.3.3-4.fc26
URL: http://www.lua.org/ftp/

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.

Based on the information from anitya:  https://release-monitoring.org/project/1847/
Comment 1 Upstream Release Monitoring 2017-01-30 12:17:10 UTC 
Patching or scratch build for lua-5.3.3 failed.
Comment 2 Upstream Release Monitoring 2017-01-30 12:17:13 UTC 
Created attachment 1245878 [details]
Rebase-helper rebase-helper-debug.log log file.
See for details and report the eventual error to rebase-helper https://github.com/phracek/rebase-helper/issues.
Comment 3 Upstream Release Monitoring 2017-01-30 12:17:16 UTC 
Patches were not touched. All were applied properly
Comment 4 Upstream Release Monitoring 2017-02-09 15:20:54 UTC 
spot's lua-5.3.4-1.fc26 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=839724
Comment 5 Fedora Update System 2017-02-09 15:38:34 UTC 
lua-5.3.4-1.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-1621800cc4
Comment 6 Fedora Update System 2017-02-09 15:38:42 UTC 
lua-5.3.4-1.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2017-85415b3949
Comment 7 Fedora Update System 2017-02-10 00:50:46 UTC 
lua-5.3.4-1.fc25 has been pushed to the Fedora 25 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-1621800cc4
Comment 8 Fedora Update System 2017-02-10 14:23:06 UTC 
lua-5.3.4-1.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.
Comment 9 Fedora Update System 2017-02-10 15:47:26 UTC 
lua-5.3.4-1.fc24 has been pushed to the Fedora 24 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-85415b3949
Comment 10 Fedora Update System 2017-02-22 17:50:55 UTC 
lua-5.3.4-1.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.