I see, thanks. It seems that there is an ambiguity here. Binary dependency might mean a dependency in a binary package as defined in the source package's control file, or it might mean a dependency in a binary package as defined in a binary package's control file only.
It seems that check_mir is using the former and calling parse_depends, and python-apt requires parse_src_depends in this case. The only documentation I see in python-apt doesn't appear to actually describe where the name "src" comes from. The confusion seems to be that "src" might mean that we're parsing a source package's control file (the assumption that python-apt makes), or that we're parsing the source package's build-depends in the source package's control file (the assumption that check-mir makes). It looks like the spec difference between parse_src_depends and depends is just that parse_src_depends resolves all arch-specific dependencies based on the value of APT::Architecture, so I think this can just be swapped out wholesale without causing any issues. check-mir still won't be perfect, but at least it'll give _an_ answer valid for one architecture, rather than crashing with no answer at all for packages that use this feature. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1149679 Title: [check-mir] cannot parse dependencies with architecture restrictions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1149679/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
