netdata package maintainers

Created on 5 Jul 2016 · 95Comments · Source: netdata/netdata

This issue has been converted to a wiki page

For the latest info check it here: https://github.com/firehol/netdata/wiki/netdata-package-maintainers

I think it would be useful to prepare a wiki page with information about the maintainers of netdata for the Linux distributions, automation systems, containers, etc.

Let's see who is who:

Official Linux Distributions

FreeBSD

System|Initial PR|Core Developer|Package Maintainer
|:-:|:-:|:-:|:-:|
FreeBSD|#1321|@vlvkobal|@mmokhi

MacOS

System|URL|Core Developer|Package Maintainer
|:-:|:-:|:-:|:-:|
MacOS Homebrew Formula|link|@vlvkobal|@rickard-von-essen

Unofficial Linux Packages

Embedded Linux

Linux Containers

| Containers | Netdata Version | Maintainer | Related URL |
| :-: | :-: | :-: | :-- |
| Docker | Git | @titpetric | https://github.com/titpetric/netdata |

Automation Systems

If you know other maintainers of distributions that should be mentioned, please help me complete the list...

cc: @mcnewton @philwhineray @alonbl @simonnagl @paulfantom

aredocs arepackaging

Source

ktsaou

👍2

Most helpful comment

1.8.0 is up in debian shortly: https://tracker.debian.org/news/873552

lhw on 19 Sep 2017

🎉2 👍2

All 95 comments

You can set the "Related URL" for Gentoo to https://github.com/gentoo/gentoo/tree/master/net-analyzer/netdata

candrews on 5 Jul 2016

You can set the "Related URL" for Gentoo to https://github.com/gentoo/gentoo/tree/master/net-analyzer/netdata

Thanks! Done.

ktsaou on 5 Jul 2016

@ktsaou It should probably be:

RHEL == CentOS (just rebranded and a few other nuances)
Fedora is where things are tested before being released to RHEL

RHEL/CentOS
Fedora

jasonwbarnett on 28 Jul 2016

RHEL == CentOS (just rebranded and a few other nuances)

ok, fixed that. Although there are differences. I decided to treat separately when I found this: https://github.com/firehol/netdata-demo-site/blob/28c7962d28a942c5321e8475f51d5b17dd48a884/install-required-packages.sh#L653

ktsaou on 28 Jul 2016

I meant this: https://github.com/firehol/netdata-demo-site/blob/28c7962d28a942c5321e8475f51d5b17dd48a884/install-required-packages.sh#L613-L616

ktsaou on 28 Jul 2016

I'm maintaining netdata for NETGEAR ReadyNAS @ https://github.com/nastools/netdata

NAStools on 30 Jul 2016

I'm maintaining netdata for NETGEAR ReadyNAS

nice. Thank you!

Please make sure the directory /var/lib/netdata/registry is empty on your distribution package. There is an embedded devices package that distributes netdata with the unique id file pre-installed. This makes all these netdata installations appear as the same one to the global registry..

ktsaou on 30 Jul 2016

ok, fixed that. Although there are differences. I decided to treat separately when I found this: https://github.com/firehol/netdata-demo-site/blob/28c7962d28a942c5321e8475f51d5b17dd48a884/install-required-packages.sh#L653

I just submitted this PR to correct that repo. Not sure how those packages made it in the repo, but they're wrong.

jasonwbarnett on 30 Jul 2016

Please make sure the directory /var/lib/netdata/registry is empty on your distribution package.

I'm building with dh-autoreconf and don't end up with a registry directory. Do I need to be including this?

root@readynas:/apps/nastools-netdata# find . -name registry
root@readynas:/apps/nastools-netdata#

NAStools on 30 Jul 2016

I'm building with dh-autoreconf and don't end up with a registry directory. Do I need to be including this?

The installation should only create /var/lib/netdata. The rest are created by netdata itself. It is ok.

ktsaou on 30 Jul 2016

