Re: warnings importing new upstream source

[Scott Kitterman <debian@kitterman.com>]

On October 12, 2015 1:27:41 AM EDT, Brian May <brian@microcomaustralia.com.au> wrote:
>As far as I know this actually did work despite the complaining about
>no
>parent commit... What does that mean?
>
>git-dpm import-new-upstream --ptc --rebase-patched
>../django-model-utils_2.3.1.orig.tar.gz
>There were no patches recorded, so merging the new state directly (no
>git-dpm rebase-patched needed).
>git-dpm: WARNING: No parent commit specified.
>This means the upstream branch was created from the .orig.tar with only
>theold upstream branch as parent (but not any possible upstream git
>history).
>Use 'git config dpm.importWithoutParent true' to no longer show this
>warning.
>or 'git config dpm.importWithoutParent false' to make this an hard
>error.
>calling pristine-tar commit '../django-model-utils_2.3.1.orig.tar.gz'
>'1b7b962b83568d87570e8865fb02b1d3331deda2'...
>pristine-tar: committed django-model-utils_2.3.1.orig.tar.gz.delta to
>branch pristine-tar

All this means is that the upstream release came from a tarball and not a git repository.

It's harmless.

Scott K