Mattia Rizzolo writes ("Bug#857316: dgit: please make --build-products-dir
configurable"):
> package: dgit
>
> I build my packages with pbuilder, and it is set up to put the results
> in ~/pbuilder/results/$distribution/$architecture/. I'd like dgit to go
> look for the .changes to upload there, and I currently accomplish that
> by passing `--build-products-dir ~/pbuilder/result/sid/amd64` to
> `dgit push`. I'd like to configure that statically, so I don't have to
> keep specifying it.
dgit needs better pbuilder integration generally. (There's another
bug for that.)
But I think a config option for the default --build-products-dir would
be a good thing too (or maybe part of that). So I agree with this bug
report.
> 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.
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 ?
Regards,
Ian.
--
Ian Jackson <ijack...@chiark.greenend.org.uk> These opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
