Bug#1031649: wine: /usr/bin/wine64 still required

2023-03-09 Thread Paul Gevers

Hi Jens,

On 09-03-2023 19:06, Jens Reyer wrote:

2.
Keep everything as it is now, make sure vulkan 1.3.239 doesn't make it 
to bullseye, and bullseye-ignore this and the 2 other bugs.


I assume you ment bookworm when you wrote bullseye here. However:
$ rmadison  -s unstable,testing vulkan-loader
vulkan-loader | 1.3.239.0-1   | testing| source
vulkan-loader | 1.3.239.0-1   | unstable   | source

vulkan already migrated a month ago, so that ship has sailed.

Paul


OpenPGP_signature
Description: OpenPGP digital signature


Bug#1031649: wine: /usr/bin/wine64 still required

2023-03-09 Thread Jens Reyer

Hi Paul

On 09.03.23 15:50, Paul Gevers wrote:

Hi,

On Sun, 19 Feb 2023 18:17:39 -0600 Austin English 
 wrote:



Yes, it's arguably a bug in winetricks. Film what I gather upstream,
it's also not yet fully supported.
On Sat, 25 Feb 2023 17:10:47 +0100 Jens Reyer  
wrote:
ftr: I just uploaded a new winetricks 20230212-1 to unstable which 
should migrate to bookworm before the hard freeze. It workarounds a 
missing /usr/bin/wine64. The fix is quite late in Winetricks logic to 
figure out wine64, so it should work just fine with both setups.  
Tested against wine 8.0~repack-2, 8.0~repack-4 and winehq-staging 
8.2~bookworm-1.


If I understand correctly, this bug can now be downgraded in severity 
because winetricks migrated to bookworm. Maybe even better, reassign to 
winetricks and close it with the version in bookworm? Or am I missing 
the point?


Well, yes, from my winetricks perspective this bug could be closed as 
described.



But I suspect (without any evidence) that a missing /usr/bin/wine64 also 
affects others, at least in non-packaged software, but maybe also in 
Debian. Changing this now shortly before the release imo calls for 
trouble. In general I think /usr/bin/wine64 should be kept as long as 
Wine is built as it is now, since just too many people got used to it. 
Only once Wine is built the new way (upstream is still working on this) 
this setup should be changed.


This change was intended to fix #1029536, where I unfortunately 
mentioned that removing /usr/bin/wine64 might solve the issue. That 
issue may be either ignored or preferably fixed another way, e.g. by 
doing a "ln -s /usr/lib/wine/wine64 /usr/lib/wine/wine64-stable".


Finally this issue here blocked the fix for #1031102 from migrating to 
testing.  As far as I see that could be ignored, since it's a build 
issue with vulkan 1.3.239, which is also only in unstable. I do not know 
if the current wine 8.0~repack-4 would even build with the vulkan 
currently in testing. If it doesn't there would be a new rc bug.


So we have three options (ordered best to least from my perspective, and 
assuming wine builds with both vulkan versions from testing and unstable 
(requirement for 1 and 3). Please note that I stepped down from 
maintaining wine, and might miss something).


1.
Revert the /usr/bin/wine64 removal, add the /usr/lib/wine/wine64-stable 
link instead, and then let wine migrate to bullseye.


2.
Keep everything as it is now, make sure vulkan 1.3.239 doesn't make it 
to bullseye, and bullseye-ignore this and the 2 other bugs.


3.
Reassign this bug as you suggested to winetricks and close it with the 
version in bookworm.


Greets
jre



Bug#1031649: wine: /usr/bin/wine64 still required

2023-03-09 Thread Paul Gevers

Hi,

On Sun, 19 Feb 2023 18:17:39 -0600 Austin English 
 wrote:



Yes, it's arguably a bug in winetricks. Film what I gather upstream,
it's also not yet fully supported.

