Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod From: Christopher Baines Newsgroups: linux.debian.maint.python Subject: Updating python-django-tagging Date: Sun, 06 Mar 2016 14:20:01 +0100 Message-ID: X-Original-To: debian-python@lists.debian.org, genannt@debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Sun Mar 6 13:13:17 2016 Old-Return-Path: X-Amavis-Spam-Status: No, score=-11.981 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, MURPHY_DRUGS_REL8=0.02, PGPSIGNATURE=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no X-Policyd-Weight: DYN_NJABL=ERR(0) NOT_IN_SBL_XBL_SPAMHAUS=-1.5 BL_NJABL=ERR(-1.5) CL_IP_EQ_FROM_MX=-3.1; rate: -6.1 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.6.0 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="fAHbpOag9XbBjmBksEL4WHotO80RKBkun" X-Mailing-List: archive/latest/13605 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/56DC2CB2.4060504@cbaines.net Approved: robomod@news.nic.it Lines: 62 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Sun, 6 Mar 2016 13:12:18 +0000 X-Original-Message-ID: <56DC2CB2.4060504@cbaines.net> Xref: csiph.com linux.debian.maint.python:8278 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --fAHbpOag9XbBjmBksEL4WHotO80RKBkun Content-Type: multipart/mixed; boundary="9bn5XLin176vgpdeLPHeXvVPVqFgU61TC" From: Christopher Baines To: debian-python@lists.debian.org, genannt@debian.org Message-ID: <56DC2CB2.4060504@cbaines.net> Subject: Updating python-django-tagging --9bn5XLin176vgpdeLPHeXvVPVqFgU61TC Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hello, I have been looking at updating the python-django-tagging package, as it currently fails to build from source, and there is a new upstream release available (that I believe will fix this). 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)? Thanks, Chris --9bn5XLin176vgpdeLPHeXvVPVqFgU61TC-- --fAHbpOag9XbBjmBksEL4WHotO80RKBkun Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJW3Cy1XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzRTg5RUVFNzQ1OEU3MjBEOTc1NEUwQjI1 RTI4QTMzQjBCODRGNTc3AAoJEF4oozsLhPV33AsP/Rb3QE49NLy9wqXWtVPpR7IH PTsEzLmjTnVwnzvHa7Zg6nlHtHPOn9MiEERfelUQIiiurAtAhd0mfz/QQYNZtklx yrLriODWpvLYAmIhLcxgp1iRHZa+2kRhmuF12SPF3TbqnIeKQcQeo9Xrt/lr/Ttx 8td1HtYD6hUe2qh3iGcWjYcQ/USzuLz7TN8T2aupEV5WSdCGmOa8ZrlAHjA+f6um 1QFKjtC+ftExPMYjw2HRkHtR2FOgatNhk2Kgo7ltpI2fPX1KddwDMsjzOgTGOLm8 vb14k0O3hITYG9U7o7/Z7zcb8fsgjOZA857MISjbq9AmWl/cEGlHe3h2pSZFmIjE xH23YbHVF5qSXKvFS8L+0OHuFuaPcYcl//b/RNGditZilErsIqDWxDUEQoEAFfu/ a9e3roN5wE1LdK1mHJVps86tSGd2fKCljQzFELTAU+29gpK8jNOuIj0126BclULI 8fVURoGISG6WFZ0GNe2NyJfU0ZF1Bp6LAoI1SOy5k5+Su9ijJsggudEJwhb3EJPg 6o2mQliOou1odeu98k3wnHcuahkMUJfrhzFdwp3c9EJSfvwJjk+4Fom1xfzNjTUh +Ofxz2f7DUVvKGMtKl9hO/zw+qFDX7AcLPKZSDWGawpXLbIWzswMaZkexsToCrS6 6JVcXC8myHbqVFTFLGcJ =orDR -----END PGP SIGNATURE----- --fAHbpOag9XbBjmBksEL4WHotO80RKBkun--