On Fri, Oct 20, 2017 at 10:03:01PM +0200, Manuel A. Fernandez Montecelo wrote: > #875650 looks like a duplicate of #769380, and according to #769380 back > in 2014 josch and helmut seem to have concluded that the better solution > was to either change the package to "Architecture: any" and "M-A: same", > or demote the dependency on python-markupsafe.
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. > So I think that the bugs should be merged, and 3 years later than the > original submission, I think that it's time to solve this issue unless > there's a good reason to not change it in this way, because it affects > hundreds of packages for cross-compilation. It is true that this bug theoretically affects a lot of packages (318). The vast majority of these (258) go through gobject-introspection though and will fail to cross build even if this bug is fixed. From what I understand now, gobject-introspection looks pretty much unfixable. So realistically, this bug affects 60 packages. > Since the package is actively maintained and you uploaded a version very > recently, I am not sure if it makes much sense to offer to NMU, but > nevertheless if we can help in some way, please tell. The issue here is that the bug kinda is under (inactive) discussion: There are multiple ways to fix and nobody knows which one is better. The first question to answer is whether it would be reasonable to demote the dependency on markupsafe to recommends. Having an answer on that question from someone of the DPMT would be very helpful. Barring that, we're still talking with Guillem whether dpkg could allow :native annotations on Arch:all packages (which dose does allow). In case that moves forward, we might be able to cancel this bug. 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. Helmut
