Path: csiph.com!eternal-september.org!feeder.eternal-september.org!aioe.org!bofh.it!news.nic.it!robomod From: Scott Kitterman Newsgroups: linux.debian.maint.python Subject: Re: git-dpm tag possible gotcha Date: Fri, 06 Nov 2015 06:20:02 +0100 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Fri Nov 6 05:14:09 2015 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.1 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, LDO_WHITELIST=-5] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -5 Dkim-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=201409; t=1446786831; bh=0FH13DOEu/5Nm35oTXIq45GHr5veO5ZdpD//fNYNXsI=; h=From:To:Subject:Date:In-Reply-To:References:From; b=HdxL8/ChA0iViOf5bgvPkROvGanWrNtyghcdH0LKilqUzh0MvILKGcsGdPmC8AJ96 6Ae+94LpK1SynV1s3ocuVm+9uHgI3gZhmMoVqXLLtI3x0wQjE6+KQ9YRJMKVQD8Srq K0uT1/6YGZFEevMW+3B8mzn3qu6aDXKFeNQHhx8Y= User-Agent: KMail/4.13.3 (Linux/3.13.0-63-generic; KDE/4.13.3; x86_64; ; ) MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Mailing-List: archive/latest/13147 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/2523022.k3yUcyODKl@kitterma-e6430 Approved: robomod@news.nic.it Lines: 16 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Fri, 06 Nov 2015 00:13:51 -0500 X-Original-Message-ID: <2523022.k3yUcyODKl@kitterma-e6430> X-Original-References: <20151104144454.3e42a707@anarchist> <87twp0qdr2.fsf@prune.linuxpenguins.xyz> Xref: csiph.com linux.debian.maint.python:7834 On Friday, November 06, 2015 09:32:01 AM Brian May wrote: > Barry Warsaw writes: > > I've occasionally seen this when I try to `git-dpm tag`: > > > > git-dpm: ERROR: 'upstream' differs from recorded one! > > I have regularly seen this problem and my upstream branch is up-to-date > with origin/upstream. > > Seems to go away after I import a new upstream version and git-dpm tags > the new upstream version. Which of course requires a new upstream > version. My experience has been similar. Scott K