Description of problem: Netdata ships a v2 dashboard (loaded by default via cdn, and shipped as fallback from built files in https://github.com/netdata/netdata/tree/master/src/web/gui/v2 ) that is built in private and with no source available. It either needs the v2 dashboard stripped for fedora builds, or not be included (since the firmware criteria is not met). Version-Release number of selected component (if applicable): all since v2 dashboard ships How reproducible: 100% Steps to Reproduce: 1. install netdata 2. open it and observe being able to use `/v2` (local copy of the built blobs) and it shipping the cdn edition on `/` Actual results: I get closed source code code from files installed on my disk. Expected results: Only `/v1` should work under fedora, or netdata should not be in the repos. Additional info: I opened a Pull/Consideration Request at https://github.com/netdata/netdata/pull/18319 for them to label this clearly or provide a FLOSS only build.
Note: a similar bug report exists for debian at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054354
Opensuse has patched this now for their distribution (removal of v2, defaulting to v1 on /), a similar patch could be adopted for fedora & co? https://bugzilla.opensuse.org/show_bug.cgi?id=1229119
FEDORA-2024-e46059b3ef (netdata-1.46.3-4.fc39) has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2024-e46059b3ef
FEDORA-2024-a22c307c0d (netdata-1.46.3-4.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-a22c307c0d
FEDORA-EPEL-2024-0e18547512 (netdata-1.46.3-4.el8) has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-0e18547512
FEDORA-EPEL-2024-73c7ba7318 (netdata-1.46.3-4.el9) has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-73c7ba7318
FEDORA-EPEL-2024-73c7ba7318 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-73c7ba7318 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2024-0e18547512 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-2024-0e18547512 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-e46059b3ef has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-e46059b3ef` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-e46059b3ef See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-a22c307c0d has been pushed to the Fedora 40 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-a22c307c0d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-a22c307c0d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2024-73c7ba7318 (netdata-1.46.3-4.el9) has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2024-e46059b3ef (netdata-1.46.3-4.fc39) has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2024-0e18547512 (netdata-1.46.3-4.el8) has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2024-a22c307c0d (netdata-1.46.3-4.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.