Groups > linux.debian.maint.python > #8733

Re: using git-dpm or plain git-buildpackage in PAPT and DPMT (was: PAPT Git)

Path	csiph.com!goblin3!goblin.stu.neva.ru!inn10.news.alteholz.net!news.in-chemnitz.de!news2.arglkargh.de!news.mixmin.net!news.unit0.net!news.panservice.it!bofh.it!news.nic.it!robomod
From	Brian May <bam@debian.org>
Newsgroups	linux.debian.maint.python
Subject	Re: using git-dpm or plain git-buildpackage in PAPT and DPMT (was: PAPT Git)
Date	Wed, 10 Aug 2016 12:50:01 +0200
Message-ID	<s4zfb-3XQ-5@gated-at.bofh.it> (permalink)
References	<s4kSS-3iq-9@gated-at.bofh.it> <s4ne2-4FM-3@gated-at.bofh.it> <s4oab-5fc-11@gated-at.bofh.it> <s4w7D-24x-1@gated-at.bofh.it> <s4wU1-2Bz-23@gated-at.bofh.it>
X-Mailbox-Line	From debian-python-request@lists.debian.org Wed Aug 10 10:49:51 2016
Old-Return-Path	<brian@microcomaustralia.com.au>
X-Amavis-Spam-Status	No, score=-7.579 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FOURLA=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, LDO_WHITELIST=-5, MURPHY_DRUGS_REL8=0.02, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
X-Policyd-Weight	NOT_IN_SBL_XBL_SPAMHAUS=-1.5 NOT_IN_BL_NJABL=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .microcomaustralia. - helo: .mail-pf0-x244.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; bh=OP022j50Pr1XLvC5Jm6X9QEd138Cbdk4WLrx3F/jAnU=; b=XGBXhavJqrgCwVkB5o8OyjLyPKVzEXyzBdRrufd/g8uoT56RwCKCSk+YA0luDmF/g1 kGGUiDWH83ZeS0g1uX4jBcvSnTHpLbat5j9k7NIvb0b1Wx3i54mgVbSQ2m5qJq4zu++K rWUPTubu5mXMENa0t7a/fZDYG9FfRmMC/tXb4=
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; bh=OP022j50Pr1XLvC5Jm6X9QEd138Cbdk4WLrx3F/jAnU=; b=MtSoF7VTkHd50wRMk8vDdghf+mqI0EJkF3WwyCp+DiisSCIZQV8TSnaP2hpRP6S9tS 9ztDvAiA43AZIr1X/fqE5P7JMIhCpNngRz5oGlCI2rBtS5dNlFvJWvTjG/QKRfetSWeH Xw9IT/v3NxoROxyl7flFiNz5ZvtKwfGRnyUtpVW2nB3Flz+RGgpVOR+6KZhbMAFc8oie 857jEwhZhqcbCIL/JuW6VkJTMYTpr6lWZhhUu3rLHWdknK2UGAhwpgCXanLdU5053GYk JYK23zJ7Tk4sALvIgvsI4WivbxMj7GLJz5iEAVXHIJEY/nR4kJ9S0v4asaWAlPcldKDb d/oA==
X-Gm-Message-State	AEkoouuTUeuv6ttv7R5kL7n/17JB22vu42AO/BGikeMfuSXzs/NNewjvhH0YuQym/9KCsQ==
X-Received	by 10.98.103.214 with SMTP id t83mr5912534pfj.158.1470826171160; Wed, 10 Aug 2016 03:49:31 -0700 (PDT)
Sender	robomod@news.nic.it
Organization	Debian
User-Agent	Notmuch/0.22 (http://notmuchmail.org) Emacs/24.5.1 (x86_64-pc-linux-gnu)
MIME-Version	1.0
Content-Type	text/plain
X-Mailing-List	<debian-python@lists.debian.org> archive/latest/14075
List-ID	<debian-python.lists.debian.org>
List-URL	<https://lists.debian.org/debian-python/>
List-Archive	https://lists.debian.org/msgid-search/87d1lg99vt.fsf@prune.linuxpenguins.xyz
Approved	robomod@news.nic.it
Lines	26
X-Original-Date	Wed, 10 Aug 2016 20:49:26 +1000
X-Original-Message-ID	<87d1lg99vt.fsf@prune.linuxpenguins.xyz>
X-Original-References	<20160809192733.pfsnzejxlmd3knbe@p1otr.com> <356e3407-7970-5c4f-f963-60664898548a@debian.org> <20160809225020.GA30494@fama> <CAB4XWXyt2kqg0ThuFKyi48eMp86jYgLZUyL-LBU8dOq3Y+9cnQ@mail.gmail.com> <ab6efb18-10f2-7372-f7e5-b3a20add40e3@debian.org>
X-Original-Sender	Brian May <brian@microcomaustralia.com.au>
Xref	csiph.com linux.debian.maint.python:8733

Show key headers only | View raw

Thomas Goirand <zigo@debian.org> writes:

> git-dpm also fails to tag upstream/foo automatically when importing a
> new version. I've been told to use "git-dpm tag", but that's not
> obvious. My own experience managing debian/patches quilt patches
> manually or through gbp pq is actually much much nicer.

The problem with git-dpm tag is that this tags the Debian release too -
sometimes you want to tag the upstream version and aren't ready to
release a Debian version just yet.

> Plus it appears git-dpm is unmaintained and even sometimes buggy

That is the big problem. Nobody maintaining it or responding to bug
reports.

> As I only heard complains about git-dpm, maybe someone would like to
> express his joy using it, and explain why they think it's a nice tool.
> But is there such person? It seems git-dpm only brings frustration.

Most of the time it works pretty well... It looked good compared with
the alternatives available at the time we made the decision.

However this is irrelevant IMHO if it isn't being mantained.
-- 
Brian May <bam@debian.org>

Thread

pypi2deb 1.20160809 and --profile dpmt Piotr Ożarowski <piotr@debian.org> - 2016-08-09 21:30 +0200
  Re: pypi2deb 1.20160809 and --profile dpmt Daniel Stender <stender@debian.org> - 2016-08-10 00:00 +0200
    Re: pypi2deb 1.20160809 and --profile dpmt Barry Warsaw <barry@debian.org> - 2016-08-10 00:10 +0200
    PAPT Git (was: pypi2deb 1.20160809 and --profile dpmt) "W. Martin Borgert" <debacle@debian.org> - 2016-08-10 01:00 +0200
      Re: PAPT Git (was: pypi2deb 1.20160809 and --profile dpmt) Sandro Tosi <morph@debian.org> - 2016-08-10 09:30 +0200
        Re: PAPT Git Piotr Ożarowski <piotr@debian.org> - 2016-08-10 09:40 +0200
        Re: using git-dpm or plain git-buildpackage in PAPT and DPMT (was:  PAPT Git) Thomas Goirand <zigo@debian.org> - 2016-08-10 10:20 +0200
          Re: using git-dpm or plain git-buildpackage in PAPT and DPMT (was:  PAPT Git) "W. Martin Borgert" <debacle@debian.org> - 2016-08-10 11:00 +0200
          Re: using git-dpm or plain git-buildpackage in PAPT and DPMT (was: PAPT Git) Brian May <bam@debian.org> - 2016-08-10 12:50 +0200
            Re: using git-dpm or plain git-buildpackage in PAPT and DPMT (was:  PAPT Git) Barry Warsaw <barry@debian.org> - 2016-08-10 16:20 +0200
          Re: using git-dpm or plain git-buildpackage in PAPT and DPMT Nikolaus Rath <Nikolaus@rath.org> - 2016-08-10 21:00 +0200
            Re: using git-dpm or plain git-buildpackage in PAPT and DPMT Barry Warsaw <barry@debian.org> - 2016-08-10 22:50 +0200
              Re: using git-dpm or plain git-buildpackage in PAPT and DPMT Simon McVittie <smcv@debian.org> - 2016-08-11 01:20 +0200
                Re: using git-dpm or plain git-buildpackage in PAPT and DPMT Barry Warsaw <barry@debian.org> - 2016-08-11 15:30 +0200
                Re: using git-dpm or plain git-buildpackage in PAPT and DPMT Simon McVittie <smcv@debian.org> - 2016-08-11 18:10 +0200
              Re: using git-dpm or plain git-buildpackage in PAPT and DPMT Thomas Goirand <zigo@debian.org> - 2016-08-15 23:50 +0200
                Re: using git-dpm or plain git-buildpackage in PAPT and DPMT Barry Warsaw <barry@debian.org> - 2016-08-16 00:00 +0200
            Re: using git-dpm or plain git-buildpackage in PAPT and DPMT Raphael Hertzog <hertzog@debian.org> - 2016-08-10 23:00 +0200
              Re: using git-dpm or plain git-buildpackage in PAPT and DPMT Brian May <bam@debian.org> - 2016-08-12 12:40 +0200
            Re: using git-dpm or plain git-buildpackage in PAPT and DPMT Sergio Durigan Junior <sergiodj@sergiodj.net> - 2016-08-13 00:00 +0200
              Re: using git-dpm or plain git-buildpackage in PAPT and DPMT Barry Warsaw <barry@debian.org> - 2016-08-13 00:40 +0200
                Re: using git-dpm or plain git-buildpackage in PAPT and DPMT Sergio Durigan Junior <sergiodj@sergiodj.net> - 2016-08-16 22:40 +0200
                Re: using git-dpm or plain git-buildpackage in PAPT and DPMT IOhannes m zmölnig (Debian/GNU)  <umlaeute@debian.org> - 2016-08-31 23:50 +0200
                Re: using git-dpm or plain git-buildpackage in PAPT and DPMT Barry Warsaw <barry@debian.org> - 2016-09-02 21:20 +0200
  Re: pypi2deb 1.20160809 and --profile dpmt IOhannes m zmölnig (Debian/GNU)  <umlaeute@debian.org> - 2016-08-31 23:50 +0200

csiph-web