Bug 1624360
Summary: | perl-Redis-1.991-7.fc29 FTBFS: Failed test 'pipeline with embedded error' | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Petr Pisar <ppisar> |
Component: | perl-Redis | Assignee: | Petr Pisar <ppisar> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 28 | CC: | ddick, perl-devel, rbarlow |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
URL: | https://apps.fedoraproject.org/koschei/build/5187887 | ||
Whiteboard: | |||
Fixed In Version: | perl-Redis-1.991-8.fc30 perl-Redis-1.991-6.fc28 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-05-14 01:06:02 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Petr Pisar
2018-08-31 10:41:46 UTC
From redis changelog <https://raw.githubusercontent.com/antirez/redis/4.0/00-RELEASENOTES>: Oran Agra in commit 9535c215: fix rare replication stream corruption with disk-based replication 3 files changed, 19 insertions(+), 9 deletions(-) Redis git tree <https://github.com/antirez/redis/commit/9535c215> confirms the error message has changed. Perl Redis upstream committed <https://github.com/PerlRedis/perl-redis/commit/b811af28608320a362bf330dc1a60ef13bd0cae3> a fix <https://github.com/PerlRedis/perl-redis/pull/130>. perl-Redis-1.991-8.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-435d42848b perl-Redis-1.991-8.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-435d42848b 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. Fedora 28 is also broken (perl-Redis-1.991-5.fc28). This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. perl-Redis-1.991-6.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2019-08799a600c perl-Redis-1.991-6.fc28 has been pushed to the Fedora 28 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-2019-08799a600c perl-Redis-1.991-6.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report. |