Path: csiph.com!weretis.net!feeder4.news.weretis.net!news.unit0.net!news.panservice.it!bofh.it!news.nic.it!robomod From: Yuri D'Elia Newsgroups: linux.debian.maint.python Subject: Re: git-dpm (was Re: Bug#729956: Forwarded upstream) Date: Fri, 08 Sep 2017 00:50:01 +0200 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Thu Sep 7 22:40:57 2017 Old-Return-Path: X-Amavis-Spam-Status: No, score=-6.206 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, HEADER_FROM_DIFFERENT_DOMAINS=0.001, LDO_WHITELIST=-5, RDNS_NONE=0.793] autolearn=no autolearn_force=no X-Policyd-Weight: using cached result; rate: -6.1 X-Injected-Via-Gmane: http://gmane.org/ Lines: 18 MIME-Version: 1.0 Content-Type: text/plain User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux) Cancel-Lock: sha1:CDSdd+YIfNutY0OBZl7ckZuXXIQ= X-Mailing-List: archive/latest/15186 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/87r2virv4a.fsf@wavexx.thregr.org Approved: robomod@news.nic.it Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Fri, 08 Sep 2017 00:39:49 +0200 X-Original-Message-ID: <87r2virv4a.fsf@wavexx.thregr.org> X-Original-References: <1384861181.23137.1.camel@debiousci.pietrobattiston.it> <20170906150846.x3g3iz7qsiiclz57@an3as.eu> <87bmmn26i2.fsf@wavexx.thregr.org> <20170906202443.x46qk7jnffznsyxa@an3as.eu> <87fubzef9u.fsf@wavexx.thregr.org> <20170906205007.2pugvkvlo77n7stc@an3as.eu> <87efrjedj6.fsf@wavexx.thregr.org> X-Original-X-Complaints-To: usenet@blaine.gmane.org Xref: csiph.com linux.debian.maint.python:9804 On Thu, Sep 07 2017, Brian May wrote: > In general, however, when something does go badly wrong I think it will be a > lot easier to diagnose, understand, and fix with GPB PQ then with git-dpm. > git-dpm can get very messy very quickly, particularly if you forget to pull > before making changes (personally I make this mistake too frequently) or update > to a new upstream version without using the correct git-dpm workflow - I have > seen both of these situations happen. I concur. gbp is not without issues, but as you said, gbp is easier to reason about and fix. I don't use gbp daily. In fact, I maintain or edit existing packages not as frequently as I would like, often having to re-read the documentation along the way. The fact that gbp is better documented is a big plus, even if everything else would be equal. Simplicity goes a long way for cooperative maintenance. I'm relieved gbp is now the recommended choice.