Make a git commit and then 'tito build --test --rpm'; it sounds like you're still just building from HEAD that doesn't include your fix.
/aron -----Original Message----- Date: Tue, 12 Feb 2013 10:50:01 -0600 From: genanr <ar...@allantgroup.com> To: "spacewalk-list@redhat.com" <spacewalk-list@redhat.com> Subject: [Spacewalk-list] tito build of spacewalk git sources Message-ID: <511a72b9.80...@allantgroup.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list End of Spacewalk-list Digest, Vol 57, Issue 15 ********************************************** _______________________________________________ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
