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 1766668
| Summary: | Netdata package doesn't support dbengine, the now default backend in the upstream code | ||
|---|---|---|---|
| Product: | [Fedora] Fedora EPEL | Reporter: | unixops |
| Component: | netdata | Assignee: | Didier Fabert (tartare) <didier.fabert> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | epel7 | CC: | didier.fabert |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | netdata-1.22.1-3.fc32 netdata-1.22.1-3.fc30 netdata-1.22.1-3.fc31 netdata-1.22.1-3.el8 netdata-1.22.1-3.el7 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-05-26 03:12:33 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: | |||
| Bug Depends On: | 1759510, 1767122, 1767123 | ||
| Bug Blocks: | |||
|
Description
unixops
2019-10-29 15:50:47 UTC
dbengine cannot be enabled in epel8 for now because of missing dependencies. Some needed packages are not yet available: libuv-devel and Judy-devel. I'm waiting (a little) before apply this modifications to all branches. If you cannot wait, I built it with dbengine enabled in my copr: https://copr.fedorainfracloud.org/coprs/tartare/netdata/build/1081316/ for all fedora releases and epel6 and 7 (where I need to add an exception for epel8, which is not wanted for stable packages). Ah makes sense, thanks for the explanation. You're right there are a bunch of -devel packages missing among others after a quick glance. I will make use of the copr repo for now. Blocked by: Judy-devel: https://bugzilla.redhat.com/show_bug.cgi?id=1767122 libuv-devel: https://bugzilla.redhat.com/show_bug.cgi?id=1767123 Depends on epel issues: * Judy-devel: https://pagure.io/epel/issue/92 * libuv-devel: https://pagure.io/epel/issue/64 FEDORA-2020-aeb3b29305 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-aeb3b29305 FEDORA-2020-4d87a62071 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-4d87a62071 FEDORA-2020-c807d02b1f has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2020-c807d02b1f FEDORA-EPEL-2020-c3fca161ee has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-c3fca161ee FEDORA-EPEL-2020-ff11142989 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-ff11142989 FEDORA-2020-aeb3b29305 has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-aeb3b29305` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-aeb3b29305 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-c807d02b1f has been pushed to the Fedora 30 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-c807d02b1f` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-c807d02b1f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-4d87a62071 has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-4d87a62071` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-4d87a62071 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2020-c3fca161ee has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-c3fca161ee See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2020-ff11142989 has been pushed to the Fedora EPEL 7 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-ff11142989 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-aeb3b29305 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2020-c807d02b1f has been pushed to the Fedora 30 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2020-4d87a62071 has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-EPEL-2020-c3fca161ee has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-EPEL-2020-ff11142989 has been pushed to the Fedora EPEL 7 stable repository. If problem still persists, please make note of it in this bug report. |