[Spacewalk-list] tito build of spacewalk git sources

[Stephen Herr]

Hi Andy,

Tito will always work with the most recent version in git. If you run 
with --test it is the most recent git commit, period. If you don't run 
with --test then it's the most recent version that has been tagged in 
git. Tito will never pick up changes that have not been committed yet, 
which yes can lead to difficulty when trying to fix build errors.

The workflow I usually use when I have tito build problems is to
1) fix whatever I think needs to be changed, git commit.
Then, before pushing the changes to my upstream repo (if any), try a 
'tito build --rpm --test --offline'. If other errors are present or if 
the first fix didn't actually fix anything, then
2) continue fixing, git commit --amend
This keeps all your fixes in that most recent commit. Then once 
everything is finally working again, you can push your single git commit 
upstream (if any).

-Stephen

On 02/12/2013 11:50 AM, genanr wrote:
> How does TITO work?
>
> I understand the tito build --rpm --test to build rpms, but my problem 
> comes when I run into a problem with one of the files.
>
> In spacewalk/admin I ran tito build --rpm --test and pod2man 
> complained about an missing =back in validate-sat-cert.pod.  This is 
> fine, and I added the =back before the =head at line 35.
>
> Then, when I re-run tito build --rpm --test, it still manages to find 
> the error at the same line even though running pod2man on the file I 
> get no errors.  I can even delete the file and the tito command still 
> gives me the same error.  Where is it getting the file?  In the good 
> old day you wound run make, fix errors, run make and every would be 
> fine.  Tito seems to be pulling old files out of the air.
>
> There must be something I am missing, but I do not know what it is.
>
> Andy
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list