Hello,
On Sun 27 Oct 2019 at 12:22PM -07, Russ Allbery wrote:
> My thought process was more that since I've run dgit sbuild, there's a
> *.changes file that lists all the binary packages that the source builds.
> But there probably isn't any reasonable way for push-source to be able to
> use that
Sean Whitton writes:
> On Sat 26 Oct 2019 at 03:54PM -07, Russ Allbery wrote:
>> For what it's worth, I also always follow a practice of running dgit
>> sbuild before dgit push-source, so dgit could have detected the binary
>> packages that way in theory, but I'm not sure if that's common.
> Wou
Hello Russ,
On Sat 26 Oct 2019 at 03:54PM -07, Russ Allbery wrote:
> For what it's worth, I also always follow a practice of running dgit
> sbuild before dgit push-source, so dgit could have detected the binary
> packages that way in theory, but I'm not sure if that's common.
Wouldn't dgit have
Package: dgit
Version: 9.9
Followup-For: Bug #903090
For the purposes of tracking interest, I just ran into this problem with
a package that introduced a new binary package, and would also like dgit
to be able to detect this situation and warn me before doing a
push-source. Parsing debian/control
4 matches
Mail list logo
