Le Sat, Oct 20, 2012 at 06:29:50PM +0200, Bernhard R. Link a écrit : > * Chow Loong Jin <hyper...@debian.org> [121020 18:10]: > > The only argument I have seen for binary uploads is to ensure that DDs have > > built the package prior to uploading it. But as someone else pointed out > > earlier > > in the thread, we seem to be trusting DDs a lot in other aspects, so why not > > trust that they test-build packages prior to uploading them as well? > > Having the binary file around, even if it is not easily accessible > on some remote archive, noone can claim "I tested this, it just did > work here, something must be different on the buildds" and hope to > get away with it.
In the end, it is not so relevant that a local build could work on the DD's machine. With source uploads, we will switch from a model where most of the packages that our users install were built and tested by hand, to a model where most pakcages were autobuilt. In that model, it will be important that after the build, one developer downloads the binary packages and tests them. The 10 days of staging in Unstable do not offer much protection when packages have a small number of users who are not upgrading their system every week. In that context, it would be helpful to have an email notification after the packcages are autobuilt on amd64. For command-line programs, regression tests with autopkgtest will also be instrumental in helping developers to ensure that binary packages are functional. (http://dep.debian.net/deps/dep8/) Have a nice Sunday, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121021004724.gb23...@falafel.plessy.net
