Path: csiph.com!news.mixmin.net!eternal-september.org!feeder.eternal-september.org!aioe.org!bofh.it!news.nic.it!robomod
From: Nikolaus Rath <Nikolaus@rath.org>
Newsgroups: linux.debian.maint.python
Subject: Re: Rebuild for packages with entry points?
Date: Tue, 08 Dec 2015 18:00:02 +0100
Message-ID: <qDtMm-4Ra-15@gated-at.bofh.it>
References: <qD8HW-8aH-63@gated-at.bofh.it> <qD9kC-bo-9@gated-at.bofh.it> <qDbcK-1od-15@gated-at.bofh.it>
Old-Return-Path: <Nikolaus@rath.org>
Mail-Copies-To: never
Mail-Followup-To: debian-python@lists.debian.org
User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/24.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Approved: robomod@news.nic.it
Lines: 28
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.python:7956

On Dec 07 2015, Simon McVittie <smcv@debian.org> wrote:
> On 07/12/15 19:00, Barry Warsaw wrote:
>> On Dec 07, 2015, at 10:22 AM, Nikolaus Rath wrote:
>>> It'd be nice to have https://bitbucket.org/pypa/setuptools/issues/443/
>>> fixed in stretch.
>>=20
>> I'm also not sure how many packages it affects in practice.  We could al=
so let
>> rebuilds be bug-driven.
>
> This looks like a job for Lintian, assuming setuptools entry points are
> easy to detect with a regex.

Well, yes, but what's the point? New uploads will not be affected by
this bug anyway, and if you just want the warnings for old packages,
wouldn't the time consumed by writing a Lintian check be better spent
writing a script that triggers rebuilds directly?


Best,
-Nikolaus

--=20
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

             =C2=BBTime flies like an arrow, fruit flies like a Banana.=C2=
=AB