Hi, I removed the build logs for the double-build tests by mistake, so I re-ran all the builds.
This time, I commited the lists of failures to the collab-qa repository, under: collab-qa/archive-rebuilds/2007-09-05-doublebuild-unstable-main-i386 there are four lists: failed-build-1.txt (534 packages): packages that failed during the first build. Those should probably be ignored, as they are taken care of during the "normal" rebuilds failed-build-2.txt (371 packages): packages which failed during their second build. failed-build-3.txt (9 packages): packages that failed during their third build. failed-debdiff.txt (45 packages): packages that built fine three times in a row, but which generated files that were different from those generated when built only one time (according to debdiff). Like added files, removed files, etc. Those issues are probably severity:serious, since it might cause the silent generation of bogus packages. Also, there are some false positives, with packages that generate documentation in a non-deterministic way. All the logs are available under http://people.debian.org/~lucas/logs/2007/doublebuild-09-05/ A follow-up should probably be sent to all bug reports already opened[1], mentioning the new location for the logs, and some additional info (links to the relevant thread on -devel@, mention that the bug is subject to 0-day NMUs since it's a release goal, etc). And there's also a lot of new bugs to file. I think we should use the "normal" collab-qa procedure, modifying the lists in svn. This would make it easier if we do a third pass on this issue. Any comments? Ah, and I also commited "normal" rebuild results in 2007-09-05-unstable-main-i386. There are quite a lot of bugs to file, so if you have some free time ... :-) [1] http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=qa-doublebuild;[EMAIL PROTECTED] -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
