Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1776552 - pacemaker-2.0.3 is available
Summary: pacemaker-2.0.3 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: pacemaker
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jan Pokorný [poki]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1777056 1780573 1781205
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-26 00:13 UTC by Upstream Release Monitoring
Modified: 2020-01-16 19:16 UTC (History)
4 users (show)

Fixed In Version: pacemaker-2.0.3-1.fc30 pacemaker-2.0.3-1.fc31
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-01-15 02:10:02 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Upstream Release Monitoring 2019-11-26 00:13:16 UTC 
Latest upstream release: 2.0.3
Current version/release in rawhide: 2.0.3-0.1.rc3.fc32
URL: http://clusterlabs.org/

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/2584/
Comment 1 Upstream Release Monitoring 2019-11-26 00:13:21 UTC 
One or more of the new sources for this package are identical to the old sources. It's likely this package does not use the version macro in its Source URLs. If possible, please update the specfile to include the version macro in the Source URLs
Comment 2 Jan Pokorný [poki] 2019-11-26 20:54:10 UTC 
Waiting on Publican getting fixed on i686 in Rawhide [bug 1777056]
(so as not to break a proper update path for older/stable Fedoras
even if they may have Publican working well there).
Comment 3 Fedora Update System 2020-01-06 21:22:10 UTC 
FEDORA-2020-9ce9a36db2 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-9ce9a36db2
Comment 4 Fedora Update System 2020-01-06 21:22:15 UTC 
FEDORA-2020-a8cb70fff6 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2020-a8cb70fff6
Comment 5 Fedora Update System 2020-01-07 01:08:16 UTC 
pacemaker-2.0.3-1.fc31 has been pushed to the Fedora 31 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-2020-9ce9a36db2
Comment 6 Fedora Update System 2020-01-07 02:40:32 UTC 
pacemaker-2.0.3-1.fc30 has been pushed to the Fedora 30 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-2020-a8cb70fff6
Comment 7 Fedora Update System 2020-01-15 02:10:02 UTC 
pacemaker-2.0.3-1.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.
Comment 8 Fedora Update System 2020-01-16 19:16:26 UTC 
pacemaker-2.0.3-1.fc31 has been pushed to the Fedora 31 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.