On Sat, 25 Feb 2023 17:10:47 +0100 Jens Reyer  wrote:
ftr: I just uploaded a new winetricks 20230212-1 to unstable which 
should migrate to bookworm before the hard freeze. It workarounds a 
missing /usr/bin/wine64. The fix is quite late in Winetricks logic to 
figure out wine64, so it should work just fine with both setups.  Tested 
against wine 8.0~repack-2, 8.0~repack-4 and winehq-staging 8.2~bookworm-1.


If I understand correctly, this bug can now be downgraded in severity 
because winetricks migrated to bookworm. Maybe even better, reassign to 
winetricks and close it with the version in bookworm? Or am I missing 
the point?


Paul


OpenPGP_signature
Description: OpenPGP digital signature


Bug#1031649: wine: /usr/bin/wine64 still required

2023-02-25 Thread Jens Reyer

On 20.02.23 01:17, Austin English wrote:
On Sun, Feb 19, 2023, 17:33 Jens Reyer > wrote:
Yes, it's arguably a bug in winetricks. Film what I gather upstream, 
it's also not yet fully supported.


I would advise reverting for now. At least until upstream fully supports it.


ftr: I just uploaded a new winetricks 20230212-1 to unstable which 
should migrate to bookworm before the hard freeze. It workarounds a 
missing /usr/bin/wine64. The fix is quite late in Winetricks logic to 
figure out wine64, so it should work just fine with both setups.  Tested 
against wine 8.0~repack-2, 8.0~repack-4 and winehq-staging 8.2~bookworm-1.




Bug#1031649: wine: /usr/bin/wine64 still required

2023-02-19 Thread Austin English
On Sun, Feb 19, 2023, 17:33 Jens Reyer  wrote:

> On 19.02.23 21:45, Floris Renaud wrote:
> > Isn't this a bug in winetricks? When Wine is compiled the new way
> > (--enable-archs=i386,x86_64), there isn't, as far as I know, a wine64
> file.
> >
> >  From
> >
> https://github.com/Winetricks/winetricks/blob/master/src/winetricks#L3113
> > ---
> >
> > # Wrapper around winetricks_early_wine()
> > # Same idea, but use $WINE_ARCH, i.e., always use wine64 for 64-bit
> > prefixes
> > # Currently only used by w_expand_env()
> > winetricks_early_wine_arch()
> > {
> >  WINE="${WINE_ARCH}" winetricks_early_wine "$@"
> > }
> > ---
>
> I see, thanks.  Well, then it should probably be changed in winetricks
> for this new Wine build.
>
> But still, this change (prompted by a similar issue in a non-default
> Wine installation) breaks previously working setups in default
> installations.  I didn't think of that when originally mentioning this
> as a solution, but now I think changing this now shortly before a Debian
> release is not good.
>

Yes, it's arguably a bug in winetricks. Film what I gather upstream, it's
also not yet fully supported.

I would advise reverting for now. At least until upstream fully supports it.


Bug#1031649: wine: /usr/bin/wine64 still required

2023-02-19 Thread Jens Reyer

On 19.02.23 21:45, Floris Renaud wrote:
Isn't this a bug in winetricks? When Wine is compiled the new way 
(--enable-archs=i386,x86_64), there isn't, as far as I know, a wine64 file.


 From 
https://github.com/Winetricks/winetricks/blob/master/src/winetricks#L3113

---

# Wrapper around winetricks_early_wine()
# Same idea, but use $WINE_ARCH, i.e., always use wine64 for 64-bit 
prefixes

# Currently only used by w_expand_env()
winetricks_early_wine_arch()
{
     WINE="${WINE_ARCH}" winetricks_early_wine "$@"
}
---


I see, thanks.  Well, then it should probably be changed in winetricks 
for this new Wine build.


But still, this change (prompted by a similar issue in a non-default 
Wine installation) breaks previously working setups in default 
installations.  I didn't think of that when originally mentioning this 
as a solution, but now I think changing this now shortly before a Debian 
release is not good.


Greets
jre



Bug#1031649: wine: /usr/bin/wine64 still required

2023-02-19 Thread Floris Renaud





On zondag 19 februari 2023 20:08:54 (+01:00), Jens Reyer wrote:

