Bug#850478: git-pbuilder deliberately deletes source.changes

[Russ Allbery]

Mattia Rizzolo <mattia at debian.org> writes:
> On Fri, Jan 06, 2017 at 06:18:14PM -0800, Russ Allbery wrote:

>> Yeah, it does that because I didn't know how to do better (and this
>> started life as my personal script for my workflow, and at the time all
>> *_source.changes files were garbage).

> umh, $pkg_$version_source.changes? :)

Okay, how do I get $pkg and $version?  :)  git-pbuilder right now doesn't
know any of that stuff.  I suppose I could try to parse debian/changelog
using dpkg-parsechangelog or something....

But if pdebuild stops generating the bad *_source.changes file, then I can
just delete all that code and everything becomes easier.

>> >     Now, I'm of the view that dpkg-source -b should be used instead,
>> >     which is what sbuild uses to create the dsc. This also has the
>> >     advantage of not generating .buildinfo files (no annoying
>> >     debian/files lingering after the build, either). Then the only
>> >     _source.changes generated by pbuilder would be if the user requested
>> >     it, and therefore having it deleted by git-pbuilder would be wrong.
>> 
>> Yeah, this seems reasonable to me.  Definitely happy to change
>> git-pbuilder once pdebuild is fixed to not produce the spurious and
>> useless *_changes.file.

> Indeed, is this a suggestion for pdebuild?

Yeah, I think you might not have gotten the original message, since I
think the X-Debugs-Cc may have been in the wrong spot?

-- 
Russ Allbery (rra at debian.org)               <http://www.eyrie.org/~eagle/>