On Tue, Oct 01, 2013 at 10:23:22PM +0100, Adam D. Barratt wrote: > > That looks okay. In terms of the other suggested updates, as a > non-release architecture for wheezy, hurd-specific patches aren't really > appropriate for a stable update.
Perhaps not appropriate to upload just for Hurd, but hurd-specific patches that don't touch other arches also seem harmless. I'm happy to back them out, though, if it's a sticking point. > * debian/testsuite-checking/compare.sh: Disable failing the build on test > regressions to ease the pain of ongoing stable/security maintenance. This has historically always been done for stable releases. I'm not going to argue if that's right or wrong, just history. Again, happy to back this one out, and let the security team actually deal with potential regressions from kernel changes and other fun on buildds. (For instance, there's a patch in sid that fixes a test that fails only on >> 3.11 kernels, which could eventually hit a wheezy security build... This sort of fragility is why the testsuite is usually made non-fatal for stable, because it's frustrating to have to fix tests that don't relate to the changes you just uploaded for). ... Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131002151402.gg16...@0c3.net
