Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#44462 - [wine] Existing patch from wine upstream sources not incorporated into Arch wine package

Attached to Project: Community Packages
Opened by Kevin (Gamonics) - Saturday, 04 April 2015, 14:41 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Sunday, 05 April 2015, 04:44 GMT
Task Type Feature Request
Category Packages: Multilib
Status Closed
Assigned To Florian Pritz (bluewind)
Sven-Hendrik Haase (Svenstaro)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

Visual Studio .NET 2003 Academic edition will apparently run in wine if this patch is applied to current sources:

https://github.com/wine-compholio/wine-staging/tree/master/patches/kernel32-NeedCurrentDirectoryForExePath

from Comment 41 at upstream bug tracker:
https://bugs.winehq.org/show_bug.cgi?id=8439

" Anastasius Focht 2015-01-24 05:14:36 CST

Hello folks,

same procedure as every year.
Still present.

$ wine --version
wine-1.7.34-159-g7b45103

Fortunately Wine-staging project cared about this here: https://github.com/wine-compholio/wine-staging/tree/master/patches/kernel32-NeedCurrentDirectoryForExePath

It allows all VS.NET 200x installers to find and run their sub-installers.

Chances improved to have this fixed in upstream before the 10th anniversary happens.

Regards"

This bug was apparently first reported upstream 7 years ago but for some reason still has not yet been incorporated into upstream sources.

Steps to reproduce:

1. Install the following Arch packages:
community/wine-mono 4.5.6-1
community/winetricks 20141130-1
multilib/q4wine 1.1_r2-1
multilib/wine 1.7.40-1
multilib/wine_gecko 2.36-1

2. Run WINEARCH=win32 winecfg to build a new wine prefix

3. Run winetricks dotnet11

4. Run wine /mnt/setup.exe with proprietary software from Microsoft (Visual Studio .NET 2003 Academic Prerequisites CDROM) mounted at /mnt. I can make this iso available to someone who needs to confirm this problem but of course I cannot make it generally available due to the potential for infringing the owner's copyright. This completes Step 1 (Visual Studio .NET Prerequisites) and enables Step 2 of the 4 step installation process for Visual Studio .NET 2003 Academic edition.

5. Run wine /mnt/setup.exe with proprietary software from Microsoft (Visual Studio .NET 2003 Academic Disc 1 CDROM) mounted at /mnt. I can make this iso available to someone who needs to confirm this problem but of course I cannot make it generally available due to the potential for infringing the owner's copyright. This results in an installation window opening that indicates Step 1 is complete and Step 2 is ready for completion.

6. Click "Visual Studio .NET" to the right of the big "2".

7. Wait 5-10 seconds and this installation window disappears and the setup.exe program crashes silently.
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Sunday, 05 April 2015, 04:44 GMT
Reason for closing:  Won't implement
Comment by Kevin (Gamonics) - Saturday, 04 April 2015, 15:57 GMT
Rereading this, I feel a need to explain that I don't want to install Visual Studio .NET 2003 in Arch/wine for its own sake or for my sake. Personally, I would use free tools for any development I wanted to do. But I think Visual Studio .NET 2003 will give me access to many of the Visual FoxPro runtimes and DLLs that I need for another proprietary software product that will enable a client to use that product in Arch instead of their current solution of running it in a Windows OS.
Comment by Doug Newgard (Scimmia) - Sunday, 05 April 2015, 03:53 GMT
Arch very rarely (read almost never) incorporates feature patches that haven't been accepted upstream. I think you'll need to make a very clear case on why this feature is critical.
Comment by Sven-Hendrik Haase (Svenstaro) - Sunday, 05 April 2015, 03:55 GMT
Unless you can explain to me why I this is relevant to most users, I think this is a better case for making your own package in AUR.
Comment by Kevin (Gamonics) - Sunday, 05 April 2015, 04:24 GMT
Sorry, I just noticed existence of the wine-staging package from the AUR. I'm building that now. What I'd most prefer is to have just this one patch applied; not everything in wine-staging. I've spent the day today learning about all the modifications I'll need to make to my arch system to allow me to build 32-bit applications, so building it myself with just this one patch applied won't happen tonight anyway. So maybe the wine-staging package will allow me to install Visual Studio .NET 2003. If so then I'll close this feature request.
Comment by Sven-Hendrik Haase (Svenstaro) - Sunday, 05 April 2015, 04:25 GMT
In order to build 32-bit stuff like wine, all you need to do is pacman -S devtools and then type extra-i686-build or multilib-build, it's not that hard.
Comment by Kevin (Gamonics) - Sunday, 05 April 2015, 04:27 GMT
Really!? That's not the impression I had from https://wiki.archlinux.org/index.php/64-bit_FAQ#Can_I_build_32-bit_packages_for_i686_inside_Arch64.3F

Well I'll try that next if the wine-staging package doesn't solve the problem for me.
Comment by Sven-Hendrik Haase (Svenstaro) - Sunday, 05 April 2015, 04:28 GMT
In all honesty, that page should be deleted. It's 8 years outdated or something.

Loading...