Path: csiph.com!feeder.erje.net!2.eu.feeder.erje.net!newsfeed.CARNet.hr!news.spin.it!bofh.it!news.nic.it!robomod From: Simon McVittie Newsgroups: linux.debian.maint.python Subject: Re: git-dpm -> gbp conversion (mass-change) Date: Fri, 03 Aug 2018 09:10:01 +0200 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Fri Aug 3 07:04:43 2018 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -5 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.10.1 (2018-07-13) X-Mailing-List: archive/latest/16170 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/20180803070413.GA11122@espresso.pseudorandom.co.uk Approved: robomod@news.nic.it Lines: 31 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Fri, 3 Aug 2018 08:04:13 +0100 X-Original-Message-ID: <20180803070413.GA11122@espresso.pseudorandom.co.uk> X-Original-References: <20180802151614.jlu5w3l3lnhwi3he@werner.olasd.eu> <20180803035100.GA9931@fama> <0BA88625-8549-4029-AF86-896BA9947BCD@kitterman.com> <20180803062128.GB1955@fama> Xref: csiph.com linux.debian.maint.python:10750 On Fri, 03 Aug 2018 at 08:21:28 +0200, W. Martin Borgert wrote: > In fact, I thought that "upstream/master" were DEP-14-ish, but > only "upstream/latest" (for the newest release) is. Yes. The simple case for DEP-14 is that you are only following one upstream branch, which is upstream/latest; the more complex case is that you are also following an upstream stable-branch or something, for which naming like upstream/1.2.x is suggested for the older (stable) branch. dbus and glib2.0 are examples of DEP-14 packages that track more than one upstream branch. There is no upstream/master, upstream/unstable, upstream/stretch or similar in DEP-14, because: * if uploads to a particular Debian suite are tracking upstream versions older than the latest, they presumably meet some sort of criteria for which versions are acceptable, most commonly "is from the same stable-branch as the previous release"; the branch is named after those criteria rather than the target suite, because multiple suites might be sharing an upstream release series * if there is no upstream version that is acceptable for e.g. stable, then new upstream versions won't get imported for that suite, so there's no need to maintain a branch that they could be imported into (if using pristine-tar, it uses commits, not branches, to check out upstream source) smcv