git-pbuilder removes necessary *_source.changes

Bug #1349103 reported by Carl Suster on 2014-07-27
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
git-buildpackage (Ubuntu)
Undecided
Unassigned

Bug Description

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)
---
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
InstallationDate: Installed on 2013-02-06 (536 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
Package: git-buildpackage 0.6.9 [modified: usr/bin/git-pbuilder]
PackageArchitecture: all
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Tags: trusty third-party-packages
Uname: Linux 3.13.0-32-generic x86_64
UpgradeStatus: Upgraded to trusty on 2014-05-02 (86 days ago)
UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo
_MarkForUpload: True

apport information

tags: added: apport-collected third-party-packages trusty
description: updated

apport information

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in git-buildpackage (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers