From: "lofyer" <lofyer(a)gmail.com>
To: "Alon Bar-Lev" <alonbl(a)redhat.com>
Cc: "Itamar Heim" <iheim(a)redhat.com>, "Sandro Bonazzola"
<sbonazzo(a)redhat.com>, "users" <users(a)ovirt.org>
Sent: Friday, June 21, 2013 3:29:12 PM
Subject: Re: [Users] Cannot make rpm
δΊ 2013/6/21 19:43, Alon Bar-Lev ει:
>
> ----- Original Message -----
>> From: "Itamar Heim" <iheim(a)redhat.com>
>> To: "Sandro Bonazzola" <sbonazzo(a)redhat.com>
>> Cc: "lof yer" <lofyer(a)gmail.com>, "users"
<users(a)ovirt.org>
>> Sent: Friday, June 21, 2013 2:14:43 PM
>> Subject: Re: [Users] Cannot make rpm
>>
>> On 06/21/2013 09:18 AM, Sandro Bonazzola wrote:
>>> Hi,
>>> patch already pushed for review:
http://gerrit.ovirt.org/15963
>> was this breakage detected by jenkins automatically?
> we do not use this target any more.
> I wish to remove it from Makefile.
> there is no sense in adding these into each makefile... there is a standard
> sequence to do so...
>
> make dist
>
> then:
>
> rpmbuild -ts <tarball>
> rpmbuild --rebuild <srpm>
>
> or:
>
> rpmbuild -tb <tarball>
>
> if tarball is in correct format, there is no need for project specific
> targets.
>
>>>
>>> Il 21/06/2013 04:10, lof yer ha scritto:
>>>> I wanted to make rpm from the lastest src, but failed.
>>>> Here's my log:
>>>>
>>>> git ls-files | tar --files-from /proc/self/fd/0 -czf
>>>> "ovirt-engine-3.3.0_master.tar.gz" ovirt-engine.spec
>>>>
>>>> You can use rpmbuild -tb ovirt-engine-3.3.0_master.tar.gz to produce
>>>> rpms
>>>>
>>>> rm -rf "/home/demo/gittest/ovirt-engine/tmp.rpmbuild"
>>>> mkdir -p
>>>>
"/home/demo/gittest/ovirt-engine/tmp.rpmbuild"/{SPECS,RPMS,SRPMS,SOURCES,BUILD,BUILDROOT}
>>>> mkdir -p "output"
>>>> rpmbuild -ts --define="_topdir
>>>> /home/demo/gittest/ovirt-engine/tmp.rpmbuild"
>>>> "ovirt-engine-3.3.0_master.tar.gz"
>>>> Wrote:
>>>>
/home/demo/gittest/ovirt-engine/tmp.rpmbuild/SRPMS/ovirt-engine-3.3.0-0.2.master.20130621014614.fc18.src.rpm
>>>> mv "/home/demo/gittest/ovirt-engine/tmp.rpmbuild/SRPMS"/*.rpm
"output"
>>>> rm -rf "/home/demo/gittest/ovirt-engine/tmp.rpmbuild"
>>>>
>>>> srpm is ready at output
>>>>
>>>> rm -rf "/home/demo/gittest/ovirt-engine/tmp.rpmbuild"
>>>> mkdir -p
>>>>
"/home/demo/gittest/ovirt-engine/tmp.rpmbuild"/{SPECS,RPMS,SRPMS,SOURCES,BUILD,BUILDROOT}
>>>> mkdir -p "output"
>>>> rpmbuild --define="_topdir
/home/demo/gittest/ovirt-engine/tmp.rpmbuild"
>>>> --rebuild "output/ovirt-engine-3.3.0*.src.rpm"
>>>> error: cannot open output/ovirt-engine-3.3.0*.src.rpm: No such file or
>>>> directory
>>>> make: *** [rpm] Error 1
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Users mailing list
>>>> Users(a)ovirt.org
>>>>
http://lists.ovirt.org/mailman/listinfo/users
>>>
>>> --
>>> Sandro Bonazzola
>>> Better technology. Faster innovation. Powered by community collaboration.
>>> See how it works at
redhat.com
>>>
>>>
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users(a)ovirt.org
>>>
http://lists.ovirt.org/mailman/listinfo/users
>>>
>> _______________________________________________
>> Users mailing list
>> Users(a)ovirt.org
>>
http://lists.ovirt.org/mailman/listinfo/users
>>
Will you? But I think it is quite convinient for us to test new features
from source.
The standard way of:
# make dist
# rpmbuild -tb <tarball>
is common to most of packages within rpm environment, and allow you to "test new
features from source".
no need to re-invent the wheel, or hide the standard sequence from developers, knowing
that will enable them to feel comfortable in other environments/packages as well.
in the old days, the tabrall did not contain the spec file correctly, so using the
standard sequence was impossible.
can you please try this sequence?
thanks,
Alon