> Source: wine
> Version: 8.0~repack-4
> Severity: serious
> 
> Hi Mike,
> 
> I wasn't aware of this, but it seems indeed that /usr/bin/wine64 is 
required somehow: winetricks fails to start with 8.0~repack-4, but works 
with 8.0~repack-2.
> 
> I don't understand yet what's exactly going wrong (winetricks complains 
about some empty output, but if I execute said command manually I get the 
output), but I think the recent change should be reverted.
> 
> Greets anyway!

> jre
> 
> 
> 
> Winetricks fails with 8.0~repack-4:
> 
> jens@thing:~$ wine --version

> wine-8.0 (Debian 8.0~repack-4)
> jens@thing:~$ winetricks
> Executing mkdir -p /home/jens
> --
> warning: You are using a 64-bit WINEPREFIX. Note that many verbs only 
install 32-bit versions of packages. If you encounter problems, please 
retest in a clean 32-bit WINEPREFIX before reporting a bug.

> --
> --
> WINEPREFIX INFO:
> Drive C: total 28
> drwxr-xr-x  7 jens jens 4096 Feb 13 21:28 .
> drwxr-xr-x  4 jens jens 4096 Feb 19 19:50 ..
> drwxr-xr-x  3 jens jens 4096 Feb 13 21:28 ProgramData
> drwxr-xr-x  6 jens jens 4096 Feb 13 21:28 Program Files
> drwxr-xr-x  6 jens jens 4096 Feb 19 19:28 Program Files (x86)
> drwxr-xr-x  4 jens jens 4096 Feb 13 21:28 users
> drwxr-xr-x 21 jens jens 4096 Feb 19 19:28 windows
> 
> Registry info:

> /home/jens/.wine/system.reg:#arch=win64
> /home/jens/.wine/user.reg:#arch=win64
> /home/jens/.wine/userdef.reg:#arch=win64
> --
> --
> warning: wine cmd.exe /c echo '%AppData%' returned empty string, error 
message ""

> --
> jens@thing:~$ echo $?
> 1
> jens@thing:~$ wine cmd.exe /c echo '%AppData%'
> 0098:err:winediag:is_broken_driver Broken NVIDIA RandR detected, falling 
back to RandR 1.0. Please consider using the Nouveau driver instead.
> 0034:err:winediag:is_broken_driver Broken NVIDIA RandR detected, falling 
back to RandR 1.0. Please consider using the Nouveau driver instead.

> C:\users\jens\AppData\Roaming
> 
> 

Isn't this a bug in winetricks? When Wine is compiled the new way 
(--enable-archs=i386,x86_64), there isn't, as far as I know, a wine64 file.


From 
https://github.com/Winetricks/winetricks/blob/master/src/winetricks#L3113

---

# Wrapper around winetricks_early_wine()
# Same idea, but use $WINE_ARCH, i.e., always use wine64 for 64-bit 
prefixes

# Currently only used by w_expand_env()
winetricks_early_wine_arch()
{
WINE="${WINE_ARCH}" winetricks_early_wine "$@"
}
---



Bug#1031649: wine: /usr/bin/wine64 still required

2023-02-19 Thread Jens Reyer

Source: wine
Version: 8.0~repack-4
Severity: serious

Hi Mike,

I wasn't aware of this, but it seems indeed that /usr/bin/wine64 is 
required somehow: winetricks fails to start with 8.0~repack-4, but works 
with 8.0~repack-2.


I don't understand yet what's exactly going wrong (winetricks complains 
about some empty output, but if I execute said command manually I get 
the output), but I think the recent change should be reverted.


Greets anyway!
jre



Winetricks fails with 8.0~repack-4:

jens@thing:~$ wine --version
wine-8.0 (Debian 8.0~repack-4)
jens@thing:~$ winetricks
Executing mkdir -p /home/jens
--
warning: You are using a 64-bit WINEPREFIX. Note that many verbs only 
install 32-bit versions of packages. If you encounter problems, please 
retest in a clean 32-bit WINEPREFIX before reporting a bug.

