Bug 1931611
| Summary: | log4cplus-2.0.7 is available | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> | ||||
| Component: | log4cplus | Assignee: | Martin Osvald 🛹 <mosvald> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | rawhide | CC: | olysonek-foss, pzhukov, zdohnal | ||||
| Target Milestone: | --- | Keywords: | FutureFeature, Triaged | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | log4cplus-2.0.7-1.fc35 log4cplus-2.0.7-1.fc36 | Doc Type: | --- | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2022-06-11 01:41:52 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: | |||||||
| Attachments: |
|
||||||
|
Description
Upstream Release Monitoring
2021-02-22 19:19:01 UTC
Created attachment 1758669 [details]
[patch] Update to 2.0.6 (#1931611)
the-new-hotness/release-monitoring.org's scratch build of log4cplus-2.0.6-1.fc32.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=62529565 This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component. Latest upstream release: 2.0.7 Current version/release in rawhide: 2.0.5-14.fc35 URL: http://sourceforge.net/projects/log4cplus Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/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/1835/ An unexpected error occurred while creating the scratch build and has been automatically reported. Sorry! This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component. FEDORA-2022-b3af0be9ba has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-b3af0be9ba FEDORA-2022-0447cbdc90 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-0447cbdc90 FEDORA-2022-b3af0be9ba has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-b3af0be9ba` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-b3af0be9ba See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-0447cbdc90 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-0447cbdc90` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-0447cbdc90 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-0447cbdc90 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-b3af0be9ba has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report. |