January 2026 - Wine-Devel - list.winehq.org

Re: Availability of wine-devel/wine-gitlab archives

by Austin English

On Sun, Jan 18, 2026 at 2:26 AM Dmitry Timoshkov via Wine-devel <wine-devel(a)list.winehq.org> wrote: > > Elizabeth Figura via Wine-devel <wine-devel(a)list.winehq.org> wrote: > > > > On 1/17/2026 1:26 PM, Dmitry Timoshkov via Wine-devel wrote: > > > > Elizabeth Figura <zfigura(a)codeweavers.com> wrote: > > > > > > > >> It seems the archives are all still there, but the domain was changed from www.winehq.org to list.winehq.org. Perhaps we could set up some forwards? > > > >> > > > >> FWIW all the mailman2 (pipermail) links do still exist as a read-only archive, up until the point when we transitioned to mailman3. > > > > While the archives seem to be there they can't be downloaded. For example > > > > from https://www.winehq.org/pipermail/wine-devel an attempt try to download > > > > archive for August 2022 fails: > > > > https://www.winehq.org/pipermail/wine-devel/2022-August.txt.gz > > > > While it's only 35Kb in size it stucks at 14.7 Kb for me. > > > > Archives for gitlab, for instance > > > > https://www.winehq.org/mailman3/hyperkitty/list/wine-gitlab@winehq.org/2022… > > > > can't be even browsed, and timeout for me. Do they work for you? > > > > Both of these links work fine for me (and I did test outside of any CW networks, just in case). > > Many thanks for the assistance! > > Do the following links also work for you? They hang for me after initial small chunk: > > https://www.winehq.org/pipermail/wine-devel/2022-June.txt.gz > https://www.winehq.org/mailman3/hyperkitty/list/wine-gitlab@winehq.org/expo… > > -- > Dmitry. Both work for me: $ du -sh Downloads/*gz 4.2M Downloads/2022-June.txt.gz 3.0M Downloads/wine-gitlab(a)winehq.org-2024-09.mbox.gz -- -Austin GPG: 267B CC1F 053F 0749 (expires 2026-03-03)

Jan. 18, 2026

Re: Availability of wine-devel/wine-gitlab archives

by Dmitry Timoshkov

Elizabeth Figura via Wine-devel <wine-devel(a)list.winehq.org> wrote: > > On 1/17/2026 1:26 PM, Dmitry Timoshkov via Wine-devel wrote: > > > Elizabeth Figura <zfigura(a)codeweavers.com> wrote: > > > > > >> It seems the archives are all still there, but the domain was changed from www.winehq.org to list.winehq.org. Perhaps we could set up some forwards? > > >> > > >> FWIW all the mailman2 (pipermail) links do still exist as a read-only archive, up until the point when we transitioned to mailman3. > > > While the archives seem to be there they can't be downloaded. For example > > > from https://www.winehq.org/pipermail/wine-devel an attempt try to download > > > archive for August 2022 fails: > > > https://www.winehq.org/pipermail/wine-devel/2022-August.txt.gz > > > While it's only 35Kb in size it stucks at 14.7 Kb for me. > > > Archives for gitlab, for instance > > > https://www.winehq.org/mailman3/hyperkitty/list/wine-gitlab@winehq.org/2022… > > > can't be even browsed, and timeout for me. Do they work for you? > > Both of these links work fine for me (and I did test outside of any CW networks, just in case). Many thanks for the assistance! Do the following links also work for you? They hang for me after initial small chunk: https://www.winehq.org/pipermail/wine-devel/2022-June.txt.gz https://www.winehq.org/mailman3/hyperkitty/list/wine-gitlab@winehq.org/expo… -- Dmitry.

Jan. 18, 2026

Re: Availability of wine-devel/wine-gitlab archives

by Elizabeth Figura

On Saturday, 17 January 2026 14:20:26 CST Jeremy Newman via Wine-devel wrote: > The old pipermail archives are provided as is. If you cannot access or > download them, that is between you and your ISP. I've not had any issues > loading them myself. > > The new mailman3 list archives are here: > https://list.winehq.org/archives/list/wine-devel@list.winehq.org/ > > I've updated the old mailman3 redirects on www.winehq.org so that they > go to the correct place. We never did that after the lists moved to the > new list.winehq.org home. Works now, thank you! > On 1/17/2026 1:26 PM, Dmitry Timoshkov via Wine-devel wrote: > > Elizabeth Figura <zfigura(a)codeweavers.com> wrote: > > > >> It seems the archives are all still there, but the domain was changed from www.winehq.org to list.winehq.org. Perhaps we could set up some forwards? > >> > >> FWIW all the mailman2 (pipermail) links do still exist as a read-only archive, up until the point when we transitioned to mailman3. > > While the archives seem to be there they can't be downloaded. For example > > from https://www.winehq.org/pipermail/wine-devel an attempt try to download > > archive for August 2022 fails: > > https://www.winehq.org/pipermail/wine-devel/2022-August.txt.gz > > While it's only 35Kb in size it stucks at 14.7 Kb for me. > > Archives for gitlab, for instance > > https://www.winehq.org/mailman3/hyperkitty/list/wine-gitlab@winehq.org/2022… > > can't be even browsed, and timeout for me. Do they work for you? Both of these links work fine for me (and I did test outside of any CW networks, just in case).

