Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod From: Brian May Newsgroups: linux.debian.maint.python Subject: Re: git-dpm -> gbp conversion (mass-change) Date: Wed, 08 Aug 2018 23:50:01 +0200 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Wed Aug 8 21:40:42 2018 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -5 Organization: Debian MIME-Version: 1.0 Content-Type: text/plain X-Mailing-List: archive/latest/16196 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/87lg9go7ui.fsf@silverfish.pri Approved: robomod@news.nic.it Lines: 14 Sender: robomod@news.nic.it X-Original-Date: Thu, 09 Aug 2018 07:40:21 +1000 X-Original-Message-ID: <87lg9go7ui.fsf@silverfish.pri> X-Original-References: <20180802151614.jlu5w3l3lnhwi3he@werner.olasd.eu> <20180804070542.ehshncjtlx4lsswf@macbookair> <87h8k53x69.fsf@vostro.rath.org> Xref: csiph.com linux.debian.maint.python:10776 Nikolaus Rath writes: > The problems with git-dpm are the implementation and lack of > maintenance, not the way the Debian changes are managed. git-dpm requires that you always use its tools. If another maintainer got confused and used another toolset to upgrade the upstream version, things could get messy. I did see it happen from time to time that the previous maintainer would leave the repository in a weird state that could only be fixed (unfortunately) with a git rebase. -- Brian May