[pkg-wine-party] Bug#804046: No wine-development package and so not binary available anymore

Jens Reyer jre.winesim at gmail.com
Thu Nov 5 15:57:47 UTC 2015

On 11/05/2015 11:26 AM, Klaus Ethgen wrote:
>> 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.
> Well, it is the result of the issue. But I don't use wine32 that much. I
> only use wine64 playing WoW (The only usecase for me :-D). That works
> well. Unfortunatelly for updates that doesn't as it battlenet is 32bit
> only.

But you had it installed, so you would have the manpages installed with
my proposed fix.

Re 64-bit-only installs: I digged that up and they are indeed not
supported by upstream. *Not* installing the recommended wine32-package
(with the manpages) is considered advanced and done on purpose (=don't
complain if something doesn't work, or if the manpages are missing).

>> All in all I'd still go with my committed fix (move manpages to wine32),
>> but I'd be less happy with it.
> If the man pages do the trouble, why not splitting out them to a -doc
> package? That would be the cleanest way.

Unfortunately no, they are only built on 32-bit arches now. So unless we
change the buildsystem they are just not available from 64-bit builds.
So a -doc package doesn't help here.


More information about the pkg-wine-party mailing list