Can you please add https://anonscm.debian.org/git/collab-maint/netdata.git for Debian (and maybe put in my name as well?) Thanks

FedericoCeratto on 13 Oct 2016

Can you please add https://anonscm.debian.org/git/collab-maint/netdata.git for Debian (and maybe put in my name as well?) Thanks

done. thanks!

I would love to provide a binary package and probably a PPA for users to install it easily on debian based distributions, until the distros include it. I am completely ignorant of the procedure - I have tried to do it a few times, but it is totally counter-intuitive for me. Can you help me?

ktsaou on 13 Oct 2016

oh! I replaced @lhw with @FedericoCeratto . Do you want me to add @lhw back, to list both of you?

ktsaou on 13 Oct 2016

@ktsaou we are both maintaining the package and lhw did a lot of work :)

FedericoCeratto on 13 Oct 2016

Added @lhw back, together with you.

ktsaou on 14 Oct 2016

Just updated the ansible role and uploaded it into ansible galaxy.

You can retrieve the whole playbook here : https://galaxy.ansible.com/jffz/netdata/

Direct usage with ansible-galaxy: ansible-galaxy install jffz.netdata

jffz on 17 Oct 2016

updated the link above to point to https://galaxy.ansible.com/jffz/netdata/

ktsaou on 17 Oct 2016

Maybe you can delete "
https://github.com/jffz/ansible-netdata/blob/master/tasks/main.yml" to
avoid any mistake.

But i guess both chef and ansible books should be linked somewhere in the readme / wiki for easier retrieving.

jffz on 17 Oct 2016

You mean https://github.com/firehol/netdata/blob/master/ansible/netdata.yml ?

ktsaou on 17 Oct 2016

yeah sorry, i pasted a wrong link

jffz on 17 Oct 2016

done is #1123

ktsaou on 17 Oct 2016

I have been (trying to) following the (amazing amount of) development in this project... Quite a few new features were merged (fping, DBs, external backend come to mind), is there any timeframe for a new release?
It will help iron out a few more things, without having "old" users complain like when they had to switch between gnome2/3 or WinXP/7 :-)

thinrope on 21 Nov 2016

I think in 1-2 weeks v1.5 will be out.
We need some time to test all new features.

ktsaou on 21 Nov 2016

Dear all, netdata v1.5.0 has been released!

ktsaou on 23 Jan 2017

Should be in Gentoo shortly: https://github.com/gentoo/gentoo/pull/3607

candrews on 23 Jan 2017

hm... I see it searches for the URL at firehol.org but @philwhineray has moved everything to github.

@philwhineray also, since travis failed to create the tar files, can I create them by hand and upload them to github? If that is too hard, I'll release 1.5.1 shortly to have the packages generated...

ktsaou on 23 Jan 2017

Hopefully the redirects from the website take care of it for most people.

Creating the packages by hand should not be hard. Just checkout the tag, run the fakeroot ./packaging/git-build step from .travis.yml and upload the tar-files that are created manually.

philwhineray on 23 Jan 2017

I am going to be out for the next hour or two but after that, if you are struggling, let me know and I will create them and do the upload. I think you will find it easy though, you just need to have the dependent library headers and fakeroot command.

philwhineray on 23 Jan 2017

@ktsaou thanks for the reminder! Looks like something is different in the tarball signing: the signature file is not published anymore at https://github.com/firehol/netdata/releases/ - is that on purpose?

FedericoCeratto on 23 Jan 2017

ok, I have the packages. I am uploading them now.
Is there another procedure to sign them?

ktsaou on 23 Jan 2017

Perhaps something changed on GH? If you curl | grep you'll see asc files for previous releases:
curl https://github.com/firehol/netdata/releases/ | grep '.tar.gz.asc'

FedericoCeratto on 23 Jan 2017

Uploaded.

@FedericoCeratto: Phil changed the release procedure to have travis create the files of the release. There was an issue and this broke in the middle. I have uploaded the files now, but there might be something more missing to upload the signature files and possibly update the firehol.org site for the release.

