I would recommend that you make strides towards backporting vkd3d-1.2 aswell,
since wine-6.0 would require this to build with d3d12 support. Currently this
is only available in debian experimental, and is currently (imo) not being
built correctly as libvkd3d-dev is not multilib installable due
On Sun, Mar 07, 2021 at 09:32:32PM -0500, Michael Gilbert wrote:
> On Thu, Feb 25, 2021 at 8:22 AM Sean Ho wrote:
> > it would be nice if maintainers make efforts to let wine-5.0 to
> > buster-backports first.
>
> Jens Reyer was solely responsible for wine's backports for a very long
> time.
Michael,
I'm interested to maintain the backport version of wine for Bullseye. I no
need to have the latest version of Wine for my game so my laptop will be on
Debian Stable after freeze.
My sources.list is already configured to use "bullseye" instead of
"testing".
Maxime
On Thu, Feb 25, 2021 at 8:22 AM Sean Ho wrote:
> it would be nice if maintainers make efforts to let wine-5.0 to
> buster-backports first.
Jens Reyer was solely responsible for wine's backports for a very long
time. Since he has stepped back, there is no one currently pursuing
this.
> If
On Mon, Feb 22, 2021 at 7:34 AM Maxime Lombard wrote:
> Do you think, after the freeze, to work on Wine-Staging at same time
> than Wine-development ?
I am willing to potentially sponsor someone else working on such a
thing but can't commit to maintaining it myself.
> I already try with
> Well, it would be nice if it were that simple ;)
> But to be able to ship WINE 6.0 with Debian Bullseye, it would have
needed to be included in Sid some time ago already. There simply is not
enough time to include WINE 6.0 and check it integrates well with Buster
with no side-effect, and still
Hi Michael,
Do you think, after the freeze, to work on Wine-Staging at same time
than Wine-development ?
I already try with wine-development-5.6 and i did some changes.
This idea is to use wine-development as base, applied all Staging
patchset and finally refresh debian/*
Wine-Staging on salsa
On Sun, Feb 7, 2021 at 4:34 PM Maxime Lombard wrote:
> No objection but why do not ship Wine-6.0 as stable version for
> Bullseye instead of 5.0 ?
Because milestone 1 in the freeze policy [0] requires no
large/disruptive changes.
Best wishes,
Mike
[0]
Le 09/02/2021 à 21:58, Sveinar Søpler a écrit :
I would say i agree with the plans of not focusing on wine-devel. I think
it would be a shame not to ship wine-6.0 as the stable version tho.
Well, it would be nice if it were that simple ;)
But to be able to ship WINE 6.0 with Debian Bullseye,
I would say i agree with the plans of not focusing on wine-devel. I think
it would be a shame not to ship wine-6.0 as the stable version tho.
Sveinar Søpler
- On Feb 7, 2021, at 10:34 PM, Berillions berilli...@gmail.com wrote:
> Hi,
>
> No objection but why do not ship Wine-6.0 as stable
Hi,
No objection but why do not ship Wine-6.0 as stable version for
Bullseye instead of 5.0 ?
Because as Phil explained in another mail, wine-6.0 release date is
after the 1st freeze date ?
Sorry for these questions, it's new for me.
But it would be a shame to have an old stable version in
Given some of the discussion on this list recently, it seems there is
a need for plans to be clarified.
My intent is for wine-development to no longer ship in stable
releases. I don't see the value of a mid-cycle version of wine to be
in debian stable any more. It made sense when the time
12 matches
Mail list logo
