Bug 1131114
Summary: | qxmpp-v0.9.0 is available | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> |
Component: | qxmpp | Assignee: | Minh Ngo <nlminhtl> |
Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | nlminhtl |
Target Milestone: | --- | Keywords: | FutureFeature, Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | 0.9.2-1.fc23 | Doc Type: | Enhancement |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-09-13 00:49:02 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Upstream Release Monitoring
2014-08-18 13:18:54 UTC
Latest upstream release: 0.8.1 Current version/release in Fedora Rawhide: 0.7.5-5.fc22 URL: https://api.github.com/repos/qxmpp-project/qxmpp/tags 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 Soon this service will be implemented by a new system: https://release-monitoring.org/ It will require to manage monitored projects via a new web interface. Please make yourself familiar with the new system to ease the transition. Latest upstream release: 0.8.2 Current version/release in Fedora Rawhide: 0.7.5-5.fc22 URL: https://api.github.com/repos/qxmpp-project/qxmpp/tags 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 Soon this service will be implemented by a new system: https://release-monitoring.org/ It will require to manage monitored projects via a new web interface. Please make yourself familiar with the new system to ease the transition. Latest upstream release: v0.9.0 Current version/release in rawhide: 0.7.5-7.fc23 URL: https://github.com/qxmpp-project/qxmpp 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. Failed to kick off scratch build. cmd: sha256sum /var/tmp/thn-Pos913/100.0% return code: 1 stdout: stderr: sha256sum: /var/tmp/thn-Pos913/100.0%: No such file or directory qxmpp-0.9.0-1.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2015-14548 qxmpp-0.9.0-1.fc21 has been submitted as an update to Fedora 21. https://bodhi.fedoraproject.org/updates/FEDORA-2015-14549 qxmpp-0.9.0-1.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2015-14550 qxmpp-0.9.0-1.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report.\nIf you want to test the update, you can install it with \n su -c 'yum --enablerepo=updates-testing update qxmpp'. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-14548 qxmpp-0.9.0-1.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.\nIf you want to test the update, you can install it with \n su -c 'yum --enablerepo=updates-testing update qxmpp'. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-14550 qxmpp-0.9.0-1.fc21 has been pushed to the Fedora 21 testing repository. If problems still persist, please make note of it in this bug report.\nIf you want to test the update, you can install it with \n su -c 'yum --enablerepo=updates-testing update qxmpp'. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-14549 qxmpp-0.9.2-1.fc21 has been pushed to the Fedora 21 testing repository. If problems still persist, please make note of it in this bug report.\nIf you want to test the update, you can install it with \n su -c 'yum --enablerepo=updates-testing update qxmpp'. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-14946 qxmpp-0.9.2-1.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report.\nIf you want to test the update, you can install it with \n su -c 'yum --enablerepo=updates-testing update qxmpp'. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-14947 qxmpp-0.9.2-1.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.\nIf you want to test the update, you can install it with \n su -c 'yum --enablerepo=updates-testing update qxmpp'. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-14945 qxmpp-0.9.2-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report. qxmpp-0.9.2-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report. qxmpp-0.9.2-1.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report. |