On Monday, 23 October 2017 5:07 AM, Helmut Grohne wrote: > They kinda are duplicates, but unless the markupsafe dependency is > demoted, the advice from #875650 to add m-a:foreign is simply wrong. > Since #769380 contains all the deatils, I am simply closing the newer > bug.
In what way? Marking M-A: foreign satisfies the build-dependencies I need. Otherwise, I have to deal with python3-mako:i386 not found. Either way, I'd have preferred you to merge #875650 with #769380, not just close it. > If all else fails, I see no way around turning it Arch:any at some > point. What we need here is an answer to the demotion question to move > on. Well, hopefully this doesn't take another three years. :-)