--
--
WINEPREFIX INFO:
Drive C: total 28
drwxr-xr-x  7 jens jens 4096 Feb 13 21:28 .
drwxr-xr-x  4 jens jens 4096 Feb 19 19:50 ..
drwxr-xr-x  3 jens jens 4096 Feb 13 21:28 ProgramData
drwxr-xr-x  6 jens jens 4096 Feb 13 21:28 Program Files
drwxr-xr-x  6 jens jens 4096 Feb 19 19:28 Program Files (x86)
drwxr-xr-x  4 jens jens 4096 Feb 13 21:28 users
drwxr-xr-x 21 jens jens 4096 Feb 19 19:28 windows

Registry info:
/home/jens/.wine/system.reg:#arch=win64
/home/jens/.wine/user.reg:#arch=win64
/home/jens/.wine/userdef.reg:#arch=win64
--
--
warning: wine cmd.exe /c echo '%AppData%' returned empty string, error 
message ""

--
jens@thing:~$ echo $?
1
jens@thing:~$ wine cmd.exe /c echo '%AppData%'
0098:err:winediag:is_broken_driver Broken NVIDIA RandR detected, falling 
back to RandR 1.0. Please consider using the Nouveau driver instead.
0034:err:winediag:is_broken_driver Broken NVIDIA RandR detected, falling 
back to RandR 1.0. Please consider using the Nouveau driver instead.

C:\users\jens\AppData\Roaming




Winetricks works with 8.0~repack-2:

jens@thing:~$ winetricks
Executing mkdir -p /home/jens
--
warning: You are using a 64-bit WINEPREFIX. Note that many verbs only 
install 32-bit versions of packages. If you encounter problems, please 
retest in a clean 32-bit WINEPREFIX before reporting a bug.

--
Using winetricks 20220411 - sha256sum: 
a4952b40c48d104eb4bcb5319743c95ae68b404661957a134974ae4e1dc79b34 with 
wine-8.0 (Debian 8.0~repack-2) and WINEARCH=win64

winetricks GUI enabled, using zenity 3.44.0






-- Package-specific info:
/usr/bin/wine points to /usr/bin/wine-stable.

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

Kernel: Linux 6.1.0-3-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages wine depends on:
ii  wine32  8.0~repack-4
ii  wine64  8.0~repack-4

wine recommends no packages.

Versions of packages wine suggests:
pn  dosbox
pn  exe-thumbnailer | kio-extras  
pn  playonlinux   
pn  q4wine
pn  winbind   
pn  wine-binfmt   
ii  winetricks20220411-1

Versions of packages libwine depends on:
ii  libasound2   1.2.8-1+b1
ii  libc62.36-8
ii  libcapi20-3  1:3.27-3+b1
ii  libfontconfig1   2.14.1-4
ii  libfreetype6 2.12.1+dfsg-4
ii  libglib2.0-0 2.74.5-1
ii  libgphoto2-6 2.5.30-1
ii  libgphoto2-port122.5.30-1
ii  libgstreamer-plugins-base1.0-0   1.22.0-3
ii  libgstreamer1.0-01.22.0-2
ii  libpcap0.8   1.10.3-1
ii  libpulse016.1+dfsg1-2+b1
ii  libudev1 252.5-2
ii  libunwind8   1.6.2-3
ii  libusb-1.0-0 2:1.0.26-1
ii  libx11-6 2:1.8.3-3
ii  libxext6 2:1.3.4-1+b1
ii  libz-mingw-w64   1.2.13+dfsg-1
ii  ocl-icd-libopencl1 [libopencl1]  2.3.1-1

Versions of packages libwine recommends:
ii  fonts-liberation   1:1.07.4-11
ii  fonts-wine 8.0~repack-4
ii  gstreamer1.0-plugins-good  1.22.0-4
ii  libasound2-plugins 1.2.7.1-1
ii  libcups2   2.4.2-1+b2
ii  libdbus-1-3