FS#60919 - [netdata] edit-config script (and others) uses wrong prefix

Attached to Project: Community Packages
Opened by Sefa Eyeoglu (Scrumplex) - Tuesday, 27 November 2018, 14:24 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Monday, 25 February 2019, 09:41 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:
The edit-config script located in /etc/netdata handles editing most config files. It should be used in favor of any manual copy operation. But the script provided by the package looks for config files in the wrong prefix. It looks in "/usr/local/etc/netdata" and "/usr/local/lib/netdata/conf.d". This should be changed to "/etc/netdata" and "/usr/lib/netdata/conf.d" respectively.


Additional info:
* package version(s) 1.11.1-1
* config and/or log files etc.


Steps to reproduce:
Run /etc/netdata/edit-config netdata.conf
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Monday, 25 February 2019, 09:41 GMT
Reason for closing:  Fixed
Comment by mpan (mpan) - Wednesday, 09 January 2019, 09:38 GMT
Nearly surely related to issue #61316¹.

¹ https://bugs.archlinux.org/task/61316
Comment by Eli Schwartz (eschwartz) - Friday, 11 January 2019, 04:03 GMT
  • Field changed: Summary ([netdata] edit-config script uses wrong prefix → [netdata] edit-config script (and others) uses wrong prefix)
  • Field changed: Status (Unconfirmed → Assigned)
  • Field changed: Category (Packages → Upstream Bugs)
  • Task assigned to Sven-Hendrik Haase (Svenstaro)
As pointed out in  FS#61316  this is a problem with a number of files provided by the package, and the upstream build system is somehow ignoring the configure options.

Discussion: https://github.com/netdata/netdata/issues/5136
Comment by Adriano Fantini (OdinEidolon) - Tuesday, 22 January 2019, 09:27 GMT
Now fixed according to this:
https://github.com/netdata/netdata/issues/5136

I'm not sure if this will require some modifications of the install scripts.
Comment by Sven-Hendrik Haase (Svenstaro) - Tuesday, 22 January 2019, 13:21 GMT
Nah we just gotta wait for a new netdata release.
Comment by Sven-Hendrik Haase (Svenstaro) - Sunday, 24 February 2019, 09:47 GMT
Should be fixed by new upstream release, please test.
Comment by Adriano Fantini (OdinEidolon) - Sunday, 24 February 2019, 17:48 GMT
Seems fixed to me.

Loading...