On Tue, Dec 20, 2011 at 09:36:47PM +0100, Lucas Nussbaum wrote: > On 20/12/11 at 22:01 +0200, Peter Eisentraut wrote: > > With recent dpkg(-source) changes, many packages are again failing to > > build twice in a row, because of uncommitted upstream changes. Fixing > > this was a lenny release goal, maybe it should be one again?!? Most > > importantly, maybe someone who has access to one of those build grids > > can run the old tests again, because I feel by accidentally stumbling > > upon these problems we will not be able to find and fix many of them any > > time soon. > > Is it really worth it? There are many ways to work-around this, such as > using a temporary git repo to be able to 'git clean' and return to a > clean state before each build.
If I'm fixing an RC bug, it's very convenient to be able to test a patch and then rebuild with a different patch if necessary. If the package doesn't build cleanly N times in a row, or if there are other problems with the packaging that make it difficult to fix, I usually go on to fix other bugs instead. Also, when I file a bug report, the harder you make it to fix your package, the less likely you are to receive a patch with that report, workaround or not. -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
signature.asc
Description: Digital signature
