Bug 647970 – app-emulation/wine-staging new SRC_URI HOMEPAGE in forked project

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description jospezial 2018-02-17 23:59:16 UTC]

https://wine-staging.com/news/2018-02-17-future-wine-staging.html

"Overall, our available spare time decreased to a level that we can no longer maintain Wine Staging in the same quality as we did before (rebasing patches, reviewing new ones, testing applications before each release, etc.). We therefore decided that it is currently not possible for us to provide new releases. Sorry for keeping you guys waiting for so long, but as you can imagine, suspending the project was not an easy decision as we know that many users depend on it."

"There are also attempts by other Wine developers to keep Wine Staging alive, for example this fork, which you might want to look into."

"this fork" = https://github.com/wine-staging/wine-staging

[Comment 1 Sebastian Schreier 2018-03-02 17:42:42 UTC]

I posted a small workaround for everyone who can wait ;-)
https://forums.gentoo.org/viewtopic-p-8190930.html#8190930

[Comment 2 Sebastian Schreier 2018-03-02 17:56:06 UTC]

Created attachment 521966 [details, diff]
patch for wine-staging-9999

[Comment 3 Adam Feldman 2018-03-02 18:01:35 UTC]

I certainly can update the URIs, but I don't really know at this point the level of upstream support I'll have.  I can't vouch for things working as is right now.  Like, what happens if CSMT is enabled in staging and in wine itself?

I've been holding off until I could do some assessments.  I can certainly go ahead and do it now, but then I have to say that it's totally unsupported at this time too.

[Comment 4 tt_1 2018-03-02 18:04:33 UTC]

You could edit the src_uri for the live ebuild only, for testing.

[Comment 5 Markus 2018-03-04 07:19:11 UTC]

First (stable?) release (3.3) in fork:
https://github.com/wine-staging/wine-staging/releases/tag/v3.3

[Comment 6 Rodrigo Saboya 2018-03-20 18:47:55 UTC]

I think the support is there for now. It's being maintained by people connected to Wine development.

https://www.winehq.org/pipermail/wine-devel/2018-February/123080.html

[Comment 7 Maxime Lombard 2018-04-01 17:41:36 UTC]

Created attachment 526266 [details, diff]
Ebuild for wine-staging 3.5

(In reply to NP-Hardass from comment #3)
> I certainly can update the URIs, but I don't really know at this point the
> level of upstream support I'll have.  I can't vouch for things working as is
> right now.  Like, what happens if CSMT is enabled in staging and in wine
> itself?
> 
> I've been holding off until I could do some assessments.  I can certainly go
> ahead and do it now, but then I have to say that it's totally unsupported at
> this time too.

Wine-Staging is updated all days to follow wine-git and the official release. If Wine team decide to enable cmst so Staging team will disable their patches. It was the case when vulkan was implemented officially in Wine, Staging team disable their Vulkan patches to avoid conflict.

I share you my ebuild and patch (from wine-staging 2.21) for wine-staging 3.5 released yesterday. The changes are the following compared to the wine-2.21 ebuild :
- Modify the links for Staging Git and archive.
- Add support for Vulkan (implemented in Wine 3.4) -> media-libs/vulkan-loader
- Disable the patch for manpage since it fail to patch.
- Disable Pipelight since it's deprecated and discontinued since early 1 year ago.
- Disable winhlp32-Flex_Workaround since the patch is implemented in flex 2.6.4 which in stable now on Gentoo.
- Disable tests during compilation. It's not necessary for a simple user like us.

The ebuild works, i used it in my local overlay to install the latest version of Staging.

[Comment 8 Maxime Lombard 2018-04-01 17:43:24 UTC]

Created attachment 526268 [details, diff]
Patch for wine-staging 3.5 from wine-staging 2.21

[Comment 9 Maxime Lombard 2018-04-01 17:43:51 UTC]

Created attachment 526270 [details]
Ebuild for wine-staging 3.5

[Comment 10 Nick Sarnie 2018-04-27 02:39:57 UTC]

Hi all,

I am going to version bump wine-staging this weekend, which will include switching over to the new upstream repository.

Thanks,
Sarnex

[Comment 11 Larry the Git Cow 2018-04-30 03:05:29 UTC]

The bug has been closed via the following commit(s):

https://gitweb.gentoo.org/repo/proj/wine.git/commit/?id=9e401d55ad21d461c115e8b092d402b79678573d

commit 9e401d55ad21d461c115e8b092d402b79678573d
Author:     Nick Sarnie <[e-mail]>
AuthorDate: 2018-04-30 02:36:03 +0000
Commit:     Nick Sarnie <[e-mail]>
CommitDate: 2018-04-30 02:59:23 +0000

    app-emulation/wine-staging: Bump to 3.3
    
    There were no staging releases between 2.21 and 3.3 exclusive
    
    Closes: https://bugs.gentoo.org/647970
    Package-Manager: Portage-2.3.31, Repoman-2.3.9

 app-emulation/wine-staging/Manifest                |   2 +
 app-emulation/wine-staging/wine-staging-3.3.ebuild | 608 +++++++++++++++++++++
 2 files changed, 610 insertions(+)

Additionally, it has been referenced in the following commit(s):

https://gitweb.gentoo.org/repo/proj/wine.git/commit/?id=616353a10a8262f8ee125b306d4429680aaae20a

commit 616353a10a8262f8ee125b306d4429680aaae20a
Author:     Nick Sarnie <[e-mail]>
AuthorDate: 2018-04-30 02:19:27 +0000
Commit:     Nick Sarnie <[e-mail]>
CommitDate: 2018-04-30 02:56:13 +0000

    app-emulation/wine-staging: Updates for 9999
    
    - Added sdl USE
    - Updated upstream SRC_URI to point to the active fork
    - Removed unneeded patch exclusion as the patch was dropped upstream
    
    Bug: https://bugs.gentoo.org/647970
    
    Package-Manager: Portage-2.3.31, Repoman-2.3.9

 app-emulation/wine-staging/metadata.xml             | 1 +
 app-emulation/wine-staging/wine-staging-9999.ebuild | 9 +++++----
 2 files changed, 6 insertions(+), 4 deletions(-)}