Thanks a lot for your reply.
El 8/6/25 a las 15:18, Paul Gevers escribió:
However, src:lmfit-py doesn't run any tests on 32 bits architectures (the
binary is arch:all, but the tests don't support 32 bit) so src:lmfi-py can't
migrate without an unblock, or without a change to the package. Now the
question is, if the tests are skipped on 32 bit architecture, does that mean
that the package is broken on those architectures? If the tests are only
disabled because the tests are broken on those architectures, but the package
works anyways, than that's the reason why src:lmfit-py would need an unblock.
Good question. This is from commit [17b1c270] of src:lmfit-py by Picca
Frédéric-Emmanuel
(which I'm adding to Cc).
* d/t/control: Added architecture !armel !armhf !i386
The upstream do not provides support for these architectures.
I would guess that at some point some of those tests started to fail,
we probably asked upstream, and they probably told us "I don't care about
32-bit".
So based on the currently available information I don't really know if the tests
just fail or it's that the package is actually broken on 32-bit.
or without a change to the package.
Ok. I will probably ask for an unblock in a few days. For future reference:
What kind
of change to the package would help in cases like this one?
(Maybe we should invent a new control field to express "This is arch:all but
only
supported on such and such").
Thanks.
