I'm trying to build vdsm from git . After make rpm I get these errors:
Processing files: vdsm-debuginfo-4.10.0-0.306.git5c8440f.fc17.x86_64 Checking for unpackaged file(s): /usr/lib/rpm/check-files /root/rpmbuild/BUILDROOT/vdsm-4.10.0-0.306.git5c8440f.fc17.x86_64 error: Installed (but unpackaged) file(s) found: /usr/lib64/python2.7/site-packages/vdsm/tool/load_needed_modules.py /usr/lib64/python2.7/site-packages/vdsm/tool/load_needed_modules.pyc /usr/lib64/python2.7/site-packages/vdsm/tool/load_needed_modules.pyo /usr/libexec/vdsm/hooks/after_vdsm_stop/10_faqemu /usr/share/vdsm-bootstrap/interface-2/deployUtil.py /usr/share/vdsm-bootstrap/interface-2/deployUtil.pyc /usr/share/vdsm-bootstrap/interface-2/deployUtil.pyo /usr/share/vdsm-bootstrap/interface-2/setup /usr/share/vdsm-bootstrap/interface-2/vds_bootstrap.py /usr/share/vdsm-bootstrap/interface-2/vds_bootstrap.pyc /usr/share/vdsm-bootstrap/interface-2/vds_bootstrap.pyo /usr/share/vdsm-bootstrap/interface-2/vds_bootstrap_complete.py /usr/share/vdsm-bootstrap/interface-2/vds_bootstrap_complete.pyc /usr/share/vdsm-bootstrap/interface-2/vds_bootstrap_complete.pyo /usr/share/vdsm/debugPluginClient.py /usr/share/vdsm/debugPluginClient.pyc /usr/share/vdsm/debugPluginClient.pyo /usr/share/vdsm/nwfilter.py /usr/share/vdsm/nwfilter.pyc /usr/share/vdsm/nwfilter.pyo /usr/share/vdsm/tests/glob_1c60971a-8647-44ac-ae33-6520887f8843.out /usr/share/vdsm/tests/lvs_3386c6f2-926f-42c4-839c-38287fac8998.out /usr/share/vdsm/tests/route_info.out /usr/share/vdsm/tests/tc_filter_show.out /usr/share/vdsm/vdsmDebugPlugin.py /usr/share/vdsm/vdsmDebugPlugin.pyc /usr/share/vdsm/vdsmDebugPlugin.pyo
RPM build errors: Installed (but unpackaged) file(s) found: /usr/lib64/python2.7/site-packages/vdsm/tool/load_needed_modules.py /usr/lib64/python2.7/site-packages/vdsm/tool/load_needed_modules.pyc /usr/lib64/python2.7/site-packages/vdsm/tool/load_needed_modules.pyo /usr/libexec/vdsm/hooks/after_vdsm_stop/10_faqemu /usr/share/vdsm-bootstrap/interface-2/deployUtil.py /usr/share/vdsm-bootstrap/interface-2/deployUtil.pyc /usr/share/vdsm-bootstrap/interface-2/deployUtil.pyo /usr/share/vdsm-bootstrap/interface-2/setup /usr/share/vdsm-bootstrap/interface-2/vds_bootstrap.py /usr/share/vdsm-bootstrap/interface-2/vds_bootstrap.pyc /usr/share/vdsm-bootstrap/interface-2/vds_bootstrap.pyo /usr/share/vdsm-bootstrap/interface-2/vds_bootstrap_complete.py /usr/share/vdsm-bootstrap/interface-2/vds_bootstrap_complete.pyc /usr/share/vdsm-bootstrap/interface-2/vds_bootstrap_complete.pyo /usr/share/vdsm/debugPluginClient.py /usr/share/vdsm/debugPluginClient.pyc /usr/share/vdsm/debugPluginClient.pyo /usr/share/vdsm/nwfilter.py /usr/share/vdsm/nwfilter.pyc /usr/share/vdsm/nwfilter.pyo /usr/share/vdsm/tests/glob_1c60971a-8647-44ac-ae33-6520887f8843.out /usr/share/vdsm/tests/lvs_3386c6f2-926f-42c4-839c-38287fac8998.out /usr/share/vdsm/tests/route_info.out /usr/share/vdsm/tests/tc_filter_show.out /usr/share/vdsm/vdsmDebugPlugin.py /usr/share/vdsm/vdsmDebugPlugin.pyc /usr/share/vdsm/vdsmDebugPlugin.pyo make: *** [rpm] Error 1
Any idea?
Thanks, Itzik
----- Original Message -----
From: "Itzik Brown" ItzikB@mellanox.com To: vdsm-devel@lists.fedorahosted.org Sent: Wednesday, September 19, 2012 5:12:28 PM Subject: [vdsm] Problem building vdsm RPM
I'm trying to build vdsm from git . After make rpm I get these errors:
<snip>
How exactly do you try to build?
This is what working for me:
$ git clone ... $ cd vdsm $ autoreconf -ivf $ ./configure $ make dist $ rpmbuild -tb vdsm*.gz
Alon.
----- Original Message -----
From: "Alon Bar-Lev" alonbl@redhat.com To: "Itzik Brown" ItzikB@mellanox.com Cc: vdsm-devel@lists.fedorahosted.org Sent: Wednesday, September 19, 2012 4:18:08 PM Subject: Re: [vdsm] Problem building vdsm RPM
----- Original Message -----
From: "Itzik Brown" ItzikB@mellanox.com To: vdsm-devel@lists.fedorahosted.org Sent: Wednesday, September 19, 2012 5:12:28 PM Subject: [vdsm] Problem building vdsm RPM
I'm trying to build vdsm from git . After make rpm I get these errors:
<snip>
How exactly do you try to build?
This is what working for me:
$ git clone ... $ cd vdsm $ autoreconf -ivf $ ./configure $ make dist $ rpmbuild -tb vdsm*.gz
The suggested way of building vdsm is:
(clone and cd vdsm) $ ./autogen.sh --system $ make rpm
----- Original Message -----
From: "Federico Simoncelli" fsimonce@redhat.com To: "Alon Bar-Lev" alonbl@redhat.com Cc: vdsm-devel@lists.fedorahosted.org, "Itzik Brown" ItzikB@mellanox.com Sent: Thursday, September 20, 2012 1:06:53 PM Subject: Re: [vdsm] Problem building vdsm RPM
----- Original Message -----
From: "Alon Bar-Lev" alonbl@redhat.com To: "Itzik Brown" ItzikB@mellanox.com Cc: vdsm-devel@lists.fedorahosted.org Sent: Wednesday, September 19, 2012 4:18:08 PM Subject: Re: [vdsm] Problem building vdsm RPM
----- Original Message -----
From: "Itzik Brown" ItzikB@mellanox.com To: vdsm-devel@lists.fedorahosted.org Sent: Wednesday, September 19, 2012 5:12:28 PM Subject: [vdsm] Problem building vdsm RPM
I'm trying to build vdsm from git . After make rpm I get these errors:
<snip>
How exactly do you try to build?
This is what working for me:
$ git clone ... $ cd vdsm $ autoreconf -ivf $ ./configure $ make dist $ rpmbuild -tb vdsm*.gz
The suggested way of building vdsm is:
(clone and cd vdsm) $ ./autogen.sh --system $ make rpm
No reason for the --system, as rpmbuild will execute configure with right settings. Also, in most projects autogen does not run configure... this is something unique in vdsm I like to avoid. If there is a problem with rpmbuild -tb tarball, we need to fix it... is there any?
Alon.
----- Original Message -----
From: "Alon Bar-Lev" alonbl@redhat.com To: "Federico Simoncelli" fsimonce@redhat.com Cc: vdsm-devel@lists.fedorahosted.org, "Itzik Brown" ItzikB@mellanox.com Sent: Thursday, September 20, 2012 12:12:28 PM Subject: Re: [vdsm] Problem building vdsm RPM
----- Original Message -----
From: "Federico Simoncelli" fsimonce@redhat.com To: "Alon Bar-Lev" alonbl@redhat.com Cc: vdsm-devel@lists.fedorahosted.org, "Itzik Brown" ItzikB@mellanox.com Sent: Thursday, September 20, 2012 1:06:53 PM Subject: Re: [vdsm] Problem building vdsm RPM
----- Original Message -----
From: "Alon Bar-Lev" alonbl@redhat.com To: "Itzik Brown" ItzikB@mellanox.com Cc: vdsm-devel@lists.fedorahosted.org Sent: Wednesday, September 19, 2012 4:18:08 PM Subject: Re: [vdsm] Problem building vdsm RPM
----- Original Message -----
From: "Itzik Brown" ItzikB@mellanox.com To: vdsm-devel@lists.fedorahosted.org Sent: Wednesday, September 19, 2012 5:12:28 PM Subject: [vdsm] Problem building vdsm RPM
I'm trying to build vdsm from git . After make rpm I get these errors:
<snip>
How exactly do you try to build?
This is what working for me:
$ git clone ... $ cd vdsm $ autoreconf -ivf $ ./configure $ make dist $ rpmbuild -tb vdsm*.gz
The suggested way of building vdsm is:
(clone and cd vdsm) $ ./autogen.sh --system $ make rpm
No reason for the --system, as rpmbuild will execute configure with right settings.
Correct, but since you have to run it why keeping different (wrong) settings locally (vs. the ones that you'll be using in the rpm)?
Also, in most projects autogen does not run configure... this is something unique in vdsm I like to avoid.
Taken from libvirt, I don't see value in de-automating things.
If there is a problem with rpmbuild -tb tarball, we need to fix it... is there any?
The problem with your rpmbuild command is that it's not automatic enough, if you want to automate it you use wildcards (vdsm*.gz) which will build any vdsm tar.gz you find in the directory rather the one you just prepared (which is what make rpm is doing).
It's not that what you're saying is wrong (after all it's what autogen.sh and the Makefile rely upon, and it works for you), it's that what you do manually is already done automatically (with less potential errors and confusion for the newcomers).
----- Original Message -----
From: "Federico Simoncelli" fsimonce@redhat.com To: "Alon Bar-Lev" alonbl@redhat.com Cc: vdsm-devel@lists.fedorahosted.org, "Itzik Brown" ItzikB@mellanox.com Sent: Thursday, September 20, 2012 1:38:23 PM Subject: Re: [vdsm] Problem building vdsm RPM
----- Original Message -----
From: "Alon Bar-Lev" alonbl@redhat.com To: "Federico Simoncelli" fsimonce@redhat.com Cc: vdsm-devel@lists.fedorahosted.org, "Itzik Brown" ItzikB@mellanox.com Sent: Thursday, September 20, 2012 12:12:28 PM Subject: Re: [vdsm] Problem building vdsm RPM
----- Original Message -----
From: "Federico Simoncelli" fsimonce@redhat.com To: "Alon Bar-Lev" alonbl@redhat.com Cc: vdsm-devel@lists.fedorahosted.org, "Itzik Brown" ItzikB@mellanox.com Sent: Thursday, September 20, 2012 1:06:53 PM Subject: Re: [vdsm] Problem building vdsm RPM
----- Original Message -----
From: "Alon Bar-Lev" alonbl@redhat.com To: "Itzik Brown" ItzikB@mellanox.com Cc: vdsm-devel@lists.fedorahosted.org Sent: Wednesday, September 19, 2012 4:18:08 PM Subject: Re: [vdsm] Problem building vdsm RPM
----- Original Message -----
From: "Itzik Brown" ItzikB@mellanox.com To: vdsm-devel@lists.fedorahosted.org Sent: Wednesday, September 19, 2012 5:12:28 PM Subject: [vdsm] Problem building vdsm RPM
I'm trying to build vdsm from git . After make rpm I get these errors:
<snip>
How exactly do you try to build?
This is what working for me:
$ git clone ... $ cd vdsm $ autoreconf -ivf $ ./configure $ make dist $ rpmbuild -tb vdsm*.gz
The suggested way of building vdsm is:
(clone and cd vdsm) $ ./autogen.sh --system $ make rpm
No reason for the --system, as rpmbuild will execute configure with right settings.
Correct, but since you have to run it why keeping different (wrong) settings locally (vs. the ones that you'll be using in the rpm)?
Also, in most projects autogen does not run configure... this is something unique in vdsm I like to avoid.
Taken from libvirt, I don't see value in de-automating things.
If there is a problem with rpmbuild -tb tarball, we need to fix it... is there any?
The problem with your rpmbuild command is that it's not automatic enough, if you want to automate it you use wildcards (vdsm*.gz) which will build any vdsm tar.gz you find in the directory rather the one you just prepared (which is what make rpm is doing).
It's not that what you're saying is wrong (after all it's what autogen.sh and the Makefile rely upon, and it works for you), it's that what you do manually is already done automatically (with less potential errors and confusion for the newcomers).
Well, my view is that there is a standard method of creating rpms out of source tree.
Newcomers that have done this on one project can reuse their knowledge to do this in another project.
There is no need to create custom unique methods to confuse people.
Regards, Alon.
----- Original Message -----
From: "Alon Bar-Lev" alonbl@redhat.com To: "Federico Simoncelli" fsimonce@redhat.com Cc: vdsm-devel@lists.fedorahosted.org, "Itzik Brown" ItzikB@mellanox.com Sent: Thursday, September 20, 2012 12:41:58 PM Subject: Re: [vdsm] Problem building vdsm RPM
----- Original Message -----
From: "Federico Simoncelli" fsimonce@redhat.com To: "Alon Bar-Lev" alonbl@redhat.com Cc: vdsm-devel@lists.fedorahosted.org, "Itzik Brown" ItzikB@mellanox.com Sent: Thursday, September 20, 2012 1:38:23 PM Subject: Re: [vdsm] Problem building vdsm RPM
The problem with your rpmbuild command is that it's not automatic enough, if you want to automate it you use wildcards (vdsm*.gz) which will build any vdsm tar.gz you find in the directory rather the one you just prepared (which is what make rpm is doing).
It's not that what you're saying is wrong (after all it's what autogen.sh and the Makefile rely upon, and it works for you), it's that what you do manually is already done automatically (with less potential errors and confusion for the newcomers).
Well, my view is that there is a standard method of creating rpms out of source tree.
That is why I pushed for autotools, so experienced people can use it in all the way they prefer.
Newcomers that have done this on one project can reuse their knowledge to do this in another project.
There is no need to create custom unique methods to confuse people.
Are you suggesting that "./autogen.sh && make rpm" is "unique"?
----- Original Message -----
From: "Federico Simoncelli" fsimonce@redhat.com To: "Alon Bar-Lev" alonbl@redhat.com Cc: vdsm-devel@lists.fedorahosted.org, "Itzik Brown" ItzikB@mellanox.com Sent: Thursday, September 20, 2012 2:15:58 PM Subject: Re: [vdsm] Problem building vdsm RPM
----- Original Message -----
From: "Alon Bar-Lev" alonbl@redhat.com To: "Federico Simoncelli" fsimonce@redhat.com Cc: vdsm-devel@lists.fedorahosted.org, "Itzik Brown" ItzikB@mellanox.com Sent: Thursday, September 20, 2012 12:41:58 PM Subject: Re: [vdsm] Problem building vdsm RPM
----- Original Message -----
From: "Federico Simoncelli" fsimonce@redhat.com To: "Alon Bar-Lev" alonbl@redhat.com Cc: vdsm-devel@lists.fedorahosted.org, "Itzik Brown" ItzikB@mellanox.com Sent: Thursday, September 20, 2012 1:38:23 PM Subject: Re: [vdsm] Problem building vdsm RPM
The problem with your rpmbuild command is that it's not automatic enough, if you want to automate it you use wildcards (vdsm*.gz) which will build any vdsm tar.gz you find in the directory rather the one you just prepared (which is what make rpm is doing).
It's not that what you're saying is wrong (after all it's what autogen.sh and the Makefile rely upon, and it works for you), it's that what you do manually is already done automatically (with less potential errors and confusion for the newcomers).
Well, my view is that there is a standard method of creating rpms out of source tree.
That is why I pushed for autotools, so experienced people can use it in all the way they prefer.
Newcomers that have done this on one project can reuse their knowledge to do this in another project.
There is no need to create custom unique methods to confuse people.
Are you suggesting that "./autogen.sh && make rpm" is "unique"?
Well... as far as I know more common is: $ ./autogen $ ./configure $ make rpm
While I don't see the "make rpm" is required, I do not really care, as far as there is no magic hidden within... so that when we will publish release tarballs for download (using make dist of course no magic), people can simply do rpmbuild -tb on these to produce valid rpms.
In the past people needed to use aclocal, autoconf, libtool, automake, gettext in proper sequence in order to produce build environment. autogen(or any script) was born to automate this task, the task of producing build environment so that configure could be executed.
These days a single 'autoreconf -ivf' is doing exactly what in the past was complex, hence no autogen is required any more... but I don't care project putting a single command just for keep the name...
Thanks, Alon.
----- Original Message -----
From: "Alon Bar-Lev" alonbl@redhat.com To: "Federico Simoncelli" fsimonce@redhat.com Cc: vdsm-devel@lists.fedorahosted.org, "Itzik Brown" ItzikB@mellanox.com Sent: Thursday, September 20, 2012 1:29:00 PM Subject: Re: [vdsm] Problem building vdsm RPM
----- Original Message -----
From: "Federico Simoncelli" fsimonce@redhat.com To: "Alon Bar-Lev" alonbl@redhat.com Cc: vdsm-devel@lists.fedorahosted.org, "Itzik Brown" ItzikB@mellanox.com Sent: Thursday, September 20, 2012 2:15:58 PM Subject: Re: [vdsm] Problem building vdsm RPM
----- Original Message -----
From: "Alon Bar-Lev" alonbl@redhat.com To: "Federico Simoncelli" fsimonce@redhat.com Cc: vdsm-devel@lists.fedorahosted.org, "Itzik Brown" ItzikB@mellanox.com Sent: Thursday, September 20, 2012 12:41:58 PM Subject: Re: [vdsm] Problem building vdsm RPM
----- Original Message -----
From: "Federico Simoncelli" fsimonce@redhat.com To: "Alon Bar-Lev" alonbl@redhat.com Cc: vdsm-devel@lists.fedorahosted.org, "Itzik Brown" ItzikB@mellanox.com Sent: Thursday, September 20, 2012 1:38:23 PM Subject: Re: [vdsm] Problem building vdsm RPM
The problem with your rpmbuild command is that it's not automatic enough, if you want to automate it you use wildcards (vdsm*.gz) which will build any vdsm tar.gz you find in the directory rather the one you just prepared (which is what make rpm is doing).
It's not that what you're saying is wrong (after all it's what autogen.sh and the Makefile rely upon, and it works for you), it's that what you do manually is already done automatically (with less potential errors and confusion for the newcomers).
Well, my view is that there is a standard method of creating rpms out of source tree.
That is why I pushed for autotools, so experienced people can use it in all the way they prefer.
Newcomers that have done this on one project can reuse their knowledge to do this in another project.
There is no need to create custom unique methods to confuse people.
Are you suggesting that "./autogen.sh && make rpm" is "unique"?
Well... as far as I know more common is: $ ./autogen $ ./configure $ make rpm
While I don't see the "make rpm" is required, I do not really care, as far as there is no magic hidden within... so that when we will publish release tarballs for download (using make dist of course no magic), people can simply do rpmbuild -tb on these to produce valid rpms.
In the past people needed to use aclocal, autoconf, libtool, automake, gettext in proper sequence in order to produce build environment. autogen(or any script) was born to automate this task, the task of producing build environment so that configure could be executed.
These days a single 'autoreconf -ivf' is doing exactly what in the past was complex, hence no autogen is required any more... but I don't care project putting a single command just for keep the name...
It's not like anyone is preventing you from doing what you think is the best. The build system already supports what you want to do.
vdsm-devel@lists.stg.fedorahosted.org
-
Alon Bar-Lev -
Federico Simoncelli -
Itzik Brown