Path: csiph.com!news.redatomik.org!aioe.org!bofh.it!news.nic.it!robomod
From: Thomas Goirand <zigo@debian.org>
Newsgroups: linux.debian.maint.python
Subject: Re: converting to git-dpm (was: Update of python-xlwt with Py3  support)
Date: Thu, 26 Oct 2017 15:20:02 +0200
Message-ID: <uEQeK-5QJ-9@gated-at.bofh.it>
References: <uEyhP-383-5@gated-at.bofh.it> <uEO3f-4lk-3@gated-at.bofh.it> <uEQ54-5ND-13@gated-at.bofh.it>
X-Mailbox-Line: From debian-python-request@lists.debian.org  Thu Oct 26 13:17:30 2017
Old-Return-Path: <zigo@debian.org>
X-Amavis-Spam-Status: No, score=-6.98 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, MURPHY_DRUGS_REL8=0.02, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
X-Policyd-Weight: using cached result; rate:hard: -5
Organization: Debian
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Mailing-List: <debian-python@lists.debian.org> archive/latest/15341
List-ID: <debian-python.lists.debian.org>
List-URL: <https://lists.debian.org/debian-python/>
List-Archive: https://lists.debian.org/msgid-search/63f517e4-b338-f751-0dc4-7cda70433e49@debian.org
Approved: robomod@news.nic.it
Lines: 18
Sender: robomod@news.nic.it
X-Original-Date: Thu, 26 Oct 2017 15:17:09 +0200
X-Original-Message-ID: <63f517e4-b338-f751-0dc4-7cda70433e49@debian.org>
X-Original-References: <c5e31a1a-fc4f-74a7-7bdf-18071048c056@debian.org> <20171026102724.xs26wecyhhk4igsd@mail.dittberner.home> <449a9000-ff92-bbb6-5523-457d258156b6@debian.org>
Xref: csiph.com linux.debian.maint.python:9958

On 10/26/2017 03:02 PM, Thomas Goirand wrote:
> To avoid breakage, I'll wait for antlr support for Python 3 passes the
> NEW queue, and then upload. I've already merged to master.

I've found out that antlr.py is embedded, and still in use in this
upstream release. So I added a patch to remove it from upstream.

However, the package was using git-dpm. As always, importing a new
release with git-dpm is a nightmare. Therefore, before doing it, I
simply removed all patches (as I thought no patch was needed). Now,
what's the way to make it again so that the package uses git-dpm? Is it
still needed these days, or is it ok to not do it in the team?

Cheers,

Thomas Goirand (zigo)

P.S: As I wrote, I didn't upload yet...