Package: git-buildpackage-rpm Version: 0.7.5 Severity: normal When exporting a patch series using 'gbp pq-rpm export', spec is updated to include them. However the patches are included with full pathes.
For instance: Patch0: /path/to/work/dir/0001-fix-problem.patch ... # /path/to/work/dir/0001-fix-problem.patch %patch0 -p1 Instead of: Patch0: 0001-fix-problem.patch ... # 0001-fix-problem.patch %patch0 -p1 The comment is a cometic issue, but the full path to the file would be wrong when the package is used in a different directory. Note that merely stripping out the full path would not do, as the user may use a packaging directory: Patch0: /path/to/work/dir/rpm/0001-fix-problem.patch ... # /path/to/work/dir/rpm/0001-fix-problem.patch %patch0 -p1 With should instead be: Patch0: rpm/0001-fix-problem.patch ... # rpm/0001-fix-problem.patch %patch0 -p1 -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: armhf Kernel: Linux 4.6.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=he_IL.UTF-8, LC_CTYPE=he_IL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages git-buildpackage-rpm depends on: ii cpio 2.11+dfsg-5 ii git-buildpackage 0.7.5 ii python-rpm 4.12.0.1+dfsg1-4 pn python:any <none> ii rpm 4.12.0.1+dfsg1-4 Versions of packages git-buildpackage-rpm recommends: ii pristine-tar 1.34 Versions of packages git-buildpackage-rpm suggests: ii mock 1.2.18-1 ii python-notify 0.1.1-4 ii unzip 6.0-20 ii zipmerge 1.1.2-1.1 -- no debconf information