I think @philwhineray will help us complete the release in a while...

ktsaou on 23 Jan 2017

OK, so the travis would also normally do checksums and upload them i.e.:

~~
for i in .tar.; do md5sum -b $i > $i.md5; sha512sum -b $i > $i.sha
~~

The signing is always a separate step to ensure what went in the package is what was in git. On yout machine, In the firehol/infrastructure repo do this:

~~
./bin/sign-github-release netdata 1.5.0
~~

It should download the packages, check they are OK then ask for your gpg key password to sign, then upload the .asc files using the token you previously set up in ~/.firehol-github-oauth.

philwhineray on 23 Jan 2017

Also, I put a helper script in there:

./bin/upload-github-asset which might be quicker than uploading all the checkums by hand:

~~
./bin/upload-github-asset netdata 1.5.0 *.md5 *.sha
~~

philwhineray on 23 Jan 2017

For future reference, the infrastructure repo readme documents this and most of the other things I have set up, just in case the proverbial bus hits me.

philwhineray on 23 Jan 2017

@philwhineray :

firehol-infrastructure.git $ ./bin/sign-github-release netdata 1.5.0
{
  "message": "Not Found",
  "documentation_url": "https://developer.github.com/v3"
}

ktsaou on 23 Jan 2017

Sorry, it needs to be:

~~
./bin/sign-github-release netdata v1.5.0
~~

i.e. the full tag name

philwhineray on 24 Jan 2017

ok. done!
Thanks @philwhineray !
(have a look, everything should be ok now)

ktsaou on 24 Jan 2017

Looks OK to me!

philwhineray on 24 Jan 2017

netdata at freeports: http://www.freshports.org/net-mgmt/netdata/
@vlvkobal Wow!

ktsaou on 27 Jan 2017

👍1

@mmokhi I believe you submitted netdata to freeports. If yes, first of all, thank you, next I would like to add you to this issue as the maintainer for freebsd. Do you agree?

ktsaou on 27 Jan 2017

👍1

@ktsaou Hey, my pleasure to help.
Sure I'll agree. :smile: I think it'll help me to connect with related people sooner and discover bugs/updates easier :wink:

mmokhi on 27 Jan 2017

ok. nice. I added you.

ktsaou on 27 Jan 2017

Thanks :smile: :+1:

mmokhi on 27 Jan 2017

@ktsaou the .asc signature file for 1.6.0 is still missing from https://github.com/firehol/netdata/releases
The URL should be https://github.com/firehol/netdata/releases/download/v1.6.0/netdata-1.6.0.tar.xz.asc

FedericoCeratto on 30 Apr 2017

hm... @philwhineray any ideas?

ktsaou on 30 Apr 2017

Well package uploads are automatic but you still have to run the signature
script by hand. Did that get done?

philwhineray on 30 Apr 2017

Well package uploads are automatic but you still have to run the signature
script by hand. Did that get done?

Forgive me... I missed that detail.
How do I do that?

ktsaou on 30 Apr 2017

I think the infrastructure repo readme has the details.

Apologies: I am on phone email only so I can't check the details.

philwhineray on 30 Apr 2017

ok, let me check... thanks!

ktsaou on 30 Apr 2017

done!

@philwhineray thank you for your help (yeap, the docs are clear)!

@FedericoCeratto thank you for bringing this to my attention. I completely missed this detail.

ktsaou on 30 Apr 2017

I have released netdata v1.7.0
Please update your repos/distros.

ktsaou on 18 Jul 2017

Already done :wink: :smile:

https://svnweb.freebsd.org/ports?view=revision&revision=446144

mmokhi on 18 Jul 2017

As you're probably aware, OpenWRT is in the process of merging with LEDE project. Until the repositories are merged there will be no changes in the code, unless security related. Thanks for your understanding.

nitroshift

nitroshift on 20 Jul 2017

Hi all,

I have just released netdata v1.8.0
Please update your packages.
Thanks!

