On Thu, Nov 24, 2016 at 07:24:31AM +0000, Gianfranco Costamagna wrote: > Hi Gustavo, > > > >can i ask you why are you doing source-only uploads? > > > >i did a lot of binary+source uploads in the last days without an issue > >(after removing > >.buildinfo from .changes) > > > knowing that mentors discards binaries (and sponsors should do it anyway), > what is the > reason for uploading them, other than wasting bandwidth? :)
to be honest, i don't have a good reason besides testing the resulting deb and that is my existing workflow i do sbuild or pdebuilder or export GIT_PBUILDER_OPTIONS=--twice ; export ARCH=amd64 ;export DIST=sid; \ gbp buildpackage --git-builder=git-pbuilder -d --git-verbose on top of a debian source tree and it always works, so why change? > > I think a source-only upload is more error-prone than a manual edit of > changes file, > and source-only have lots of reasons to exist, so why don't use them? :p i'm not sure i follow you here, but here goes my reasoning anyway ftp-master will request a binary upload, so why don't do the same for mentors since is the very thing you're going to be doing later down the road. i'd love if ftp-master accepted source only or even better discard the uploaded binaries, but is not the way it is today i'm very tempted to do uploads to debian using !amd64 binaries to be sure that the binary used by (most of the) users hasn't been build by me but a buildd! > > BTW congrats for your nm process end! > > Gianfranco -- 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333 keybase: https://keybase.io/gfa
