When using `git-buildpackage -S` to produce a source package, it can manage to successfully build everything, but then gets to this part in /usr/bin/pbuilder:
if [ -n "`ls ../*_source.changes`" ] ; then
rm ../*_source.changes
fi
This means that after the successful -S build, it will proceed to delete the source.changes file. This is the file that you need to give to dput for submitting packages to a launchpad PPA, for example. Since the file is deleted, an argument like --git-postbuild='lintian $GBP_CHANGES_FILE' will cause the build to fail because the file at '$GBP_CHANGES_FILE' is the source.changes file that it just deleted.
I can't see any configuration that will fix this, because the deletion isn't wrapped in any conditionals. Am I missing something? I would very much like to bypass the deletion when building source packages. For now, I've just commented out the three lines above and I get the desired behaviour.
(git-buildpackage 0.6.9 from the trusty repositories)
When using `git-buildpackage -S` to produce a source package, it can manage to successfully build everything, but then gets to this part in /usr/bin/pbuilder:
if [ -n "`ls ../*_source. changes` " ] ; then
rm ../*_source.changes
fi
This means that after the successful -S build, it will proceed to delete the source.changes file. This is the file that you need to give to dput for submitting packages to a launchpad PPA, for example. Since the file is deleted, an argument like --git-postbuild ='lintian $GBP_CHANGES_FILE' will cause the build to fail because the file at '$GBP_CHANGES_FILE' is the source.changes file that it just deleted.
I can't see any configuration that will fix this, because the deletion isn't wrapped in any conditionals. Am I missing something? I would very much like to bypass the deletion when building source packages. For now, I've just commented out the three lines above and I get the desired behaviour.
(git-buildpackage 0.6.9 from the trusty repositories)