Re: [Ltib] spec file pulling from CVS

[Stuart Hughes]

Hi Andrea,

I've checked in a change that should fix this.  It is all a bit
convoluted due to the way rpm builds and the fact we have directory
packages that may or may not create directories under rpm/BUILD (kernels
directory builds for example).

The change says that for 'local' packages (e.g. ones with no source
tarballs) only do a scbuild/scdeploy rebuild if:

a normal build (./ltib -p pkg)  _AND_  an rpm has been built before

This makes sure that the real directory to build in must have been
created before either by:

./ltib -p <pkg> -m prep
or:
./ltib -p <pkg>

In the second case, bypassing the scbuild/scdeploy rebuild will cause an
normal rpmbuild, which calls the prep section, thus creating (if
necessary) creates the real build directory.

Regards, Stuart

Stuart Hughes wrote:
> Hi Andrea,
> 
> It looks like a case I've not taken care of with that change.  Let me
> look later on (I'm tied up on other things right now).  In the mean
> time, please work-around using the -m prep etc.
> 
> Regards, Stuart
> 
> Andrea Galbusera wrote:
>> Stuart,
>> sorry for bothering you again on this... My last test was to go for a 
>> straight build of the package by issuing 
>> a ./ltib -p tpt2000-cvs.spec (no previous run with -m prep). Below is the 
>> output I get. To me it looks like 
>> ltib thinking that a source directory should be already available, instead 
>> of executing %prep and checking out things from CVS.
>> Do I miss something? Do I have to reset any "cached state" of previous run 
>> or something like that?
>>
>> TIA
>> Andrea
>>
>>> $ ./ltib -p tpt2000-cvs.spec
>>>
>>> Processing platform: Tecnint MPC512x based boards
>>> ===================================================
>>> using config/platform/mpc5121tpt/.config
>>>
>>> Processing: tpt2000-cvs
>>> =========================
>>> Build path taken because: directory build, no prebuilt rpm, 
>>> scbuild/scdeploy already unpacked package
>>>
>>> Processing: tpt2000-cvs
>>> =========================
>>> Build path taken because: directory build, build key set, no prebuilt rpm, 
>>>
>>> rpmbuild --dbpath 
>>> /home/gizero/work/tpt/mpc5121/ltib-tpt/rootfs//var/lib/rpm 
>>> --target ppc --define '_unpackaged_files_terminate_build 0' --define 
>>> '_target_cpu ppc' 
>>> --define '__strip strip' --define '_topdir 
>>> /home/gizero/work/tpt/mpc5121/ltib-tpt/rpm' 
>>> --define '_prefix /usr' --define '_tmppath 
>>> /home/gizero/work/tpt/mpc5121/ltib-tpt/tmp' 
>>> --define '_rpmdir /home/gizero/work/tpt/mpc5121/ltib-tpt/rpm/RPMS'  
>>> --define '_mandir /usr/share/man' --define '_sysconfdir /etc' 
>>> --define '_localstatedir /var' -bc --short-circuit  
>>> /home/gizero/work/tpt/mpc5121/ltib-tpt/dist/lfs-5.1/tpt2000/tpt2000-cvs.spec
>>> Building target platforms: ppc
>>> Building for target ppc
>>> Executing(%build): /bin/sh -e 
>>> /home/gizero/work/tpt/mpc5121/ltib-tpt/tmp/rpm-tmp.41500
>>> + umask 022
>>> + cd /home/gizero/work/tpt/mpc5121/ltib-tpt/rpm/BUILD
>>> + cd /home/gizero/work/tpt/mpc5121/ltib-tpt/rpm/BUILD/tpt2000-local
>>> /home/gizero/work/tpt/mpc5121/ltib-tpt/tmp/rpm-tmp.41500: line 21: cd: 
>>> /home/gizero/work/tpt/mpc5121/ltib-tpt/rpm/BUILD/tpt2000-local: No such 
>>> file or directory
>>> error: Bad exit status from 
>>> /home/gizero/work/tpt/mpc5121/ltib-tpt/tmp/rpm-tmp.41500 (%build)
>>>
>>>
>>> RPM build errors:
>>>     Bad exit status from 
>>> /home/gizero/work/tpt/mpc5121/ltib-tpt/tmp/rpm-tmp.41500 (%build)
>>> Build time for tpt2000-cvs: 0 seconds
>>>
>>> Failed building tpt2000-cvs
>>>
>>>
>>> f_buildrpms() returned an error, exiting
>>> traceback:
>>>  main:566
>>>
>>>
>>> Started: Tue Mar 16 10:40:33 2010
>>> Ended:   Tue Mar 16 10:40:33 2010
>>> Elapsed: 0 seconds
>>>
>>> These packages failed to build:
>>> tpt2000-cvs 
>>>
>>> Build Failed
>>>
>>> Exiting on error or interrupt
>>
>>
>>
> 
> 
> _______________________________________________
> LTIB home page: http://ltib.org
> 
> Ltib mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/ltib
>