build-source should output the changes file it created

[Christian Ehrhardt ]

On a normal build-source call like:
$ git ubuntu build-source --verbose --sign --for-merge

I get all I need (verbose) but even in that mode it doesn't list me what it actually created.

I love on dpkg-buildpackage that it ends with an output like:
 signfile sysstat_11.5.7-1_source.changes

That way one doesn't have to rely on
$ cd ..
$ ls -ltr *.changes
or anything like it, you can just take the changes file that was put on your screen for a dput.

I'd think it would be great to add something like this to the verbose mode:
[...]
Created ../pkg_version_source.changes

I think I'd like it, but I need other opinions - so what do you think?

[Nish Aravamudan (nacc)]

I am not 100% on how to solve this generically. It would be ideal if successful builds outputted all the files they create, but there doesn't appear to be any programmatic way to get this information.

I could output the dpkg-buildpackage output directly to the console on success?

Or, I could special-case source-package builds (since if you do a binary build, I think it's possible to generate other files we care about) and at least output the *expected* source.changes file if it exists?

[Christian Ehrhardt  (paelzer)]

Yeah it is a pity that you have to guess what is created.

How about:
- in Verbose: "output the dpkg-buildpackage output directly to the console"
- in General: output the *expected* source.changes file if it exists

When you say "if it exists" I'd add on top "and is newer than when the build stated" to be more sure we crated it.

[Nish Aravamudan (nacc)]

The new lxd based build branch (not yet landed) ends with:

09/13/2017 14:20:00 - INFO:Successfully built:
../postfix_3.2.2-1.debian.tar.xz
../postfix_3.2.2-1_source.buildinfo
../postfix_3.2.2-1.dsc
../postfix_3.2.2-1_source.changes
using fetch_orig_from_parent_dir(source=None)

[Christian Ehrhardt  (paelzer)]

That would be sufficient for me I think.