> I reported that bug. Indeed, that's why I was confused! :D
> After reading my report three times, I see how you > might have interpreted it that way. I wrote that there is a problem, > "because asciidoctor is Architecture: all and implicitly Multi-Arch: > no". The problem results from the combination of those fields, not from > either single field. The satisfiability problem is fully solved by the > Multi-Arch: foreign field alone regardless of the Architecture value. After reviewing the change, I don't exactly remember why I did the change only on the ruby-asciidoctor package but I'm guessing I simply forgot to update asciidoctor arch part when doing the split. I'll have a look at it asap. Joseph