On Fri, Mar 10, 2017 at 12:55:44AM +0000, Ian Jackson wrote: > > PS: to be on the safe side I currently delete the *.deb and the > > *_amd64.changes from that directory before running `dgit dput`, so I'm > > sure it won't try to upload binaries but only the _source.changes. > > What's the heuristic dgit uses to pick a .changes file, and how would I > > do to avoid that extra work of removing the binaries? > > I think you may find -C useful: you can specify explicitly the > .changes file. dgit won't upload anything but whatever is in that.
Yeah, I used that a couple of times, but giving that it requires
changing every time I found it annoying (i.e. `dgit -wc
pu<pg_up><return>` is not enough as it is with --build-products-dir)
> Also, anyway, dgit is a bit cautious if it sees multiple .changes
> files. I think you will probably find it will complain, rather than
> doing the wrong thing. Try it with --damp-run and see ?
I will, at the next NMU :)
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
