Path: csiph.com!eternal-september.org!feeder.eternal-september.org!aioe.org!bofh.it!news.nic.it!robomod From: Stefano Rivera Newsgroups: linux.debian.maint.python Subject: Re: Git migration schedule Date: Mon, 05 Oct 2015 22:40:03 +0200 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Mon Oct 5 20:36:22 2015 Old-Return-Path: X-Amavis-Spam-Status: No, score=-6.999 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, HEADER_FROM_DIFFERENT_DOMAINS=0.001, LDO_WHITELIST=-5] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate:hard: -6.1 Mail-Followup-To: debian-python@lists.debian.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline X-Gpg-Public-Key: http://www.rivera.za.net/stefano.gpg User-Agent: Mutt/1.5.21 (2010-09-15) X-Mailing-List: archive/latest/12783 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/20151005203606.GD3644@bach.rivera.co.za Approved: robomod@news.nic.it Lines: 27 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Mon, 5 Oct 2015 22:36:06 +0200 X-Original-Message-ID: <20151005203606.GD3644@bach.rivera.co.za> X-Original-References: <20151002102428.37362c96@limelight.wooz.org> <20151003094748.GB3567@bach.rivera.co.za> <20151003185221.GC3567@bach.rivera.co.za> <20151004210621.GB3644@bach.rivera.co.za> <56124BE5.6090903@debian.org> Xref: csiph.com linux.debian.maint.python:7472 Hi IOhannes (2015.10.05_12:07:33_+0200) > >> sorry, i forgot to ask another question: how will the packages > >> already maintained in git be handled? > > > > Up to their maintainers (assuming they're following team > > standards). If people only have one git package, for testing, each, > > then this shouldn't be an issue :) > > what does this mean in practice? > what if people have more than one git package, not only for "testing" > purposes? How about: We move away existing repositories, and put the migrated ones in the /packages/ path. If people have existing repositories, that they'd prefer to use, they can move the migrated ones out the way, and theirs back. But they have to opt in to this. This means some (work done on pre-migration git packaging) history gets temporarily "lost". But ensures that everything is the same layout. And that any deviation was intentional, not accidental. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272