Jan. 17, 2026

Re: Availability of wine-devel/wine-gitlab archives

by Dmitry Timoshkov

Hi Jeremy, thanks for looking at this. Jeremy Newman via Wine-devel <wine-devel(a)list.winehq.org> wrote: > The old pipermail archives are provided as is. If you cannot access or > download them, that is between you and your ISP. I've not had any issues > loading them myself. It seems that I'm not the only one who can't download archives, it looks like archive.org has the problem archiving them too since the archives are missing there. > The new mailman3 list archives are here: > https://list.winehq.org/archives/list/wine-devel@list.winehq.org/ > > I've updated the old mailman3 redirects on www.winehq.org so that they > go to the correct place. We never did that after the lists moved to the > new list.winehq.org home. Thanks. -- Dmitry.

Jan. 17, 2026

Re: Availability of wine-devel/wine-gitlab archives

by Jeremy Newman

The old pipermail archives are provided as is. If you cannot access or download them, that is between you and your ISP. I've not had any issues loading them myself. The new mailman3 list archives are here: https://list.winehq.org/archives/list/wine-devel@list.winehq.org/ I've updated the old mailman3 redirects on www.winehq.org so that they go to the correct place. We never did that after the lists moved to the new list.winehq.org home. On 1/17/2026 1:26 PM, Dmitry Timoshkov via Wine-devel wrote: > Elizabeth Figura <zfigura(a)codeweavers.com> wrote: > >> It seems the archives are all still there, but the domain was changed from www.winehq.org to list.winehq.org. Perhaps we could set up some forwards? >> >> FWIW all the mailman2 (pipermail) links do still exist as a read-only archive, up until the point when we transitioned to mailman3. > While the archives seem to be there they can't be downloaded. For example > from https://www.winehq.org/pipermail/wine-devel an attempt try to download > archive for August 2022 fails: > https://www.winehq.org/pipermail/wine-devel/2022-August.txt.gz > While it's only 35Kb in size it stucks at 14.7 Kb for me. > Archives for gitlab, for instance > https://www.winehq.org/mailman3/hyperkitty/list/wine-gitlab@winehq.org/2022… > can't be even browsed, and timeout for me. Do they work for you? > > -- > Dmitry. -- CodeWeavers, Inc. 🐉 Jeremy Newman ⛭ Director of IT ────────────────────────────────────────────────────── 📧 jnewman(a)codeweavers.com 🌐 https://www.codeweavers.com/about/people/jnewman

Jan. 17, 2026

Re: Availability of wine-devel/wine-gitlab archives

by Dmitry Timoshkov

Elizabeth Figura <zfigura(a)codeweavers.com> wrote: > It seems the archives are all still there, but the domain was changed from www.winehq.org to list.winehq.org. Perhaps we could set up some forwards? > > FWIW all the mailman2 (pipermail) links do still exist as a read-only archive, up until the point when we transitioned to mailman3. While the archives seem to be there they can't be downloaded. For example from https://www.winehq.org/pipermail/wine-devel an attempt try to download archive for August 2022 fails: https://www.winehq.org/pipermail/wine-devel/2022-August.txt.gz While it's only 35Kb in size it stucks at 14.7 Kb for me. Archives for gitlab, for instance https://www.winehq.org/mailman3/hyperkitty/list/wine-gitlab@winehq.org/2022… can't be even browsed, and timeout for me. Do they work for you? -- Dmitry.

Jan. 17, 2026

Re: Availability of wine-devel/wine-gitlab archives

by Elizabeth Figura

On Saturday, 17 January 2026 09:15:20 CST Dmitry Timoshkov via Wine-devel wrote: > > Hi all, > > recently I tried to lookup some previously discussed things in wine-devel > archives and was surprised that neither winehq.org nor archive.org provide > something useful, all the links I tried don't work. The things get a bit > more complex due to transition from pipermail to hyperkitty and current > system. Is it possible to make old archives available again and fix access > to current wine-devel/wine-gitlab archives? It seems the archives are all still there, but the domain was changed from www.winehq.org to list.winehq.org. Perhaps we could set up some forwards? FWIW all the mailman2 (pipermail) links do still exist as a read-only archive, up until the point when we transitioned to mailman3. --Zeb

