> Thank you for doing this Jeremy. One minor nit to pick is that some of > these failed builds are impossible to debug and hence fix without more > information than is present in the <package>.failure.log file. The most > information that file provides is: "the build failed, if you could > access this local file, you might be able to figure out why. nya, nya, > nya". Which, when you're trying to figure out why the build failed on > an architecture to which you have no access, is more than useless and > quite a bit frustrating. The 4.5M rpm log is, of course, present when > the build succeeds. This seems, uh, backwards to me. > > Seth? Any chance you could change those build scripts to copy the > rpm.log file when the build fails in addition to when it succeeds? The logging problem has been taken care of in mock. Mach currently still does some odd things with saving logs where one might expect them to be. -sv
