Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ascOK-0000ac-T8 for pgsql-pkg-debian@arkaria.postgresql.org; Tue, 19 Apr 2016 20:37:00 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1ascOK-0000Bc-Dy for pgsql-pkg-debian@arkaria.postgresql.org; Tue, 19 Apr 2016 20:37:00 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1ascLo-0008Se-0u for pgsql-pkg-debian@postgresql.org; Tue, 19 Apr 2016 20:34:24 +0000 Received: from lb2-smtp-cloud3.xs4all.net ([194.109.24.26]) by makus.postgresql.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1ascLh-0001Bt-59 for pgsql-pkg-debian@postgresql.org; Tue, 19 Apr 2016 20:34:22 +0000 Received: from [10.0.0.150] ([82.94.42.6]) by smtp-cloud3.xs4all.net with ESMTP id kLaD1s00C07ytKE01LaElB; Tue, 19 Apr 2016 22:34:14 +0200 Subject: Re: pgrouting updated to version 2.2.0-1.pgdg+1 To: Christoph Berg , Vicky Vergara , PostgreSQL in Debian , Debian GIS Project References: <20160419180107.GC12650@msg.df7cb.de> <5716806D.30603@xs4all.nl> <57169181.5080009@xs4all.nl> <571694F9.6040400@xs4all.nl> <20160419203145.GI12650@msg.df7cb.de> From: Sebastiaan Couwenberg Message-ID: <57169645.1090002@xs4all.nl> Date: Tue, 19 Apr 2016 22:34:13 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.7.2 MIME-Version: 1.0 In-Reply-To: <20160419203145.GI12650@msg.df7cb.de> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.6 (--) X-Mailing-List: pgsql-pkg-debian List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Precedence: bulk Sender: pgsql-pkg-debian-owner@postgresql.org On 04/19/2016 10:31 PM, Christoph Berg wrote: > Re: Sebastiaan Couwenberg 2016-04-19 <571694F9.6040400@xs4all.nl> >>> So I need to name the tag 2.2.1 to be 2.2.2 >>> and recover the hash from 2.2.1 and tag it again, is that correct? >> >> Yes, ideally the old 2.2.1 tag is restored to reference the old commit, >> and the new 2.2.1 tag needs to be replaced with 2.2.2, but you'll likely >> need to change a couple of source files to use 2.2.2 first too. > > Hmm, doesn't that create the same problem the other way round for the > other half of the world that has downloaded the newer tarball? > > From what I understood, the difference was just changelog/news, so > wouldn't just waiting for the next release to happen eventually be > good enough? Yes, it does. This just underscore the issue of changing tags after they've been published outside your local repository. So please disregard my advise to change the 2.2.1 tag, just make sure 2.2.2 gets it right. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 -- Sent via pgsql-pkg-debian mailing list (pgsql-pkg-debian@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-pkg-debian