Hi,
2017-10-22 20:07 Helmut Grohne:
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.
[...]
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.
So, Piotr, do you think that any of the options is preferable?
If there's no reply I'd like to upload an NMU with a fix for this
problem.
I think that changing the package to "Architecture: any" and "M-A: same"
is safer than dropping a dependency to recommends. It's not ideal, but
in the end is just causes a small overhead, and changing dependencies
can even break reverse-depends and introduce bugs difficult to detect.
Cheers.
--
Manuel A. Fernandez Montecelo <manuel.montez...@gmail.com>
