Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #7619
| From | Brian May <brian@microcomaustralia.com.au> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | warnings importing new upstream source |
| Date | 2015-10-12 07:30 +0200 |
| Message-ID | <qiDQm-6aa-5@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
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
Back to linux.debian.maint.python | Previous | Next — Next in thread | Find similar
warnings importing new upstream source Brian May <brian@microcomaustralia.com.au> - 2015-10-12 07:30 +0200 Re: warnings importing new upstream source Barry Warsaw <barry@debian.org> - 2015-10-12 20:40 +0200 Re: warnings importing new upstream source Scott Kitterman <debian@kitterman.com> - 2015-10-12 20:50 +0200
csiph-web