-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jeremy Katz wrote: | I kicked off a number of Extras builds to try to sync up versions | between architectures. A lot have succeeded, but some have failed. If | you see a package you own in the list, if you could investigate the | failure, it would be much appreciated. I've done some preliminary | looking at the failures and tried to categorize them somewhat. I also | started out looking at the existing bugs to see if there were patches | that looked reasonable, but kind of gave up halfway through :) 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? - -- Shahms E. King <shahms@xxxxxxxxxx> Multnomah ESD Public Key: http://shahms.mesd.k12.or.us/~sking/shahms.asc Fingerprint: 1612 054B CE92 8770 F1EA AB1B FEAB 3636 45B2 D75B -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFCk1Ld/qs2NkWy11sRAhE/AJ97dTD6Unk4fqfbptW/FEdK2+xqEwCdFIhk Y9j2X5ypfQoij45y7HIU8MY= =saSC -----END PGP SIGNATURE-----
