Path: csiph.com!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod From: Julian Gilbey Newsgroups: linux.debian.maint.python Subject: Re: pdm-pep517: Shall we package it now? Date: Thu, 30 Jun 2022 08:40:01 +0200 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Thu Jun 30 06:30:28 2022 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.19 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LDO_WHITELIST=-5, MURPHY_DRUGS_REL8=0.02, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no X-Policyd-Weight: NOT_IN_SBL_XBL_SPAMHAUS=-1.5 CL_IP_EQ_FROM_MX=-3.1; rate: -4.6 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Mailing-List: archive/latest/20038 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/Yr1C8utW7U+ir5Eo@d-and-j.net Approved: robomod@news.nic.it Lines: 34 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-python@lists.debian.org X-Original-Date: Thu, 30 Jun 2022 07:30:10 +0100 X-Original-Message-ID: X-Original-References: <758d24dbf569e25a1cb40318168e54a959d93619.camel@debian.org> <20220628133255.cpghnmzky37etuso@satie.tumbleweed.org.za> <4315374155e7935d682d31a13153e5889e9f704d.camel@debian.org> Xref: csiph.com linux.debian.maint.python:14208 On Wed, Jun 29, 2022 at 10:58:48AM -0400, Boyuan Yang wrote: > Hi, > [...] > Thanks. I have uploaded an initial version to the NEW queue. The packaging > work is at https://salsa.debian.org/python-team/packages/pdm-pep517/ . > > It is worth noting that I took the very aggressive way in stripping every > vendored libraries, see > https://salsa.debian.org/python-team/packages/pdm-pep517/-/tree/master/debian/patches > . This may not be ideal since the patch will need human intervention for every > new upstream release, but anyway let's have a working version in Sid first. > Meanwhile, any review or other types of help would be appreciated. Hi Boyuan, I've just taken a look; the exclusions and patching look fine to me. Yes, there will need to be some human intervention, but there always should be for new upstream versions. It may well be that all that is needed is to refresh the patch and run: quilt push -a rgrep _vendor pdm (or the equivalent gbp pq push or something like that) to check that nothing has changed. One small change to the patch: * In pdm/pep517/utils.py and pdm/pep517/wheel.py, there is no need to insert an "import packaging" Best wishes, Julian