This is strange. About an hour after I sent the original report, I sent a close
request, and explained in it that I'd found the issue. It seems to have not
gone through!
On Sun, 27 Jul 2014 15:05:48 -0400 Caitlin Matos
wrote
It was because I had somehow del
It was because I had somehow deleted the "s" for replacing the version. So in
my gbp.conf, it said:
[import-orig]
post-import = git-dch -N%(version) -a
instead of
[import-orig]
post-import = git-dch -N%(version)s -a
Once I figured that out and switched it back, it worked fine.
But a clearer
On Sat, Jul 26, 2014 at 08:44:26PM -0400, Caitlin Matos wrote:
> gbp:debug: ['git', 'merge', '--no-summary', '--no-edit', 'upstream/0.19.0']
> Traceback (most recent call last):
> File "/usr/bin/gbp", line 9, in
> load_entry_point('gbp==0.6.15', 'console_scripts', 'gbp')()
> File "/usr/l
Package: git-buildpackage
Version: 0.6.15
Severity: normal
See the output below. Note that HEAD currently points to 1df8973; it may
have changed by the time someone tries to replicate this, so if you're
not seeing the same problem, try doing a git reset!
$ gbp import-orig --verbose --uscan
gbp:in
4 matches
Mail list logo