Thread: [Ipvsman-users] ipvsman tarball
Status: Alpha
Brought to you by:
volkerjaenisch
From: Gerry R. <gr...@ve...> - 2007-07-02 00:54:38
|
Hi Volker, I have a suggestion involving packaging. In order to support various downstream packaging such as RPM, the ipvsman tarball will need to conform to certain convention. The high level directory name inside the tarball must be like "ipvsman-9.0.3" or whatever is the version number. This is a requirement of RPM specfiles. Also, the general processing expected is: ./configure make make install Regards, Gerry |
From: Dr. V. J. <vol...@in...> - 2007-07-02 01:23:23
|
Hi Gerry! Gerry Reno schrieb: > Hi Volker, > I have a suggestion involving packaging. In order to support various > downstream packaging such as RPM, the ipvsman tarball will need to > conform to certain convention. The high level directory name inside the > tarball must be like "ipvsman-9.0.3" or whatever is the version number. > This is a requirement of RPM specfiles. Also, the general processing > expected is: > ./configure > make > make install > Thank you very much for this information. I will improve the installation for RPM based systems. To work around your problems. You should go to ipvsman_0.9.2-9.tar.gz/trunk and issue a #python setup.py install this shloud do the installation. Best Regards Volker -- ==================================================== inqbus it-consulting +49 ( 341 ) 5643800 Dr. Volker Jaenisch http://www.inqbus.de Herloßsohnstr. 12 0 4 1 5 5 Leipzig N O T - F Ä L L E +49 ( 170 ) 3113748 ==================================================== |
From: Gerry R. <gr...@ve...> - 2007-07-02 01:30:32
|
Dr. Volker Jaenisch wrote: > Hi Gerry! > > Gerry Reno schrieb: > >> Hi Volker, >> I have a suggestion involving packaging. In order to support various >> downstream packaging such as RPM, the ipvsman tarball will need to >> conform to certain convention. The high level directory name inside the >> tarball must be like "ipvsman-9.0.3" or whatever is the version number. >> This is a requirement of RPM specfiles. Also, the general processing >> expected is: >> ./configure >> make >> make install >> >> > Thank you very much for this information. I will improve the > installation for RPM based systems. > > To work around your problems. You should go to > > ipvsman_0.9.2-9.tar.gz/trunk > > and issue a > > #python setup.py install > > this shloud do the installation. > > Best Regards > > Volker > > > > Hi again, I found a target: bdist_rpm that is trying to create an RPM but it errors: # python setup.py bdist_rpm running bdist_rpm creating build/bdist.linux-i686 creating build/bdist.linux-i686/rpm creating build/bdist.linux-i686/rpm/SOURCES creating build/bdist.linux-i686/rpm/SPECS creating build/bdist.linux-i686/rpm/BUILD creating build/bdist.linux-i686/rpm/RPMS creating build/bdist.linux-i686/rpm/SRPMS writing 'build/bdist.linux-i686/rpm/SPECS/ipvsman.spec' running sdist reading manifest file 'MANIFEST' creating ipvsman-0.9.2-9 making hard links in ipvsman-0.9.2-9... hard linking ipvsman -> ipvsman-0.9.2-9 'ipvsman.py' not a regular file -- skipping hard linking ipvsmand -> ipvsman-0.9.2-9 hard linking setup.py -> ipvsman-0.9.2-9 creating dist tar -cf dist/ipvsman-0.9.2-9.tar ipvsman-0.9.2-9 gzip -f9 dist/ipvsman-0.9.2-9.tar removing 'ipvsman-0.9.2-9' (and everything under it) copying dist/ipvsman-0.9.2-9.tar.gz -> build/bdist.linux-i686/rpm/SOURCES building RPMs rpmbuild -ba --define _topdir /root/build/ipvsman/trunk/build/bdist.linux-i686/rpm --clean build/bdist.linux-i686/rpm/SPECS/ipvsman.spec error: File /root/build/ipvsman/trunk/build/bdist.linux-i686/rpm/SOURCES/ipvsman-0.9.2_9.tar.gz: No such file or directory error: command 'rpmbuild' failed with exit status 1 # ls build debian ipvsman ipvsmand_rh lib README.txt svn-commit.tmp config dist ipvsmand keepalived.conf MANIFEST setup.py test.shtml Does it need for me to manually copy the tgz into SOURCES? Thanks, Gerry |
From: Gerry R. <gr...@ve...> - 2007-07-02 01:33:13
|
Gerry Reno wrote: > Dr. Volker Jaenisch wrote: > >> Hi Gerry! >> >> Gerry Reno schrieb: >> >> >>> Hi Volker, >>> I have a suggestion involving packaging. In order to support various >>> downstream packaging such as RPM, the ipvsman tarball will need to >>> conform to certain convention. The high level directory name inside the >>> tarball must be like "ipvsman-9.0.3" or whatever is the version number. >>> This is a requirement of RPM specfiles. Also, the general processing >>> expected is: >>> ./configure >>> make >>> make install >>> >>> >>> >> Thank you very much for this information. I will improve the >> installation for RPM based systems. >> >> To work around your problems. You should go to >> >> ipvsman_0.9.2-9.tar.gz/trunk >> >> and issue a >> >> #python setup.py install >> >> this shloud do the installation. >> >> Best Regards >> >> Volker >> >> >> >> >> > Hi again, > I found a target: bdist_rpm that is trying to create an RPM but it errors: > > # python setup.py bdist_rpm > running bdist_rpm > creating build/bdist.linux-i686 > creating build/bdist.linux-i686/rpm > creating build/bdist.linux-i686/rpm/SOURCES > creating build/bdist.linux-i686/rpm/SPECS > creating build/bdist.linux-i686/rpm/BUILD > creating build/bdist.linux-i686/rpm/RPMS > creating build/bdist.linux-i686/rpm/SRPMS > writing 'build/bdist.linux-i686/rpm/SPECS/ipvsman.spec' > running sdist > reading manifest file 'MANIFEST' > creating ipvsman-0.9.2-9 > making hard links in ipvsman-0.9.2-9... > hard linking ipvsman -> ipvsman-0.9.2-9 > 'ipvsman.py' not a regular file -- skipping > hard linking ipvsmand -> ipvsman-0.9.2-9 > hard linking setup.py -> ipvsman-0.9.2-9 > creating dist > tar -cf dist/ipvsman-0.9.2-9.tar ipvsman-0.9.2-9 > gzip -f9 dist/ipvsman-0.9.2-9.tar > removing 'ipvsman-0.9.2-9' (and everything under it) > copying dist/ipvsman-0.9.2-9.tar.gz -> build/bdist.linux-i686/rpm/SOURCES > building RPMs > rpmbuild -ba --define _topdir > /root/build/ipvsman/trunk/build/bdist.linux-i686/rpm --clean > build/bdist.linux-i686/rpm/SPECS/ipvsman.spec > error: File > /root/build/ipvsman/trunk/build/bdist.linux-i686/rpm/SOURCES/ipvsman-0.9.2_9.tar.gz: > -----------------------------------------------------------------------------------------------------------^ syntax error _ instead of - > No such file or directory > error: command 'rpmbuild' failed with exit status 1 > # ls > build debian ipvsman ipvsmand_rh lib README.txt > svn-commit.tmp > config dist ipvsmand keepalived.conf MANIFEST setup.py test.shtml > > > Does it need for me to manually copy the tgz into SOURCES? > > Thanks, > Gerry > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Ipvsman-users mailing list > Ipv...@li... > https://lists.sourceforge.net/lists/listinfo/ipvsman-users > > |
From: Dr. V. J. <vol...@in...> - 2007-07-02 01:42:43
|
Does it work? -- ==================================================== inqbus it-consulting +49 ( 341 ) 5643800 Dr. Volker Jaenisch http://www.inqbus.de Herloßsohnstr. 12 0 4 1 5 5 Leipzig N O T - F Ä L L E +49 ( 170 ) 3113748 ==================================================== |
From: Gerry R. <gr...@ve...> - 2007-07-02 01:45:58
|
Dr. Volker Jaenisch wrote: > Does it work? > > I'm still looking for the syntax error. G. |
From: Dr. V. J. <vol...@in...> - 2007-07-02 01:55:33
|
Gerry Reno schrieb: > Dr. Volker Jaenisch wrote: > >> Does it work? >> >> >> > I'm still looking for the syntax error. > Sorry could not confirm the error on debian platform. But this is python code. Just do a # python setup.py install and it is installed. I do not like this. I like packages - as you do. I will look into this at once to make rpms. Best regards, Volker -- ==================================================== inqbus it-consulting +49 ( 341 ) 5643800 Dr. Volker Jaenisch http://www.inqbus.de Herloßsohnstr. 12 0 4 1 5 5 Leipzig N O T - F Ä L L E +49 ( 170 ) 3113748 ==================================================== |
From: Dr. V. J. <vol...@in...> - 2007-07-02 02:00:59
|
Gerry Reno schrieb: > Dr. Volker Jaenisch wrote: > >> Does it work? >> >> >> > I'm still looking for the syntax error. > It's 4:00 local time. Time for a rest. Be online 12:00 again to solve the rpm problem. Regards, Volker -- ==================================================== inqbus it-consulting +49 ( 341 ) 5643800 Dr. Volker Jaenisch http://www.inqbus.de Herloßsohnstr. 12 0 4 1 5 5 Leipzig N O T - F Ä L L E +49 ( 170 ) 3113748 ==================================================== |
From: Gerry R. <gr...@ve...> - 2007-07-02 04:00:35
|
Volker, Ok, dependencies such as python-egenix-mxdatetime, python-urwid are not easy on Redhat/Fedora. The python-dns rpm is available but I cannot find any packages for these other dependencies. I don't do tarballs. And that is why I am able to do a 'yum update' and update to the next OS release without any major issue. If you know of a repository that may have these packages in RPM let me know. I have searched a little but did not find anything. eGenix says that they are included in RH but when you do a 'yum list python-*' they are not there. Regards, Gerry |
From: Dr. V. J. <vol...@in...> - 2007-07-02 16:23:56
|
Hi Gerry! Gerry Reno schrieb: > Volker, > Ok, dependencies such as python-egenix-mxdatetime, python-urwid are not > easy on Redhat/Fedora. The python-dns rpm is available but I cannot find > any packages for these other dependencies. I don't do tarballs. And that > is why I am able to do a 'yum update' and update to the next OS release > without any major issue. If you know of a repository that may have these > packages in RPM let me know. Check this out http://dag.wieers.com/rpm/packages/python-mx-base/ http://dag.wieers.com/rpm/packages/python-urwid/ Best Regards, Volker -- ==================================================== inqbus it-consulting +49 ( 341 ) 5643800 Dr. Volker Jaenisch http://www.inqbus.de Herloßsohnstr. 12 0 4 1 5 5 Leipzig N O T - F Ä L L E +49 ( 170 ) 3113748 ==================================================== |
From: Dr. V. J. <vol...@in...> - 2007-07-02 01:34:43
|
Hi Gerry! I will have a look immediatly! Never tried this - sorry! Gerry Reno schrieb: > Hi again, > I found a target: bdist_rpm that is trying to create an RPM but it errors: > > # python setup.py bdist_rpm > running bdist_rpm > creating build/bdist.linux-i686 > creating build/bdist.linux-i686/rpm > creating build/bdist.linux-i686/rpm/SOURCES > creating build/bdist.linux-i686/rpm/SPECS > creating build/bdist.linux-i686/rpm/BUILD > creating build/bdist.linux-i686/rpm/RPMS > creating build/bdist.linux-i686/rpm/SRPMS > writing 'build/bdist.linux-i686/rpm/SPECS/ipvsman.spec' > running sdist > reading manifest file 'MANIFEST' > creating ipvsman-0.9.2-9 > making hard links in ipvsman-0.9.2-9... > hard linking ipvsman -> ipvsman-0.9.2-9 > 'ipvsman.py' not a regular file -- skipping > hard linking ipvsmand -> ipvsman-0.9.2-9 > hard linking setup.py -> ipvsman-0.9.2-9 > creating dist > tar -cf dist/ipvsman-0.9.2-9.tar ipvsman-0.9.2-9 > gzip -f9 dist/ipvsman-0.9.2-9.tar > removing 'ipvsman-0.9.2-9' (and everything under it) > copying dist/ipvsman-0.9.2-9.tar.gz -> build/bdist.linux-i686/rpm/SOURCES > building RPMs > rpmbuild -ba --define _topdir > /root/build/ipvsman/trunk/build/bdist.linux-i686/rpm --clean > build/bdist.linux-i686/rpm/SPECS/ipvsman.spec > error: File > /root/build/ipvsman/trunk/build/bdist.linux-i686/rpm/SOURCES/ipvsman-0.9.2_9.tar.gz: > No such file or directory > error: command 'rpmbuild' failed with exit status 1 > # ls > build debian ipvsman ipvsmand_rh lib README.txt > svn-commit.tmp > config dist ipvsmand keepalived.conf MANIFEST setup.py test.shtml > > > Does it need for me to manually copy the tgz into SOURCES? > > Thanks, > Gerry > -- ==================================================== inqbus it-consulting +49 ( 341 ) 5643800 Dr. Volker Jaenisch http://www.inqbus.de Herloßsohnstr. 12 0 4 1 5 5 Leipzig N O T - F Ä L L E +49 ( 170 ) 3113748 ==================================================== |
From: Gerry R. <gr...@ve...> - 2007-07-02 02:09:32
|
Dr. Volker Jaenisch wrote: > Gerry Reno schrieb: > >> Dr. Volker Jaenisch wrote: >> >> >>> Does it work? >>> >>> >>> >>> >> I'm still looking for the syntax error. >> >> > It's 4:00 local time. Time for a rest. > Be online 12:00 again to solve the rpm problem. > > Regards, > > Volker > Volker, I thought you were burning some late oil. See you tomorrow. Gerry |
From: Gerry R. <gr...@ve...> - 2007-07-02 03:06:48
|
Gerry Reno wrote: > Dr. Volker Jaenisch wrote: > >> Does it work? >> >> >> > I'm still looking for the syntax error. > > G. (Copied from LVS-Users list) Volker, Ok, the problem in building RPM's using the bdist_rpm target is that there is a version mangling problem in bdist_rpm.py in python itself. The bug is # 1360200, http://sourceforge.net/tracker/index.php?func=detail&aid=1360200&group_id=5470&atid=305470 . I'm running the latest Fedora (F7) and the python rpm version is 2.5-12.fc7. The fix is supposed to be coming in python 2.6. Now if you go look at the bug you will see the patch that fixes the problem. So anyone that wants to compile python from source should be able to patch it. Regards, Gerry |
From: Gerry R. <gr...@ve...> - 2007-07-02 16:40:15
|
Dr. Volker Jaenisch wrote: > Hi Gerry! > > Gerry Reno schrieb: > >> Volker, >> Ok, dependencies such as python-egenix-mxdatetime, python-urwid are not >> easy on Redhat/Fedora. The python-dns rpm is available but I cannot find >> any packages for these other dependencies. I don't do tarballs. And that >> is why I am able to do a 'yum update' and update to the next OS release >> without any major issue. If you know of a repository that may have these >> packages in RPM let me know. >> > Check this out > > http://dag.wieers.com/rpm/packages/python-mx-base/ > http://dag.wieers.com/rpm/packages/python-urwid/ > > Best Regards, > > Volker > > Volker, Thanks. I checked those packages in DAG and unfortunately they are really old. The only thing there that might be of use is the spec files. These are the type of problems that anyone on a distro other than probably Debian is going to come up against. And if the barrier is too high (which I already think that it is) then adoption of ipvsman will suffer greatly. Regards, Gerry |