Path: csiph.com!weretis.net!feeder6.news.weretis.net!news.glorb.com!diesel.cu.mi.it!bofh.it!news.nic.it!robomod From: Barry Warsaw Newsgroups: linux.debian.maint.python Subject: Re: Updating python-django-tagging Date: Mon, 07 Mar 2016 00:00:01 +0100 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Sun Mar 6 22:56:11 2016 Old-Return-Path: X-Amavis-Spam-Status: No, score=-11.98 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, MURPHY_DRUGS_REL8=0.02, PGPSIGNATURE=-5] 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: .debian. - helo: .mail.wooz. - helo-domain: .wooz.) FROM/MX_MATCHES_NOT_HELO(DOMAIN)=0; rate: -5 Organization: The Organization of Unorganized Woozalists X-Mailer: Claws Mail 3.13.1 (GTK+ 2.24.29; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/4_KqRI0_NgRI6QzE1sc6NQx"; protocol="application/pgp-signature" X-Mailing-List: archive/latest/13606 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/20160306175554.64a13b12@subdivisions.wooz.org Approved: robomod@news.nic.it Lines: 55 Sender: robomod@news.nic.it X-Original-Cc: debian-python@lists.debian.org, genannt@debian.org X-Original-Date: Sun, 6 Mar 2016 17:55:54 -0500 X-Original-Message-ID: <20160306175554.64a13b12@subdivisions.wooz.org> X-Original-References: <56DC2CB2.4060504@cbaines.net> Xref: csiph.com linux.debian.maint.python:8279 --Sig_/4_KqRI0_NgRI6QzE1sc6NQx Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Mar 06, 2016, at 01:12 PM, Christopher Baines wrote: >However, git-dpm keeps complaining in different ways when I try to do >this (and I have tried a few different ways). I think the source of the >issues I am having could be that the debian/.git-dpm file is out of sync >with the rest of the repository (it seems to still refer to the 0.3.1 >version, whereas the current version is 0.4). > >What is the best approach here if I am trying to update the package? I >can try and fix the debian/.git-dpm file (manually or using some tool?), >or I could just avoid using git-dpm (but I do need to do some patch >changes)? I don't really have any good suggestions. I've had some weird problems with git-dpm occasionally and no real solutions. For example, it kept wanting to turn a certain git commit in the patched branch into a double quilt patch, = and nothing I did seemed to work (I ended up giving up). In some of my non-team packages I've been trying to use gbp-pq more. It se= ems not terrible, and at least it's maintained. Is it time to consider switchi= ng? Perhaps just on a trial basis? When git-dpm works, it does work well. Cheers, -Barry --Sig_/4_KqRI0_NgRI6QzE1sc6NQx Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJW3LV6AAoJEBJutWOnSwa/fW4QAJ63IwiMiW1NOIDBM7u5M10P 0QrzUWFbdb7EgVQcwT4HBo+8L00VyLMXFQlUjlpFFAWIlNjIjnHyCHLyzYsLZu07 7z3qrrcnuzM4o/Wlt+xbYYuJE7Dw3QXc/Qg6NADo32TSgEnTqP42dzJkKXyJ0hcc ML8XsSYwW+8aQ5VRFGbCmOY8eBQEp9ewgFp+L3a9MimZIttR7daBnrkrhXhllm3B yvDy4f/QyT/s6Dg5ZNHQnRmsaD7Byks53hVqYRCWrCQH/hR3YR4Gu76DvanvhVJK wRSUkKO2xa5U71mF5R2IVNTIxkgTblLtGepr29v+5F1wKdFfVntcdIMdOzftAQb2 KjZm8q83CBVv9alWBLdecKRqnZhXY8D3gpEcvl3Vhwn9+dnkZiXi3QgEWphXpsmJ AkEtiis9TzPmGj83vXdK7ChU5ERZ1jEQbJvfa+igY7vGNNFlbY/RFgn4l4WtAcUp vKwuv09SLPPK4Sg33/PhJnaTFuEVR9ni8TGFNl+o1truNteV5qKdQrEv/OZSRxwP V5Vt3vAhsD/Z15upgh6fO+xSBSVeXGUvSSXx32XAjbzRH17wQ8lNtBnHg8f9Z0iq P0A2oblpb00Jtyu7jPo/DQkXzXArcWS8vQwkvADc6gSdSPZxNq+L48aaJ+3eclvN GFKbJ1rNk58CubJbdQlG =9YIE -----END PGP SIGNATURE----- --Sig_/4_KqRI0_NgRI6QzE1sc6NQx--