ktsaou on 17 Sep 2017

1.8.0 is in Gentoo: https://github.com/gentoo/gentoo/commit/55c3ec1b2cb2ad736f9da9a6d53861e31346d761

candrews on 18 Sep 2017

🎉1 👍1

1.8.0 is up in debian shortly: https://tracker.debian.org/news/873552

lhw on 19 Sep 2017

🎉2 👍2

Sorry for delay :wink: took a little long to review :smile: but finally landed :wink:

mmokhi on 22 Sep 2017

👍1

@mmokhi thanks!

A folk on reddit says the freebsd port for netdata v1.8.0 is broken.

ktsaou on 25 Sep 2017

Yeh,
Fix was committed moment ago :smile: https://svnweb.freebsd.org/changeset/ports/450630

mmokhi on 25 Sep 2017

You might want to reach out to QNAP_Stephane who posts builds at https://forum.qnap.com/viewtopic.php?t=121518 (and to QNAP Club) and see if they want to be listed as a maintainer.

Speaking of which, time to update my QNAPs.

magao on 26 Sep 2017

Hi all,

I have just released netdata v1.9.0
Please update your packages.
Thanks!

ktsaou on 17 Dec 2017

Hi,

I maintain netdata SlackBuild script for Slackware. We rely on released tarball
https://slackbuilds.org/repository/14.2/system/netdata/

willysr on 15 Mar 2018

👍1

@willysr thank you! I added you to the list at the top.

ktsaou on 18 Mar 2018

Hi all,

netdata v1.10.0 has just been released!
Please update your packages.

cc: @svenstaro @SanskritFritz @candrews @lhw @FedericoCeratto @willysr @vlvkobal @mmokhi @gslin @nitroshift @NAStools @titpetric @jffz @sergiopena @mcnewton @philwhineray @alonbl @simonnagl @paulfantom @l2isbad @Fourdee

ktsaou on 27 Mar 2018

🎉1

The Debian package for v1.10.0 is almost ready.

FedericoCeratto on 28 Mar 2018

🎉1 👍1

Done.

On Wed, Mar 28, 2018 at 11:37 AM Federico Ceratto notifications@github.com
wrote:

The Debian package for v1.10.0 is almost ready.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/firehol/netdata/issues/651#issuecomment-376824669,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAGgOFBRBmRbQfPdaPFe-LV_fU1OzxUks5ti1nogaJpZM4JE6eN
.

svenstaro on 28 Mar 2018

🎉1 👍1

@ktsaou the python.d/python_modules/urllib3/packages/six.py is not part of the urllib3 and it's not listed in LICENSE-REDISTRIBUTED.md

FedericoCeratto on 28 Mar 2018

@ktsaou the python.d/python_modules/urllib3/packages/six.py is not part of the urllib3 and it's not listed in LICENSE-REDISTRIBUTED.md

oops! I didn't know that. @l2isbad do we need this file? If yes, we should add it to the license. If not, we should remove it.

https://github.com/firehol/netdata/blob/master/python.d/python_modules/urllib3/packages/six.py

ktsaou on 28 Mar 2018

do we need this file?

i think yes

[/opt/netdata/usr/libexec/netdata/python.d/python_modules/urllib3]grep -R "from .*six *"
filepost.py:from .packages import six
filepost.py:from .packages.six import b
connection.py:from .packages import six
connection.py:from .packages.six.moves.http_client import HTTPConnection as _HTTPConnection
connection.py:from .packages.six.moves.http_client import HTTPException  # noqa: F401
fields.py:from .packages import six
connectionpool.py:from .packages import six
connectionpool.py:from .packages.six.moves import queue
util/response.py:from ..packages.six.moves import http_client as httplib
util/retry.py:from ..packages import six
util/request.py:from ..packages.six import b, integer_types
_collections.py:from .packages.six import iterkeys, itervalues, PY3
packages/six.py:    """Remove item from six.moves."""
response.py:from .packages.six import string_types as basestring, binary_type, PY3
response.py:from .packages.six.moves import http_client as httplib
contrib/pyopenssl.py:    from ..packages import six
contrib/appengine.py:from ..packages.six.moves.urllib.parse import urljoin
contrib/appengine.py:from ..packages.six import BytesIO
contrib/ntlmpool.py:from ..packages.six.moves.http_client import HTTPSConnection
poolmanager.py:from .packages.six.moves.urllib.parse import urljoin
exceptions.py:from .packages.six.moves.http_client import (
request.py:from .packages.six.moves.urllib.parse import urlencode

ilyam8 on 28 Mar 2018

Slackware SlackBuild script has been updated and it will be part for this weekend's public update.

Thanks :)

