control: forcemerge 803778 -1 Hi,
thanks for reporting this. I already filed bug #803778 and committed a fix. As a workaround you may build wine-development locally for the i386 architecture. I see that you only have wine64, but not wine32 installed. Is this a result of the current issue, or did you really use Wine without the 32-bit packages installed previously? I was under the impression that a 64-bit only setup has no *real* use case and may fail. If I was wrong about that we might take another approach: E.g. build the "arch all" package only on 32-bit architectures (not sure if something like "Architecture: all [any-i386 any-powerpc armhf]" is already supported). Pro: manpages exist also for wine64 installation. Con: local 64-bit-only builds lack the wine-development package. IMO a clean handling of the manpages is not worth this disadvantage. Or patch the buildystem. Pro: Manpages always available and installed. Con: Potential of sideeffects, maintenance burden. I definitely don't want that. All in all I'd still go with my committed fix (move manpages to wine32), but I'd be less happy with it. Greets jre
