[Debian-med-packaging] Bug#1083322: I consider issue fixed in version 2.10.1-1 of brian (Was: severity of 1083322 is serious)

Alexandre Detiste alexandre.detiste at gmail.com
Wed Jun 3 21:56:07 BST 2026


Hi,

It's quite a long story.
For many years, a "setuptools" in setup.py would be translated into a
python3-pkg-resources
dependency, which is/was a confusing Debian-only thing.

Not this is reverted, so this will generate a _runtime_ dependency on
python3-setuptools
that 99% packages built with setuptools don't need.

So the most common fix is a one-line patch to setup.py / pyproject.toml
that put the "setuptools" in the correct category.

As of today, brian still depends on python3-setuptools.

I did _not_ checked again this specific package now;
having the whole story is more important.

One can ask the python Team when they want to finish this cleansing.

I did NMUed mini-soong because it bothered lingering here:
https://bugs.debian.org/release-critical/other/testing.html

Greetings

Le mer. 3 juin 2026 à 10:10, Andreas Tille <tille at debian.org> a écrit :
>
> Hi Alexandre
>
> Am Sun, Feb 15, 2026 at 07:49:20PM +0100 schrieb Alexandre Detiste:
> > severity 1083322 serious
> > thanks
>
> you reopened this bug for version 2.9.0-2.  I think it is fixed in
> 2.10.1-1.  Could you please check and be more verbose how to check?
>
> Kind regards
>    Andreas.
>
> --
> https://fam-tille.de



More information about the Debian-med-packaging mailing list