Bug#804046: No wine-development package and so not binary available anymore

[Klaus Ethgen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi, Jens,

Am Mi den  4. Nov 2015 um 16:28 schrieb Jens Reyer:
> control: forcemerge 803778 -1
> 
> thanks for reporting this. I already filed bug #803778 and committed a
> fix.

Thanks.

> As a workaround you may build wine-development locally for the i386
> architecture.

I did downgrade to 1.7.52-1.

> 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.

> 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.

Regards
   Klaus
- -- 
Klaus Ethgen  http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16   Klaus Ethgen 
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQGcBAEBCgAGBQJWOy7oAAoJEKZ8CrGAGfasW58L/AoCt9oHS9OqYWnPU0t8XWlW
JbGGZrqYrjMxZqnobGvJ8el0BeHU3GZV/Hiz7RGydTde66KeEaNk2V1WNTRGyRhk
FLZ1ejfO65xKTZoLuyZ1QE7CjwOe1CaWDFSLRWxaxwR/Xrc/CE065oGiqqSYqVrU
uFAZAx/MQFiospMLylryfx3ElvjLm2cD0cLhrgN2Y0TXz2ahxZEIZpALi2X0dqgi
A4I98OdhNg+hzLcCQyFc/g4lH30EwrC2bFs9UNHOK9GKKiKb4vW54WGEqpHIVsda
sR4tofMvTMWTwZ6NEbanlG+KorKCwoEtr54rPpxy5I8zfwUefNwdRdR0O1urOYHv
rpZ5Y4xTFAwL/+9LGtJ4ieUkOchP3sW2FsxEMMXquz8LW+bKbRk1TSPb7HJGXA8U
QIGo+otjO0YzF0ZoJt7pm7mku17CE7SHbXv7p4H5L1bjCsJvdmgHvbR+L/yocK+U
MEhQw7g8HnMCnInnn/KoAWFk2yV2OtO2GtV7WupHoA==
=w+pZ
-END PGP SIGNATURE-

Bug#804046: No wine-development package and so not binary available anymore

[Jens Reyer]

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.

Greets!
jre

Bug#804046: No wine-development package and so not binary available anymore

[Klaus Ethgen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package: wine64-development
Version: 1.7.54-1
Severity: grave

With 1.7.54-1 there is no wine-development package anymore so there is
no /usr/bin/wine-development to start wine.

That renders the whole package suit unusable for most people.

- -- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (500, 'testing'), (110, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.0.7 (SMP w/8 CPU cores)
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages wine64-development depends on:
ii  libc62.19-22
ii  libwine-development  1.7.52-1
ii  x11-utils7.7+3

Versions of packages wine64-development recommends:
ii  libasound2-plugins  1:1.0.29-dmo1
pn  libwine-gecko-2.40  
pn  wine-development
pn  wine32-development  

Versions of packages wine64-development suggests:
pn  wine64-development-preloader  

Versions of packages wine64-development is related to:
pn  fonts-wine-development
ii  libwine-development   1.7.52-1
pn  libwine-development-dbg   
pn  libwine-development-dev   
pn  wine-development  
pn  wine32-development
pn  wine32-development-preloader  
pn  wine32-development-tools  
ii  wine64-development1.7.52-1
pn  wine64-development-preloader  
pn  wine64-development-tools  

- -- no debconf information

- -- 
Klaus Ethgen  http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16   Klaus Ethgen 
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQGcBAEBCgAGBQJWOe5hAAoJEKZ8CrGAGfaszYEL/3MY2ByL7w4h7NF2gorlpD67
eEZMrmVm0V3RpGOI8zMLSU+/dcKuUoXBCfMgGcTHQJtJsGbdOOr4o1WpoR3FHEbM
tDsK7y2SmvNZnSgfiVw6VF4FqNOhFuM/na+RQ0radrACmru6VxETytSMHFujau+m
DANBDrkDTTYQ68DFJaNvQTWNVnZLGvCTcqAIeeuJ/EHl74uiFrt82gxtDHPvoySu
lgusr06jCd6Mv69IQxyKmLgsqTy9tyyMqScBU0prwk+8RTiLuI42DanNf0cBQm2s
d6m8Jy1QegH0hntqJMMRkhk14oPKrOw5sQGr6ZWwTtFdWNegvMQuHnrOgULOU5P/
MQR3NepZpwk5DRFGYz4FhC5LvCFNWVp5ah1beR7vUQ4n5SmRRur9Vu/vDrYc1b6A
R8W6oJYMZTo8bdBX1ME+LnPVrEXgtnQ7osSABzR0vmhBlJQXBvp75q5EHoj9ztYq
WAJJNtoc3wloPgc+ae8UUMax8+wM9XCGc0/ZMtPYag==
=nUVB
-END PGP SIGNATURE-

Processed: Re: Processed (with 1 error): Re: Bug#804046: No wine-development package and so not binary available anymore

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 804046 wine-development 1.7.54-1
Bug #804046 [wine64-development] No wine-development package and so not binary 
available anymore
Bug reassigned from package 'wine64-development' to 'wine-development'.
No longer marked as found in versions wine-development/1.7.54-1.
Ignoring request to alter fixed versions of bug #804046 to the same values 
previously set
Bug #804046 [wine-development] No wine-development package and so not binary 
available anymore
There is no source info for the package 'wine-development' at version 
'1.7.54-1' with architecture ''
Unable to make a source version for version '1.7.54-1'
Marked as found in versions 1.7.54-1.
> forcemerge 803778 804046
Bug #803778 [wine-development] wine-development: arch all FTBFS on 64-bit 
architectures
Bug #804046 [wine-development] No wine-development package and so not binary 
available anymore
Severity set to 'serious' from 'grave'
Added tag(s) pending.
Merged 803778 804046
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
803778: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803778
804046: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804046
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#804046: No wine-development package and so not binary available anymore

[Jens Reyer]

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

Processed (with 1 error): Re: Bug#804046: No wine-development package and so not binary available anymore

[Debian Bug Tracking System]

Processing control commands:

> forcemerge 803778 -1
Bug #803778 [wine-development] wine-development: arch all FTBFS on 64-bit 
architectures
Unable to merge bugs because:
package of #804046 is 'wine64-development' not 'wine-development'
Failed to forcibly merge 803778: Did not alter merged bugs.


-- 
803778: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803778
804046: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804046
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems