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
<caitlin.ma...@zoho.com> wrote ----
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 error message would definitely be appreciated!
---- On Sun, 27 Jul 2014 03:24:51 -0400 Guido Günther <a...@sigxcpu.org>
wrote ----
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 <module>
> load_entry_point('gbp==0.6.15', 'console_scripts', 'gbp')()
> File "/usr/lib/python2.7/dist-packages/gbp/scripts/supercommand.py", line
82, in supercommand
> return module.main(args)
> File "/usr/lib/python2.7/dist-packages/gbp/scripts/import_orig.py", line
375, in main
> gbpc.Command(options.postimport % info, extra_env=env, shell=True)()
> ValueError: unsupported format character 'a' (0x61) at index 22
Can you attach the output of
gbp config import-orig
it looks like your postimport hook is broken (we should fail with a
clearer error in that case).
Cheers,
-- Guido
