Sean Whitton <spwhit...@spwhitton.name> 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. > Wouldn't dgit have to connect to the Internet in order to perform the > detection? > I'm not sure we want a build command performing any connections. 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 *.changes file to know the binary package list, since it doesn't know that any *.changes file is from the same package that one is calling push-source on. -- Russ Allbery (r...@debian.org) <https://www.eyrie.org/~eagle/>
