Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e185k-000574-9K for pgsql-pkg-debian@arkaria.postgresql.org; Sun, 08 Oct 2017 09:41:48 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1e185j-0003UV-57 for pgsql-pkg-debian@arkaria.postgresql.org; Sun, 08 Oct 2017 09:41:47 +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 1e185e-0003Mf-9f for pgsql-pkg-debian@postgresql.org; Sun, 08 Oct 2017 09:41:42 +0000 Received: from feynman.df7cb.de ([195.49.152.168]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1e185V-00045e-AO for pgsql-pkg-debian@postgresql.org; Sun, 08 Oct 2017 09:41:41 +0000 Received: from msg.df7cb.de (unknown [IPv6:2a02:908:1474:d80:76e5:bff:fef3:7e00]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by feynman.df7cb.de (Postfix) with ESMTPSA id 3y8z0V6Dwnz3F0W; Sun, 8 Oct 2017 11:41:30 +0200 (CEST) Date: Sun, 8 Oct 2017 11:41:30 +0200 From: Christoph Berg To: Peter Geoghegan Cc: pgsql-pkg-debian@postgresql.org Subject: Re: amcheck packages Message-ID: <20171008094130.ls2nch4ahwkodzuz@msg.df7cb.de> Mail-Followup-To: Christoph Berg , Peter Geoghegan , pgsql-pkg-debian@postgresql.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170609 (1.8.3) 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 Re: Peter Geoghegan 2017-10-07 > Note that "debian/watch" is grabbing tags that match "v(.*).tar.gz". > So, even though I use "debian*" tags, too, I'm not sure that bumping > the tag will work for us. It might be easier to make the changes you > ask for formally "v1.1" and "debian/1.1-1" (i.e. avoid just bumping up > by creating "debian/1.0-2", which is what you ask for here, I gather). Sorry, my last mail was a bit confusing. What I meant to say was that I frivolously did these local changes, and then uploaded the package to Debian as 1.0-1. Assuming it passes the initial check of the package by the ftp-master people, that's what is in Debian then, so changing the tag would just mean syncing with that part of reality (while apt.postgresql.org received what you tagged, the changes being no-ops there). Sorry for the mess, I didn't want to postpone the uploads any more, and just went forward there. (The v.* tags are used by debian/watch (via "uscan") to retrieve tarballs. The debian/.* tags are just for documentation.) I guess the way ahead is now to just leave the tags in place, apply the change(s) on top of master, and wait for the next release. Re: Peter Geoghegan 2017-10-07 > On Sat, Oct 7, 2017 at 1:33 PM, Peter Geoghegan wrote: > > Note that "debian/watch" is grabbing tags that match "v(.*).tar.gz". > > So, even though I use "debian*" tags, too, I'm not sure that bumping > > the tag will work for us. It might be easier to make the changes you > > ask for formally "v1.1" and "debian/1.1-1" (i.e. avoid just bumping up > > by creating "debian/1.0-2", which is what you ask for here, I gather). > > Please let me know what you think. > > Actually, I could just create a "v1.0-2" tag, to go along with a > "debian/1.0-2" tag. That would mean that I wouldn't formally be > bumping package number, but rather debian_revision (as I understand > it). A cleaner fix, perhaps. This kind of changes in debian/-only is what -2 releases are for, so 1.1 is overkill, yes. No v1.0-2 tag is necessary because the upstream version number is still (v)1.0. Christoph -- 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