Package: git-buildpackage
Version: 0.6.0~git20120822
Severity: normal

Dear Maintainer,

I've been working on a branch named experimental. In this
branch. importing a new upstream version (with
--debian-branch=experimental) fails with a git-dch error. git-dch complains
that --debian-branch option is missing.

See the full output of the command:

$ git-import-orig --uscan --debian-branch=experimental 
--upstream-branch=upstream
gbp:info: Launching uscan...
gbp:info: using ../libconfig-model-perl_2.024.orig.tar.gz
What is the upstream version? [2.024] 
gbp:info: Importing '../libconfig-model-perl_2.024.orig.tar.gz' to branch 
'upstream'...
gbp:info: Source package is libconfig-model-perl
gbp:info: Upstream version is 2.024
pristine-tar: committed libconfig-model-perl_2.024.orig.tar.gz.delta to branch 
pristine-tar
gbp:info: Merging to 'experimental'
Switched to branch 'experimental'
Merge made by the 'recursive' strategy.
gbp:error: You are not on branch 'master' but on 'experimental'
gbp:error: Use --ignore-branch to ignore or --debian-branch to set the branch 
name.
gbp:error: Couldn't run 'git-dch -N2.024-1 -S -a': git-dch -N2.024-1 -S -a 
returned 1
gbp:error: Import of ../libconfig-model-perl_2.024.orig.tar.gz failed

All the best


-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.utf8)
Shell: /bin/sh linked to /bin/dash

Versions of packages git-buildpackage depends on:
ii  devscripts       2.12.2
ii  git              1:1.7.10.4-1
ii  python           2.7.3-2
ii  python-dateutil  1.5+dfsg-0.1

Versions of packages git-buildpackage recommends:
ii  cowbuilder    0.71
ii  pristine-tar  1.26

Versions of packages git-buildpackage suggests:
pn  python-notify  <none>
ii  unzip          6.0-7

-- no debconf information


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to