Bug 1653175
Summary: | Upgrade perl-Git-Repository to 1.323 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jitka Plesnikova <jplesnik> |
Component: | perl-Git-Repository | Assignee: | Jan Pazdziora <jpazdziora> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | iarnell, jpazdziora, perl-devel, ppisar, rbarlow |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-12-11 17:04:09 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
Jitka Plesnikova
2018-11-26 07:31:51 UTC
Thanks for the notice. Any idea what happened to the upstream release monitoring which used to file these bugzillas in the past? This package has monitoring: monitoring-with-scratch in https://pagure.io/releng/fedora-scm-requests/blob/master/f/rpms/perl-Git-Repository and https://fedoraproject.org/wiki/Upstream_release_monitoring is not very explicit in explaining whether that is the correct setup ... perl-Git-Repository-1.323-1.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-c02d63449d perl-Git-Repository-1.323-1.fc29 has been pushed to the Fedora 29 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-2018-c02d63449d A Fedora update associated with this bug has been pushed to the stable repository. A Fedora update associated with this bug has been pushed to the stable repository. |