Groups > linux.debian.maint.python > #7959

Re: Rebuild for packages with entry points?

Path	csiph.com!eternal-september.org!feeder.eternal-september.org!aioe.org!bofh.it!news.nic.it!robomod
From	Simon McVittie <smcv@debian.org>
Newsgroups	linux.debian.maint.python
Subject	Re: Rebuild for packages with entry points?
Date	Wed, 09 Dec 2015 01:40:01 +0100
Message-ID	<qDAXv-10W-5@gated-at.bofh.it> (permalink)
References	<qD8HW-8aH-63@gated-at.bofh.it> <qD9kC-bo-9@gated-at.bofh.it> <qDbcK-1od-15@gated-at.bofh.it> <qDtMm-4Ra-15@gated-at.bofh.it>
X-Original-To	debian-python@lists.debian.org
X-Mailbox-Line	From debian-python-request@lists.debian.org Wed Dec 9 00:33:27 2015
Old-Return-Path	<smcv@debian.org>
X-Amavis-Spam-Status	No, score=-7 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5] autolearn=ham autolearn_force=no
X-Policyd-Weight	using cached result; rate: -5
X-Sending-Uid	1000
X-Enigmail-Draft-Status	N1110
User-Agent	Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.4.0
MIME-Version	1.0
Content-Type	text/plain; charset=utf-8
Content-Transfer-Encoding	8bit
X-Mailing-List	<debian-python@lists.debian.org> archive/latest/13275
List-ID	<debian-python.lists.debian.org>
List-URL	<https://lists.debian.org/debian-python/>
List-Archive	https://lists.debian.org/msgid-search/566776C7.2030209@debian.org
Approved	robomod@news.nic.it
Lines	20
Organization	linux.* mail to news gateway
Sender	robomod@news.nic.it
X-Original-Date	Wed, 9 Dec 2015 00:33:11 +0000
X-Original-Message-ID	<566776C7.2030209@debian.org>
X-Original-References	<87mvtmt8yx.fsf@thinkpad.rath.org> <20151207140022.1e7f9e19@limelight.wooz.org> <5665F448.9040909@debian.org> <87twnsrijc.fsf@thinkpad.rath.org>
Xref	csiph.com linux.debian.maint.python:7959

Show key headers only | View raw

On 08/12/15 16:50, Nikolaus Rath wrote:
> On Dec 07 2015, Simon McVittie <smcv@debian.org> wrote:
>> 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?

If you already know a complete set of packages that have entry points,
sure, rebuild away. For binNMUs of arch:any packages the thing to do is
to ask the release team; for arch:all packages, it needs to be done as
individual sourceful uploads, unfortunately.

If you don't already know a complete set of affected packages, a Lintian
check + a bit of waiting would tell you, with progress tracking. I've
found that very useful for various issues with dbus policy files.

    S

Thread

Rebuild for packages with entry points? Nikolaus Rath <Nikolaus@rath.org> - 2015-12-07 19:30 +0100
  Re: Rebuild for packages with entry points? Barry Warsaw <barry@debian.org> - 2015-12-07 20:10 +0100
    Re: Rebuild for packages with entry points? Simon McVittie <smcv@debian.org> - 2015-12-07 22:10 +0100
      Re: Rebuild for packages with entry points? Nikolaus Rath <Nikolaus@rath.org> - 2015-12-08 18:00 +0100
        Re: Rebuild for packages with entry points? Simon McVittie <smcv@debian.org> - 2015-12-09 01:40 +0100
    Re: Rebuild for packages with entry points? Nikolaus Rath <Nikolaus@rath.org> - 2015-12-08 17:50 +0100
      Re: Rebuild for packages with entry points? Barry Warsaw <barry@debian.org> - 2015-12-08 18:00 +0100
        Re: Rebuild for packages with entry points? Nikolaus Rath <Nikolaus@rath.org> - 2015-12-08 23:10 +0100
          Re: Rebuild for packages with entry points? Piotr Ożarowski <piotr@debian.org> - 2015-12-09 09:40 +0100
  Re: Rebuild for packages with entry points? Brian May <bam@debian.org> - 2015-12-09 07:10 +0100

csiph-web