Path: csiph.com!fu-berlin.de!bofh.it!news.nic.it!robomod From: c.buhtz@posteo.jp Newsgroups: linux.debian.maint.python Subject: Re: [Help] New package python-loky build time test times out Date: Wed, 25 Dec 2024 20:40:01 +0100 Message-ID: References: X-Original-To: Debian Python X-Mailbox-Line: From debian-python-request@lists.debian.org Wed Dec 25 19:38:13 2024 Old-Return-Path: X-Amavis-Spam-Status: No, score=-9.496 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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -5.5 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Mailing-List: archive/latest/22715 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/4226e68c154e1fdf36e291b5d95d95fd@posteo.de Approved: robomod@news.nic.it Lines: 25 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Wed, 25 Dec 2024 19:37:51 +0000 X-Original-Message-ID: <4226e68c154e1fdf36e291b5d95d95fd@posteo.de> X-Original-References: Xref: csiph.com linux.debian.maint.python:16622 Hello, I am a Python developer and upstream maintainer. I am not much experience when it comes to distro packaging. This is just an example of a case I often do observe. And I always ask myself why this happens. Am 25.12.2024 18:47 schrieb Andreas Tille: > the new version of python-cogent needs python-loky[1] I checked both package and do not understand why python-loky exist. It is a mini package with less benefit. Why does Debian burn resources in packaging things like this. I would ask python-cogent to remove that dependency instead of create a package for it. As upstream maintainer I would not dare to have dependencies like this in my project and bother distro maintainers with it. I am assuming this package will be orphaned in the near future. I am asking the upstream maintainer for a justification about this dependency: Regards, Christian