Package: git-buildpackage Version: 0.2.12 Severity: important Hello,
I'm trying to use git-import-orig on a new repository. This repository currently has the debian packaging already present in the master branch. There are no other sources. I create an upstream branch and run git-import-orig. After it gives me the list of files and asks for confirmation, I allow it to run the import. It does so, and it deletes the debian directory in the change to the upstream branch. Then when it switches to the master branch and pull the change, the debian directory gets deleted and the import fails because this packaging information is missing. Similarly, if I create the upstream branch, then delete the debian directory there, so that the packaging info is only in the master branch, and run git-import-orig, the same thing happens. This is apparently because git-import-orig runs 'git pull . upstream', which pulls all the changes from upstream in to master, including the change that deleted the debian dir. In order to make this work, I have to manually revert the master dir and cherry-pick the import change, thus avoiding the change that deletes the debian dir. I'm not sure if this is a suitable method for git-import-orig to do, but it does get me what I need in order to build the package. - David Nusinow -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages git-buildpackage depends on: ii devscripts 2.9.27 Scripts to make the life of a Debi ii git-load-dirs 1.0.35 Import upstream archives into git ii python 2.4.4-2 An interactive high-level object-o ii python-support 0.5.6 automated rebuilding support for p git-buildpackage recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