willysr on 29 Mar 2018

👍1

@ktsaou the python.d/python_modules/urllib3/packages/six.py is not part of the urllib3 and it's not listed in LICENSE-REDISTRIBUTED.md

added it with PR #3586
thank you for letting me know...

ktsaou on 29 Mar 2018

Done, hub version is published. Next/docker image will replace ssmtp most likely (a PR is in the works), so there will be some changes regarding readme and such.

titpetric on 29 Mar 2018

❤1 👍1

This might be useful: https://repology.org/metapackage/netdata/badges :)

FedericoCeratto on 24 Apr 2018

Add me as macOS Homebrew formula.

rickard-von-essen on 17 May 2018

Add me as macOS Homebrew formula.

added you. Thank you for supporting netdata!

ktsaou on 1 Jun 2018

If you know who is the netdata package maintainer for alpine, please invite him here. It seems the latest package on alpine is broken #3897

ktsaou on 28 Jun 2018

Alpine Linux netdata package source: https://git.alpinelinux.org/cgit/aports/log/?qt=grep&q=Netdata

rickard-von-essen on 28 Jun 2018

netdata/APKBUILD

# Contributor: Carlo Landmeter <[email protected]> 
# Maintainer:

rickard-von-essen on 28 Jun 2018

nice finding!

@clandmeter are you the netdata package maintainer for alpine?

ktsaou on 29 Jun 2018

@ktsaou is list of maintainers from https://github.com/firehol/netdata/issues/651#issue-163803641 up to date? I am currently in process of writing new ansible role for netdata as I've tried @jffz one some time ago, but he is unresponsive and my PRs are waiting and waiting. I want to include option to install netdata not only from source (I don't want to install build tools on multiple servers), but also from pre-built repository packages. While writing I need to checked some of those repos, and alternative ones as I want to support systems I usually support with my roles:

Ubuntu 16.04 & 18.04
Debian 8 & 9
CentOS 7
Fedora 27

What I found:

