01.12.2024 22:32, Helmut Grohne wrote:
Hi Alexandre,
Sorry for having missed this earlier and thanks to Stefano for poking
me.
On Wed, Aug 14, 2024 at 01:59:54PM +0200, Alexandre Detiste wrote:
Can you confirm ?
I do confirm that it is sensible and useful to mark python3-urllib3
M-A:foreign.
Stefano also asked me to iterate on why we need such chanegs. Python
modules tend to turn up in Build-Depends here and there. An Arch:all
Python module generally becomes unsatisfiable in cross builds. A simple
change that makes it satisfiable is annotating it M-A:foreign as is
being requested here. That explains why it is useful to perform such
marking.
The tricky part is figuring out whether M-A:foreign actually is correct.
In particular, M-A:foreign must not be applied if the module has a
transitive dependency on a Python extension module.
This is why I mentioned in my initial report that it's safe in this case
to mark this with M-A: foreign, because there's no problematic dependencies
(or inter-dependencies).
I probably should've explained all this too since it's the base behind my
own knowledge as well. But somehow I weren't as helpful here as Helmut :)
Thanks,
/mjt
