sequential import fails

Bug #403299 reported by Rolf Leggewie on 2009-07-23
This bug affects 1 person
Affects Status Importance Assigned to Milestone
git-buildpackage (Ubuntu)

Bug Description

Binary package hint: git-buildpackage

the following sequence of commands will fail, even in the latest karmic package:

git-import-dsc --pristine-tar kasumi_2.2-1.1.dsc
git-import-dsc --pristine-tar kasumi_2.4-0ubuntu1.dsc

cd kasumi ; git-import-dsc --pristine-tar ../kasumi_2.4-0ubuntu1.dsc

as the last command on the other hand will work. The error given on the console when not changing directory first is

No git repository found, creating one.
Traceback (most recent call last):
  File "/usr/bin/git-import-dsc", line 196, in <module>
  File "/usr/bin/git-import-dsc", line 141, in main
    repo = create_repo(src.pkg)
  File "/var/lib/python-support/python2.5/gbp/", line 188, in create_repo
    raise GitRepositoryError, "Cannot create Git repository at %s: %s " % (path, err[1])
gbp.git_utils.GitRepositoryError: Cannot create Git repository at kasumi: File exists

Rolf Leggewie (r0lf) on 2009-07-23
description: updated
description: updated
Guido Günther (agx) wrote :

Works in Debian's 0.4.64.

Guido Günther (agx) wrote :

You need to change into the repo after the first import though (or use git-import-dsc*s*)

Rolf Leggewie (r0lf) wrote :

Guido, thank you for your comment. You are right that switching directory after the first import or using git-import-dscs works. This ticket is about "git-import-dsc --pristine-tar kasumi_2.2-1.1.dsc && git-import-dsc --pristine-tar kasumi_2.4-0ubuntu1.dsc" without switching directory in between failing. I hope git-import-dsc would do better here, but I agree it's not too serious since it can be made to comply the way you described.

Changed in git-buildpackage (Ubuntu):
importance: Undecided → Low
Guido Günther (agx) wrote :

git-import-dscs (note the extra s) will handle this for you.

Rolf Leggewie (r0lf) wrote :

you already said that in comment 2 (which I already acknowledged in comment 3) ;-)

Rolf Leggewie (r0lf) wrote :

still the same in 0.5.4

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers