severity 504029 wishlist clone 504029 -1 -2 retitle -1 note the current branch after import failures retitle -2 importing identical tarballs with different versions should be possible thanks
On Fri, Oct 31, 2008 at 10:54:42AM +0300, Jari Aalto wrote: [..snip..] > That the program leaves on "upstream". An mproved version could: > > a) display a message: > > "Note, the branch is now at 'upstream' for you to investigate the > issue" > > b) or go back to 'master' as usual (I'd prefer this) to reset the situation. At least printing a message makes sense. I'd rather not switch branches since on other error conditions (with the same return code from git unfortunately) we might not want to switch branches since there are uncomitted changes left. I'll add that. > > you might want to stay on that branch in case of an error to > > investigate. > > If possible, the choice between (a) and (b) could be configurable in > ~/.gbp.conf > > > To debug the later I'd need the repo to reproduce. Cheers, -- Guido > > > >> 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). > > Comparing the new upstream tar file to the old showed that upstream had > bumped the version, but the contents of the tar files were identical. > Thus: > > Nothing to commit, nothing imported > > FEATURE REQUEST > > Could there be a new option --force-empty-commit that would: > > * Commit with message-only: "Imported .... (no changes)" > * mark the commit as usual "upstream/version" I don't think we can create a new commit object without any changes. Is this possible in git? However adding another tag would indeed be useful. Patches for this would be welcome. Cheers, -- Guido -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
