On Thursday 20 November 2008 12:50:34 pm Fabian Arrotin wrote: > On Thu, 20 Nov 2008, Stefan Radman wrote: > > Sounds like a sensible proposal with all the information needed present. > > It would probably be useful to see who initiated the build process (for > > the feedback). > > > > The publicly accessible buildlogs have always been very useful for me as > > rpmforge user to give a focused feedback when a package was'nt available > > in the repo the main point being that they were publicly accessible for > > analysis. > > With the current state (buildlogs not publicly available) I can't be of > > any help in getting packages like GraphViz upgraded because I don't see > > where the build process fails and blindly bugging the packers every now > > and then is no fun. > > > > My 2 cents. > > Stefan > > Yep, that's a discussion we need to have .. > All the PPC package buildlogs are located @ > http://rpms.arrfab.net/rpmforge/_buildlogs/ PS : some older ppc logs are > still located on the build machine but available on request ;-)
I've put some info about the current build log formats on the wiki: https://rpmrepo.org/RPMforge/BuildlogFormat Fabian already added some info about his log format. The current log formats are quite different, so probably it isn't easy to switch each buildsystem to 1 fixed common format. Possible solution: * define a format for sections, for example with the '---' as used in Dag's logformat. * define a set of required sections, at least: o a general header with info about the build o the output of rpmbuild o the result of the rpmbuild command * allow additional sections, just like you can add additional X- headers in a mail * a standard name for the log file What do you think? Dries _______________________________________________ users mailing list [email protected] http://lists.rpmforge.net/mailman/listinfo/users
