Path: csiph.com!news.mixmin.net!weretis.net!feeder1.news.weretis.net!newsfeed.CARNet.hr!news.spin.it!bofh.it!news.nic.it!robomod
From: Raphael Hertzog <hertzog@debian.org>
Newsgroups: linux.debian.maint.python
Subject: Re: Git migration schedule
Date: Wed, 21 Oct 2015 10:00:02 +0200
Message-ID: <qlWts-51P-11@gated-at.bofh.it>
References: <qf9vr-5XN-1@gated-at.bofh.it> <ql2rg-7dt-5@gated-at.bofh.it> <qlmgi-2vV-31@gated-at.bofh.it> <qlqjT-8tO-3@gated-at.bofh.it>
X-Original-To: Brian May <bam@debian.org>
X-Mailbox-Line: From debian-python-request@lists.debian.org  Wed Oct 21 07:53:29 2015
Old-Return-Path: <raphael@ouaza.com>
X-Amavis-Spam-Status: No, score=-6.989 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, HEADER_FROM_DIFFERENT_DOMAINS=0.001, LDO_WHITELIST=-5, MURPHY_DRUGS_REL8=0.02, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Mail-Followup-To: Raphael Hertzog <hertzog@debian.org>, Brian May <bam@debian.org>, debian-python@lists.debian.org
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.5.24 (2015-08-30)
X-Virus-Status: Clean
X-Mailing-List: <debian-python@lists.debian.org> archive/latest/13043
List-ID: <debian-python.lists.debian.org>
List-URL: <https://lists.debian.org/debian-python/>
List-Archive: https://lists.debian.org/msgid-search/20151021075312.GC20145@home.ouaza.com
Approved: robomod@news.nic.it
Lines: 30
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
X-Original-Cc: debian-python@lists.debian.org
X-Original-Date: Wed, 21 Oct 2015 09:53:12 +0200
X-Original-Message-ID: <20151021075312.GC20145@home.ouaza.com>
X-Original-References: <20151002102428.37362c96@limelight.wooz.org> <5623F0B5.7030609@debian.org> <20151019131252.073fa34e@limelight.wooz.org> <877fmiedxm.fsf@prune.linuxpenguins.xyz>
Xref: csiph.com linux.debian.maint.python:7730

On Tue, 20 Oct 2015, Brian May wrote:
> Barry Warsaw <barry@debian.org> writes:
> 
> > Now, in practice, it doesn't matter if you ignore git-dpm and just use quilt
> > *as long as the final state of the repo is compatible with git-dpm*.  Meaning,
> > in general, you can make whatever local decisions you want as long as they
> > don't force other team members to go outside of team recommendations.
> 
> I don't see how you could use quilt and maintain compatability with
> git-dpm. git-dpm expects all patches to be in git, and will update
> debian/patches automatically from git. quilt writes patches directly in
> debian/patches/* and doesn't support git.
> 
> Not something that concerns me personally, quilt was starting to become
> very painful for me. I regularly ended up forgetting the "quilt add"
> operation before editing files, resulting in invalid patches.

And also for import of upstream tarballs you basically have to use git-dpm
as git-dpm keeps state data in debian/.git-dpm whereas git-buildpackage
does not have similar state data (except the generic git data like
availability of a upstream/<version> tag, and so on).

I really regret to not have invested time earlier to try out git-dpm...

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/