Hi,

I was referring to #1061826.

I hadn't noticed that the error lies in openmm itself;
that was the source of my complete confusion.

So yes, openmm definitively needs to be fixed first.

623s /usr/lib/python3/dist-packages/openmm/app/gromacstopfile.py:45: in
<module>
623s     import distutils.spawn
623s E   ModuleNotFoundError: No module named 'distutils'

Le dim. 19 janv. 2025 à 16:11, Colin Watson <cjwat...@debian.org> a écrit :
>
> On Thu, Jan 16, 2025 at 09:45:19PM +0100, Alexandre Detiste wrote:
> > I fixed a bunch right now,
> > but I can't fix python3-pdbfixer
> > so easily because the previous release
> > already has another RC bug.
>
> It would be easier if you hadn't pushed a new upstream version to git
> before checking whether it had any new dependencies that aren't
> satisfied yet in Debian (it needs python3-openmm >= 8.2).  Things are
> always easier when the default branch remains buildable.
>
> What other RC bug are you referring to?  I guess maybe
> https://bugs.debian.org/1061826?  But I think that's actually been fixed
> in openmm already - I don't see any distutils imports in its code any
> more.
>
> > So I'm filling this bug to request some help
> > from the team.
>
> I think all that's needed is to branch from 1.9-4 (BTW, you forgot to
> push the debian/1.9-4 tag), add the missing Depends:
> python3-pkg-resources, and upload that as 1.9-5.  Does that sound right
> to you?
>
> Maybe also file a wishlist bug on openmm to upgrade to the new upstream
> version.
>
> --
> Colin Watson (he/him)                              [cjwat...@debian.org]

Reply via email to