Jan. 17, 2026

Availability of wine-devel/wine-gitlab archives

by Dmitry Timoshkov

Hi all, recently I tried to lookup some previously discussed things in wine-devel archives and was surprised that neither winehq.org nor archive.org provide something useful, all the links I tried don't work. The things get a bit more complex due to transition from pipermail to hyperkitty and current system. Is it possible to make old archives available again and fix access to current wine-devel/wine-gitlab archives? Thanks. -- Dmitry.

Jan. 17, 2026

Unixlib support for non-Wine binaries? (Or: would upstream Wine take a Spout2 to PipeWire bridge?)

by Hoshino Lina

Hi! I'm working on a tool to bridge Spout2 [1][2] to PipeWire. Spout2 is a windows-only frame-sharing technology widely used for video-streaming and mixing apps. It allows one app to send video to another, much like JACK does for audio on Linux (and now PipeWire for both A/V). For example, the majority of the VTubing/streaming world relies on Spout2 to stream avatars and graphics on screen. To make this work, the bridge needs to use unixlib to do the bridging between the Windows and Linux worlds. I got it to build outside the Wine source tree by using just a few headers outside the public wine headers (unixlib.h, server.h, server_protocol.h). Originally I intended to distribute it as a simple installable that users could throw into their WINEPREFIX, but it turned out that for unixlib to work, the exe needs to be marked as builtin and distributed as a Wine builtin exe in wine/x86_64-windows with the .so file in the companion x86_64-unix directory. - Would it make sense for Wine to change its unixlib loading code to work with non-builtin binaries, such as looking for the .so in the same directory as the .dll/.exe? - Otherwise, would upstream Wine be interested in merging this feature? The main dependencies are PipeWire and libfunnel [3]. The app does rely on some Wine/DXVK internals (unixlib, KeUserDispatchCallback, \??\SharedGpuResource, ProcessWineMakeProcessSystem) but it's not strictly necessary for those to remain stable across all future Wine releases, as making updates to stay compatible is not a major issue. At this time I plan to distribute it as a "patch" that can be applied to Proton installations (which just drops in the exe/so and adds it to wine.ini). Another option is using WINEDLLPATH, which should work for regular Wine (this one is problematic on Proton since the Proton launcher unconditionally clobbers that environment variable). One potential issue is that due to the less than ideal design of Spout2, there is no way to know when apps start using Spout2 other than polling for the existence of a named shared memory segment. So if this is merged unconditionally, the service would have to always run even if not needed, unless some kind of hack is added to `CreateFileMappingA` to watch for the "SpoutSenderNames" mapping and launch the service on demand when it is created. On top of that, once PipeWire -> Spout2 support is added, it would mean the daemon is bridging every possible PipeWire stream to Spout2 as soon as any Spout2 app runs regardless of whether any Spout2 consumer exists for it. The only way I can think of avoiding this (other than manual config) is, again, some kind of Wine hook that only triggers the bridge for a stream when some Spout2 consumer app has the specific stream shared memory and/or mutex opened to a handle... it really isn't a well designed protocol, unfortunately, but it is what is in use on Windows. [1] https://spout.zeal.co/ [2] https://github.com/leadedge/Spout2 [3] https://github.com/hoshinolina/libfunnel ~~ Lina

Jan. 17, 2026

Upcoming vkd3d 1.19 release

by Henri Verbeet

Hi all, The planned release date for vkd3d 1.19 is Thursday February 19. That means the public API will become frozen next week on January 22, and features will be frozen two weeks before the release, on February 5. This does not mean that development should slow down or stop, of course; after making sure that we're in good shape to release, this would be the ideal time to make sure that any larger features are ready to get merged at the start of the next development cycle. As usual, if you're an upstream vkd3d developer, please do the following: - Keep an eye on Bugzilla for any reported regressions. - Review any API changes since the previous release. - Verify that all vkd3d tests pass on your hardware/setup, and please send fixes if they don't. - Review and improve the documentation. - Get any larger features ready to get merged at the start of the next development cycle. If you're a downstream user of vkd3d, please test your applications for any regressions, and file bug reports if you find any. The planned release date for vkd3d 2.0 is Thursday May 21. A tentative release schedule for future releases can be found on the vkd3d wiki[1]. Regards, Henri [1] https://gitlab.winehq.org/wine/vkd3d/-/wikis/release-schedule

Jan. 15, 2026