On Thu, 24 Nov 2011 02:37:25 -0500, Michael Gilbert wrote:
Maybe the real issue here is that the build-depends dependency analysis is only done on i386 (according to the wording "including build-depends; i386 only"), and the ia32-libs-dev package of course doesn't exist there?
That's one of the many reasons why that section of the page is unhelpful, yes.
It also shouldn't mix runtime and build dependencies, and shouldn't care a hoot whether build-dependencies exist in testing or not. In fact, it probably shouldn't care if they exist in unstable, to be honest, as they have no direct relevancy to migration.
Anyway, I think my original point remains
Your original point seemed to be that you'd "worked out" that ia32-libs-dev not being in testing on kfreebsd-amd64 was somehow affecting the wine-unstable packages. What I've been trying to do is to point out to you why you were mistaken in what you believed that page showed, before you wasted any further time attempting to fix issues that don't exist. :-/ (The failures on amd64 and powerpc do matter, otoh).
For the dependencyanalysis to be unambiguous like in this case, it needs to be generatedon a per-arch basis.
Indeed. If you'd started from that point and not mentioned any of the confused kfreebsd-amd64 stuff, my original response would probably simply have been "patches welcome" and we could have left it there... ah well.
Regards, Adam