"Related URL" for debian official distro doesn't work
debian 8 doesn't have netdata included, so the table is a bit misleading
Fedora and CentOS have natdata packages (1.10) in copr (https://copr.fedorainfracloud.org/coprs/baoboa/netdata/ and https://copr.fedorainfracloud.org/coprs/tartare/netdata/), maybe consider adding them?
there is actually an official package for netdata (1.9.0) in ubuntu 18.04 maintained by @lhw, at least that's what apt show netdata says

There are possibly more things lacking, but I found that in current state it is impossible to support all those repo combinations in one ansible role, so I decided to use official releases and install it all by myself with ansible. Hopefully it will be ready soon and we all be able to install netdata faster on multiple devices at once (compile on one device - install on many). :smile:

paulfantom on 30 Jun 2018

@paulfantom If you want to check debian package status it's actually easier to just go to the package tracker: https://tracker.debian.org/pkg/netdata
So for now its up-to-date but you are right it's not in debian 8 at least not officially and even in debian 9 it's only in the backports. And Ubuntu packages are simply pulled from debian testing which was 1.9.0 at the time.

@ktsaou The URL for debian has changed as debian switched to gitlab its now http://salsa.debian.org/debian/netdata but you could also use the tracker URL from above.

lhw on 1 Jul 2018

ok guys I converted this to a wiki page: https://github.com/firehol/netdata/wiki/netdata-package-maintainers

So, feel free to edit it to reflect the current status.

ktsaou on 1 Jul 2018

👍1

updated also the original post to divert to the wiki.

ktsaou on 1 Jul 2018

Wiki page is now at https://github.com/netdata/netdata/wiki/netdata-package-maintainers.

Closing as this information is tracked in wiki.

paulfantom on 22 Sep 2018

@lhw @FedericoCeratto do you need GPG signature for tar packages of netdata? If yes, why?

paulfantom on 26 Sep 2018

@paulfantom the signature is optional and it's meant to ensure the authenticity and integrity of the tarball

FedericoCeratto on 26 Sep 2018

Great! :+1: So it is not crucial if you are downloading from github via HTTPS. In such scenario source authenticity is achieved by downloading using github and transport security is achieved by using HTTPS. And if someone would gain access to our code on github, then GPG signature won't prevent anything since archive signing is in travis.

As for integrity there is always a checksum.

paulfantom on 26 Sep 2018

HTTPS provides limited security (there has been many issues) and only for data in transit (not at rest). GPG signatures from Travis or other 3rd party services are not accepted - the tarball has to be signed directly by the author.

FedericoCeratto on 26 Sep 2018

It is not provided directly by an author, that's why I want to remove GPG signature.

paulfantom on 26 Sep 2018

The GPG signatures are only on source files and are currently provided directly by an author.

I don't have a strong view about what happens going forwards but for reference, the current process is:

a GPG-signed tag is created
this is checked by the travis build. it does not add anything directly but just makes sure later steps should work
a script, sign-github-release from the firehol/infrastructure repo is run on the developer's machine where signing will take place. This takes a clean copy of the repo and checks the source signature. If then downloads the release source tar from github and if the contents match, prompts the dev to sign. It then uploads the signature back to the github release.

If you are thinking to replace the tagging with a system which does so automatically, e.g. based on the content of a PR, I think the signatures can still be produced without opening much of a hole.

The script in (3) would need to be updated not look for a signature, and any manual checks that the tag is good move from before tagging (otherwise the git gpg signature did nothing anyway) to after.

I should note as well at this point that the checks in said script are not perfect. They don't check files added by Travis since we have no way to independently verify them, much as with binary output. The key suspects I would suggest are those produced by autoconf/automake, so if you distrust Travis, or the possibility that the tar could be interfered with between upload by travis and download for checking before signing, whilst the sources should be sound, running autoreconf in your own trusted environment would be a good idea.

philwhineray on 26 Sep 2018

Source tar signatures could still be produced without changing much that is. I'm not suggesting signed tags from Travis, to be clear.

philwhineray on 26 Sep 2018

Plan is to have fully automated reproducible build and release system which could be easily extended to provide binary packages (via repository). Whole thing needs to be as simple as possible for two reasons. First is to allow other people see how it is created (without magic) and second is to allow for very fast release cycle, where we can have "nightly" packages every 24h and "stable" ones every 2-4 weeks. This means that system will probably be highly opinionated, so if something is only optional and doesn't have much value, it is just a complication which needs to be removed.

This doesn't mean that we won't sign packages, we will, but binary packages. In future we will probably drop tarball generation by travis since GitHub automatically creates archives with code when creating a release.

paulfantom on 26 Sep 2018

Dear all netdata release v1.11 is currently in draft.
We will do some tests during the weekend and publish it on Mon or Tue.

A lot have changed in this release. The whole release procedure has been rewritten, stock config files have been moved to /usr/lib/netdata, etc.

The draft release message describes everything in more detail.

ktsaou on 2 Nov 2018

Well, it's already in Gentoo: https://github.com/gentoo/gentoo/tree/master/net-analyzer/netdata

candrews on 2 Nov 2018

👍1

Was this page helpful?

0 / 5 - 0 ratings