bts tag 50402 +moreinfo
On Thu, Oct 30, 2008 at 07:19:45PM +0200, jaalto wrote:
> I was trying to upgrade from new tar:
>
> $ git-import-orig --verbose --upstream-version=2007.01.01
> ../fvwm-icons_2007.01.01.orig.tar.gz
> Run above command (C-c to abort)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Where does this come from?
> Upstream version is 2007.01.01
> tar ['-C', '../tmpoKDrq8', '--gzip', '-xf',
> '../fvwm-icons_2007.01.01.orig.tar.gz'] []
> Unpacked ../fvwm-icons_2007.01.01.orig.tar.gz to '../tmpoKDrq8'
> Importing '../fvwm-icons_2007.01.01.orig.tar.gz' to branch 'upstream'...
> git ['checkout', 'upstream'] []
> Switched to branch "upstream"
> git ['add'] ['-f', '.']
> Nothing to commit, nothing imported.
> rm ['-rf', '../tmpoKDrq8'] []
>
> PROBLEM
>
> The branch pointed is left in 'upstream' when I expected it to be on
> 'master' after git-import-orig call, becaus it cleaned ../tmpoKDrq8
>
> $git branch
> master
> pristine-tar
> * upstream
>
> There are files in the new tar, but I haven't analyzed why the import
> reports "nothing to commit" (it's not a problem in git-buildpackage I
> assume).
What is this bug about? That you're left on upstream after an error or
that nothing get's imported? Or both? I think the former isn't a bug
since you might want to stay on that branch in case of an error to
investigate. To debug the later I'd need the repo to reproduce.
Cheers,
-- Guido
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
