graphite-dev team mailing list archive

[fp <question100624@xxxxxxxxxxxxxxxxxxxxx>]

Question #100624 on Graphite changed:
https://answers.launchpad.net/graphite/+question/100624

fp posted a new comment:

Also, I found the problem that you are running into, because I did the same thing just now.  

If you generate a src.rpm using

python setup.py bdist_rpm

it will generate the following src rpms: 
-rw-r--r-- 1 root root 12220 Feb  8 08:29 carbon-0.9.5-1.src.rpm
-rw-r--r-- 1 root root  76437 Feb  8 08:30 graphite-0.9.5-1.src.rpm
-rw-r--r-- 1 root root 10449 Feb  8 08:49 whisper-0.9.5-1.src.rpm

The src rpms are way to small, the tarballs that the src.rpms install in
/usr/src/redhat/SOURCES are much smaller then the regular downloads. ie:

-rw-r--r-- 1 root root 9979 Feb  8 08:29 carbon-0.9.5.tar.gz (from bdist)
-rw-r--r--  1 root root   14580 Feb  8 08:21 carbon-0.9.5.tar.gz (regular download)
-rw-r--r-- 1 root root 74062 Feb  8 08:30 graphite-0.9.5.tar.gz  (from bdist)
-rw-r--r-- 1 root root 2047050 Feb  8 08:21 graphite-0.9.5.tar.gz (regular download)
-rw-r--r-- 1 root root 8258 Feb  8 08:22 whisper-0.9.5.tar.gz (from bdist)
-rw-r--r--  1 root root   12028 Feb  8 08:21 whisper-0.9.5.tar.gz (regular download) 

That being said, if you install the src.rpm generated from bdist,
overwrite the files in the SOURCES dir with the ones downloaded from the
main graphite site, and your the templates/content dir from graphite
will be installed as per normal. So there is a bug with how the bdist is
generated atm, but this is a simple workaround.

That being said, I'm still working on rpms for rhel/centos that do a bit
more stuff (init scripts, dependencies, httpd hosts, etc) I'll let you
know when they are done.

ttyl

You received this question notification because you are a member of
graphite-dev, which is an answer contact for Graphite.