Hi Colin, On Sun, 2 Dec 2012 00:09:08 +0000, Colin Watson wrote:
> lynx-cur is Architecture: any, but on a multiarch system it doesn't > matter which architecture you get as long as you can execute its > binaries. Six source packages in unstable build-depend on it directly, > and 40 more would if they noticed that lynx is a transitional package > and replaced it with lynx-cur. Accordingly, it would be helpful to mark > lynx-cur Multi-Arch: foreign to avoid blocking cross-builds of those > packages. For example, at the moment xterm fails to cross-build in > Ubuntu because it tries to run lynx but only has the version for the > host architecture (the one being built for) rather than the build > architecture (the one being built on). > > There would be no harm in marking lynx-cur-wrapper and lynx Multi-Arch: > foreign as well, even though they're transitional and Architecture: all. > On Ubuntu this is in practice unnecessary for Architecture: all packages > in cross-build-dependencies due to an apt patch, but that patch hasn't > yet been accepted into Debian so it still makes a difference there. In > any case it seems good to be explicit. Thanks for your explanation. In fact I don't have clear understandung of Multi-Arch so now I try to understand it by browsing http://wiki.debian.org/Multiarch/ . I will undate the package as soon as possible. Best regards, 2012-12-4(Tue) -- Debian Developer - much more I18N of Debian Atsuhito Kohda <kohda AT debian.org> Department of Math., Univ. of Tokushima -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
