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!
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!
FS#66428 - [wine-mono] wine cannot find wine-mono when creating a new prefix
Attached to Project:
Community Packages
Opened by Edwin (edwin) - Sunday, 26 April 2020, 17:35 GMT
Last edited by freswa (frederik) - Tuesday, 28 July 2020, 19:32 GMT
Opened by Edwin (edwin) - Sunday, 26 April 2020, 17:35 GMT
Last edited by freswa (frederik) - Tuesday, 28 July 2020, 19:32 GMT
|
DetailsDescription:
When creating a new prefix, wine complains that it cannot find the wine-mono package and offer to download it, even though it is already installed. Cause: https://git.archlinux.org/svntogit/community.git/commit/trunk?h=packages/wine-mono&id=654cfc78c753486d3dae34114c3bf513ebce7c25 shows that the msi in /usr/share/wine/mono/ was renamed upstream from wine-mono-pkgver.msi to wine-mono-pkgver-x86.msi, but the PKGBUILD still installs it to the old location. Fix: Creating symlink wine-mono-5.0.0-x86.msi is sufficient to fix the issue. Additional info: *wine-5.7-1 *wine-mono-5.0.0-1 |
This task depends upon
Closed by freswa (frederik)
Tuesday, 28 July 2020, 19:32 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in 5.1.0-
Tuesday, 28 July 2020, 19:32 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in 5.1.0-
Still needed for wine-5.8-1