Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod From: Andreas Tille Newsgroups: linux.debian.maint.python Subject: Re: [Help] Bug#938668: tifffile: Python2 removal in sid/bullseye Date: Thu, 05 Sep 2019 22:00:01 +0200 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Thu Sep 5 19:52:14 2019 Old-Return-Path: X-Amavis-Spam-Status: No, score=-5.34 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, RCVD_IN_DNSWL_NONE=-0.0001, SARE_MLH_Stock10=1.66] autolearn=no autolearn_force=no X-Policyd-Weight: using cached result; rate:hard: -3.5 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: NeoMutt/20170113 (1.7.2) X-Mailing-List: archive/latest/17283 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/20190905195200.jpgzs7zjut4u4vba@an3as.eu Approved: robomod@news.nic.it Lines: 44 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-python@lists.debian.org X-Original-Date: Thu, 5 Sep 2019 21:52:00 +0200 X-Original-Message-ID: <20190905195200.jpgzs7zjut4u4vba@an3as.eu> X-Original-References: <20190905174215.ddifllftxd7dw2qo@an3as.eu> <20190905180622.GF8787@belkar.wrar.name> Xref: csiph.com linux.debian.maint.python:11765 Hi Andrey, On Thu, Sep 05, 2019 at 11:06:22PM +0500, Andrey Rahmatullin wrote: > > Depends: python3-numpy (>= 1:1.16.0~rc1), python3-numpy-abi9, python3:any, python:any > > > > > > How can I get rid of the python:any dependency? > You ship a Python 2 script, /usr/bin/tifffile. It also doesn't work, for > obvious reasons. Fix its shebang. Argh. Thanks a lot for opening my eyes. > It would also be a good idea to test it > before the last upload, but as nobody noticed that the package doesn't > work since it was broken in December and got into buster, maybe it should > just be RMed? Good question. I admit I'm actually a bit pissed since the former maintainer introduced several packages into the team and than simply left the team. I tried my best to get the packages in a decent state but in this case failed obviously. I've just checked popcon of "vote" which is not really amazing. > I've just filed an RC bug for it. Fixed in new upload. > Also, my understanding is that public modules should be packaged > separately as python3-foo packages and private modules should be put into > private paths, but this package ships a public module and the changelog > entry says "The package does not really provide a Python module for > inclusion into other projects." See > https://www.debian.org/doc/packaging-manuals/python-policy/programs.html#current_version_progs Thanks for the hint. I admit I try to concentrate on other Python3 migration issues. In case some more problems come up with tifffile I'll reconsider RM. Kind regards Andreas. -- http://fam-tille.de