Path: csiph.com!goblin3!goblin2!goblin.stu.neva.ru!aioe.org!bofh.it!news.nic.it!robomod From: Brian May Newsgroups: linux.debian.maint.python Subject: Re: Git migration schedule Date: Mon, 19 Oct 2015 23: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 19 21:31:11 2015 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.699 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, LDO_WHITELIST=-5, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no X-Policyd-Weight: DYN_NJABL=SKIP(0) NOT_IN_SBL_XBL_SPAMHAUS=-1.5 BL_NJABL=SKIP(-1.5) CL_IP_EQ_HELO_IP=-2 (check from: .microcomaustralia. - helo: .mail-pa0-x234.google. - helo-domain: .google.) FROM/MX_MATCHES_NOT_HELO(DOMAIN)=0; rate: -5 Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microcomaustralia.com.au; s=google; h=sender:from:to:subject:in-reply-to:organization:references :user-agent:date:message-id:mime-version:content-type; bh=OXzrXIaGDIv3RKSBfJw0VkwVNSlr0vI6VApFfP6ANds=; b=ca6ecEzWhFqNuopximtNlrLV1oaIpDulJUWRY/FccNgAT09CmbT69pqypGFQOXUXTK D7duetl/9FHPqt76h8km6V0VKDyp5AFkDXVpzGy6yEn4N19QfjQGj4KpEUBBsmAQVY1X 5C4JHy9xVqgZSLueeXOQb48EJRBloMt7bc5os= X-Google-Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:from:to:subject:in-reply-to:organization :references:user-agent:date:message-id:mime-version:content-type; bh=OXzrXIaGDIv3RKSBfJw0VkwVNSlr0vI6VApFfP6ANds=; b=QqpYgn6gPgrIQFqH59lPhHOYd6All8IHhVHXdfeCgv14W95wNQBmieI50WJy+uwqna z02GOG/Sm4uwOzLCovh0Cvbi8mtm/CtHGLXA0mBoYeq9vtkjX2HeTnTMl7bZFeNygBpj ZYnxLBPfRCLDiUldSuMSuLFhGSvnVwBJ3tyhQ9cJT3X2hoEriKawZd7Rnk3q39DwS0dW hAjr2iqWgjXSnkEDeCUbpO+US2jA4IeZ2Gg4UOifqBB99VfA1osjBPUioQ29yRTvK5T3 2vrp3f9AzJoOVba4BYvxoV4x4lZJAmWYVKHwZBtGycH5T6nocZplYVtY3qCcDAOrx0z5 RjOw== X-Gm-Message-State: ALoCoQm5QSquZDgLaiIjf3lOqCLu4DZaWXS6p6+0NELXqpdef1va5+Z9k4cLbIisW8wP6+/ZF6CM X-Received: by 10.66.163.197 with SMTP id yk5mr36327375pab.37.1445290252541; Mon, 19 Oct 2015 14:30:52 -0700 (PDT) Sender: robomod@news.nic.it Organization: Debian User-Agent: Notmuch/0.18.2 (http://notmuchmail.org) Emacs/24.4.1 (x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain X-Mailing-List: archive/latest/13010 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/87bnbueebc.fsf@prune.linuxpenguins.xyz Approved: robomod@news.nic.it Lines: 25 X-Original-Date: Tue, 20 Oct 2015 08:30:47 +1100 X-Original-Message-ID: <87bnbueebc.fsf@prune.linuxpenguins.xyz> X-Original-References: <20151002102428.37362c96@limelight.wooz.org> <5623F0B5.7030609@debian.org> <20151019131252.073fa34e@limelight.wooz.org> X-Original-Sender: Brian May Xref: csiph.com linux.debian.maint.python:7699 Barry Warsaw writes: > My personal opinion is that we should live with the current git workflow > recommendations for a while and see how it goes. If there are things we can > improve on (e.g. DEP-14 compatibility) then sure, let's discuss the pros and > cons, but let's not change things right now. I'd like to see how it works in > practice for a while. I suspect some packages may end up needing DEP-14 names for security fixes and backports. The problem here is with the naming of the upstream branches is different. Although security updates and backports are unlikely to use new upstream versions, git-dpm appears to use upstream- as the upstream branch name if the debian branch is not master. Either should be upstream or upstream/. Also see: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801666 I don't (yet) see a significant problem with using master instead of debian/master, unless you want to maintain seperate branches for Ubuntu and Debian packages (a level of complexity I prefer not to think too much about right now...) -- Brian May