Package: wine Version: 4.0.2-1 Severity: normal I find needing to know about existence of msiexec /i, somehow painful, especially to wine newcomers.
I expect calling wine xyz.msi, to be equivalent to double clicking a msi file on Windows, aka launching installer automatically. Should be easy to support. At the moment wine just says: "wine: Bad EXE format for Z:\....\xyz.msi", which isn't helpful. -- Package-specific info: /usr/bin/wine points to /usr/bin/wine-stable. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-2-amd64 (SMP w/32 CPU cores) 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.UTF-8 (charmap=UTF-8) 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 4.0.2-1 ii wine64 4.0.2-1 wine recommends no packages. Versions of packages wine suggests: ii dosbox 0.74-3-1 ii exe-thumbnailer 0.10.0-3 pn playonlinux <none> pn q4wine <none> ii winbind 2:4.10.8+dfsg-1 pn wine-binfmt <none> ii winetricks 0.0+20190912-1 Versions of packages wine is related to: ii fonts-wine 4.0.2-1 ii wine 4.0.2-1 ii wine32 4.0.2-1 ii wine64 4.0.2-1 -- no debconf information
