Hi, On Fri, 21 Nov 2014 10:41:03 +0100 Helmut Grohne <hel...@subdivi.de> wrote: > Adding M-A:foreign is wrong. Suppose you are trying to satisfy > python-mako:i386 on a system that is natively amd64. Then python-mako would > satisfy this dependency and use python-markupsafe:amd64 in its installation > set. However when importing modules in an embedded i386 python interpreter an > ImportError would be raised, because python-markupsafe is unavailable. Thus > python-mako exposes the architecture awareness of python-markupsafe and > cannot become M-A:foreign. > > It is not obvious how to solve this problem and it is not obvious > whether python-mako needs to be updated to solve it. In essence, this is > the famous "multiarch interpreter" problem at > https://wiki.debian.org/HelmutGrohne/MultiarchSpecChanges#Interpreter_issue. > > A feasibly workaround to apply now would be to switch python-mako to > arch:any M-A:same.
alternatively, python-mako could also demote its dependency on python-markupsafe to a recommends. python-markupsafe seems to only be used in mako/filters.py and there seems to be a fallback to pure Python in case python-markupsafe is not available. Thus python-markupsafe is not a strict dependency. Since python-make would then not strictly depend on python-markupsafe anymore, it could become m-a:foreign. cheers, josch -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
