# Announcing Swift 5.10.1 for Linux and Windows **URL:** \ **Category:** Announcements\ **Created:** [June 6, 2024, 6:58pm UTC](https://forums.swift.org/t/announcing-swift-5-10-1-for-linux-and-windows/72292 "2024-06-06T18:58:59Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![mishal\_shah](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/mishal_shah/32/247_2.png) [@mishal\_shah](https://forums.swift.org/u/mishal_shah)\ **Post date:** [June 6, 2024, 6:58pm UTC](https://forums.swift.org/t/announcing-swift-5-10-1-for-linux-and-windows/72292/1 "2024-06-06T18:58:59Z")
We are happy to announce the release of Swift 5.10.1 for Linux and Windows.New downloads are available on [Swift.org - Install Swift](https://www.swift.org/install) **Release Note** - New Linux platforms supported: - Ubuntu 23.10 (x86\_64 and AArch64) - Ubuntu 24.04 (x86\_64 and AArch64) - Debian 12 (x86\_64 and AArch64) - Fedora 39 (x86\_64 and AArch64) ---
**Author:** ![wadetregaskis](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/wadetregaskis/32/8494_2.png) [@wadetregaskis](https://forums.swift.org/u/wadetregaskis)\ **Post date:** [June 6, 2024, 7:13pm UTC](https://forums.swift.org/t/announcing-swift-5-10-1-for-linux-and-windows/72292/2 "2024-06-06T19:13:46Z")
It's good to see Debian now on the supported distros list, but it seems there's still no native support, merely tarballs and Docker images (as opposed to e.g. `apt install swiftlang`). Why is that? ---
**Author:** ![xtremekforever](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/xtremekforever/32/43018_2.png) [@xtremekforever](https://forums.swift.org/u/xtremekforever)\ **Post date:** [June 6, 2024, 8:30pm UTC](https://forums.swift.org/t/announcing-swift-5-10-1-for-linux-and-windows/72292/3 "2024-06-06T20:30:06Z")
It seems like it would be good to have (deb and rpms) but it’s actually not common to have programming tool chains packaged for distributions officially. Look at Go and Rust as examples. Instead, they are investing time into a Swift version manager called Swiftly. It’s awesome if you haven’t checked it out yet! [https://swift-server.github.io/swiftly/](https://swift-server.github.io/swiftly/) ---
**Author:** ![wadetregaskis](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/wadetregaskis/32/8494_2.png) [@wadetregaskis](https://forums.swift.org/u/wadetregaskis)\ **Post date:** [June 6, 2024, 9:13pm UTC](https://forums.swift.org/t/announcing-swift-5-10-1-for-linux-and-windows/72292/4 "2024-06-06T21:13:47Z")
> [@xtremekforever](#): > > It seems like it would be good to have (deb and rpms) but it’s actually not common to have programming tool chains packaged for distributions officially. Look at Go and Rust as examples. Instead, they are investing time into a Swift version manager called Swiftly. It’s awesome if you haven’t checked it out yet! > > [https://swift-server.github.io/swiftly/](https://swift-server.github.io/swiftly/) Hmm, it's all I've ever used, e.g. with Python. I'm aware of Swiftly, but it just extends the problem to now having yet _another_ tarball to manually manage. In my experience pretty much every Linux system has a robust, built-in way to essentially `apt update && apt upgrade` automatically, periodically. Having to build a bespoke setup just to keep Swift up to date is not great. ---
**Author:** ![xtremekforever](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/xtremekforever/32/43018_2.png) [@xtremekforever](https://forums.swift.org/u/xtremekforever)\ **Post date:** [June 6, 2024, 9:20pm UTC](https://forums.swift.org/t/announcing-swift-5-10-1-for-linux-and-windows/72292/5 "2024-06-06T21:20:03Z")
Well if you DO want deb packages for Swift, look no further than the Swift for ARM project. They are building for Debian and Ubuntu x86\_64 and arm64 as well. Not officially supported but works like a charm. [https://swift-arm.com/installSwift](https://swift-arm.com/installSwift) I somewhat doubt Apple will officially maintain their own repositories with deb and rpm packages, but that does not stop the community from doing this! 🙂 ---
**Author:** ![wadetregaskis](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/wadetregaskis/32/8494_2.png) [@wadetregaskis](https://forums.swift.org/u/wadetregaskis)\ **Post date:** [June 6, 2024, 9:24pm UTC](https://forums.swift.org/t/announcing-swift-5-10-1-for-linux-and-windows/72292/6 "2024-06-06T21:24:17Z")
Right, and that's what I use. It works great. The problem is, practically nobody new to Swift is going to use it because they have no reasonable way to know about it, since it's never mentioned on [swift.org](http://swift.org). It'd be great if the Swift-ARM community effort were highlighted on [swift.org](http://swift.org), and included in the 'how to install Swift' pages. ---
**Author:** ![dima\_kozhinov](https://avatars.discourse-cdn.com/v4/letter/d/258eb7/32.png) [@dima\_kozhinov](https://forums.swift.org/u/dima_kozhinov)\ **Post date:** [June 6, 2024, 10:34pm UTC](https://forums.swift.org/t/announcing-swift-5-10-1-for-linux-and-windows/72292/7 "2024-06-06T22:34:35Z")
> [@wadetregaskis](#): > > there's still no native support, merely tarballs and Docker images (as opposed to e.g. `apt install swiftlang`). Why is that? I think it's due to lack of cooperation between Swift developers and Linux distributions maintainers. Or lack of effort from Swift developers to create and propose proper packages for Linux distributions. For me personally, tarballs are OK (but Docker images are not). ---
**Author:** ![sspringer](https://avatars.discourse-cdn.com/v4/letter/s/e9c0ed/32.png) [@sspringer](https://forums.swift.org/u/sspringer)\ **Post date:** [June 7, 2024, 4:06am UTC](https://forums.swift.org/t/announcing-swift-5-10-1-for-linux-and-windows/72292/8 "2024-06-07T04:06:10Z")
At which point will Windows ARM be on the list of supported platforms and available on the download page? According to [this ticket](https://github.com/thebrowsercompany/swift-build/issues/33) ARM support seems to be “ready”. ---
**Author:** ![Finagolfin](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/finagolfin/32/34388_2.png) [@Finagolfin](https://forums.swift.org/u/Finagolfin)\ **Post date:** [June 7, 2024, 6:49am UTC](https://forums.swift.org/t/announcing-swift-5-10-1-for-linux-and-windows/72292/9 "2024-06-07T06:49:41Z")
> [@sspringer](#): > > At which point will Windows ARM be on the list of supported platforms and available on the download page? See @compnerd's [earlier answer to me](https://forums.swift.org/t/article-about-swift-on-windows/67513/10). After following your link, I see now that they have been putting out [unofficial Windows AArch64 trunk toolchain installers since last September](https://github.com/thebrowsercompany/swift-build/releases), including for [the 5.10 branch](https://github.com/thebrowsercompany/swift-build/releases/tag/swift-5.10.0-20240426.0). I suggest you try those out and report any problems you find to them. ---
**Author:** ![0xTim](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/0xtim/32/27968_2.png) [@0xTim](https://forums.swift.org/u/0xTim)\ **Post date:** [June 7, 2024, 11:58am UTC](https://forums.swift.org/t/announcing-swift-5-10-1-for-linux-and-windows/72292/10 "2024-06-07T11:58:46Z")
> > > …ots (main) branch > > \Screenshot 2024-06-07 at 12 07 29 AM… ---
**Author:** ![xtremekforever](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/xtremekforever/32/43018_2.png) [@xtremekforever](https://forums.swift.org/u/xtremekforever)\ **Post date:** [June 7, 2024, 12:18pm UTC](https://forums.swift.org/t/announcing-swift-5-10-1-for-linux-and-windows/72292/11 "2024-06-07T12:18:45Z")
I agree, that would be nice. Maybe something that can happen in the future as part of the platform steering group work. ---
**Author:** ![SimplyDanny](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/simplydanny/32/25114_2.png) [@SimplyDanny](https://forums.swift.org/u/SimplyDanny)\ **Post date:** [July 5, 2024, 8:34am UTC](https://forums.swift.org/t/announcing-swift-5-10-1-for-linux-and-windows/72292/12 "2024-07-05T08:34:39Z")
How can I know which version of CoreFoundation is included in the 5.10.1 release? ---
**Author:** ![Finagolfin](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/finagolfin/32/34388_2.png) [@Finagolfin](https://forums.swift.org/u/Finagolfin)\ **Post date:** [July 5, 2024, 9:20am UTC](https://forums.swift.org/t/announcing-swift-5-10-1-for-linux-and-windows/72292/13 "2024-07-05T09:20:09Z")
The `swift-corelibs-foundation` repo used in the linux/Windows OSS toolchains but not on macOS is open source, so you can look in [the 5.10 commit log for that info](https://github.com/apple/swift-corelibs-foundation/commits/release/5.10/CoreFoundation). Scrolling through and looking for large merge commits, I see [this giant Monterey merge commit](https://github.com/apple/swift-corelibs-foundation/commit/512e4121415677c9c85b69eac5a2109815243861) on the second page, from three years ago. ---
**Author:** ![SimplyDanny](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/simplydanny/32/25114_2.png) [@SimplyDanny](https://forums.swift.org/u/SimplyDanny)\ **Post date:** [July 5, 2024, 9:32am UTC](https://forums.swift.org/t/announcing-swift-5-10-1-for-linux-and-windows/72292/14 "2024-07-05T09:32:31Z")
I'm interested in Linux actually. I thought that the swift-corelibs-foundation 5.10.1 release would be contained in Swift 5.10.1, but that doesn't seem to be the case. Now I wonder how the update cycle works there. ---
**Author:** ![Finagolfin](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/finagolfin/32/34388_2.png) [@Finagolfin](https://forums.swift.org/u/Finagolfin)\ **Post date:** [July 5, 2024, 9:38am UTC](https://forums.swift.org/t/announcing-swift-5-10-1-for-linux-and-windows/72292/15 "2024-07-05T09:38:57Z")
It should be: you're saying the released 5.10.1 library in some official linux toolchain was not built from [this source tag](https://github.com/apple/swift-corelibs-foundation/releases/tag/swift-5.10.1-RELEASE)? ---
**Author:** ![SimplyDanny](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/simplydanny/32/25114_2.png) [@SimplyDanny](https://forums.swift.org/u/SimplyDanny)\ **Post date:** [July 5, 2024, 7:16pm UTC](https://forums.swift.org/t/announcing-swift-5-10-1-for-linux-and-windows/72292/16 "2024-07-05T19:16:57Z")
I use the Swift 5.10.1 Docker image and try to compile the code ```swift await URLSession.shared.data(for: request) ``` in a CI environment. Async methods on `URLSession` were added only recently, but should be part of the 5.10.1 tag. Yet, the compiler complains like `error: value of type 'URLSession' has no member 'data'`. So I assume this code isn’t part of the toolchain. So far it isn’t obvious to me where to find what’s actually included. ---
**Author:** ![etcwilde](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/etcwilde/32/13687_2.png) [@etcwilde](https://forums.swift.org/u/etcwilde)\ **Post date:** [July 5, 2024, 7:56pm UTC](https://forums.swift.org/t/announcing-swift-5-10-1-for-linux-and-windows/72292/17 "2024-07-05T19:56:43Z")
As far as I can tell, the patches for adding the async data were never a part of 5.10. 5.10.1 is a patch release on 5.10, so it doesn't contain new feature work, just bug fixes on the existing functionality. It should be in 6.0 and main though. > > > Thanks to @b1ackturtle for providing the foundation of this work in #4705! > > T…his PR implements the remaining async \`URLSession\` methods and the \`URLSessionTask.delegate\` property, allowing a delegate to be set in the async methods (or in a non-async context before resumption). \`URLSessionTask.delegate\` returns the explicitly set delegate if present, otherwise returns the session delegate \`as? URLSessionTaskDelegate\`. It's now used wherever we previously casted the session delegate to \`URLSessionTaskDelegate\`. To accompany this change, functions in \`extension URLSessionTaskDelegate\` (which are called if not implemented by the task's delegate) now check if the session's delegate implements it and call the session's delegate if that's the case. > > > Cherry-pick of #4970 for \`release/6.0\` ---
**Author:** ![Finagolfin](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/finagolfin/32/34388_2.png) [@Finagolfin](https://forums.swift.org/u/Finagolfin)\ **Post date:** [July 7, 2024, 12:13pm UTC](https://forums.swift.org/t/announcing-swift-5-10-1-for-linux-and-windows/72292/18 "2024-07-07T12:13:57Z")
[Official trunk snapshot toolchains for Windows arm64 were just added a couple days ago](https://www.swift.org/install/windows/), try it out and report any problems you run into. ---
**Author:** ![SteveM](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/stevem/32/24870_2.png) [@SteveM](https://forums.swift.org/u/SteveM)\ **Post date:** [September 24, 2024, 11:35pm UTC](https://forums.swift.org/t/announcing-swift-5-10-1-for-linux-and-windows/72292/19 "2024-09-24T23:35:06Z")
You can blame me to a certain extent. Debian has a very large and complex set of policies for packages governing all manner of things and no package is allowed in until they are approved. For example, every single file in the package must be listed in debian/copyright with the appropriate attribution, if Debian ships with a library or tool then it must be used instead of the Swift provided version (eg. Ninja, icu, yaml). And then how to get around the problem that a long time ago someone else added a package to Debian with a binary named "swift"? None of these are issues for people cranking out .deb files for you to install. At any rate, in early 2019 someone first made the request to add Swift to Debian but it sat there for about 4 years. Then I picked it up and after many months of effort I finally got 5.6.3 into Debian unstable and testing. 5.6.3 was the latest version available when I started my work. Somewhere along the way someone updated glibc and I didn't notice that Swift was FTBFS as a result so a month later Swift was kicked out of Debian testing. I've since managed to package 5.7.3 and it is now available in unstable and testing. I've been working on 5.8.3, but am getting some very odd compile errors that I've yet to resolve. I'm only one guy working in my spare time so when I can't find a ready answer or others don't have any suggestions to help me the effort stalls out till I have a day or two free to dig into it. You might be thinking why not jump all the way up to 6.0 and get that in before the Debian 13 freeze. That would be great, but it means building 6.0 with Swift 5.7.3 or doing some bootstrapping, neither of which is supported or guaranteed to work. I'd love for Debian to be on the latest version, but I lack the free time to work through the compile issues that each new version presents in a timely fashion. All of this work is being done in the open so anyone is free to help out. The repo containing the Debian build files is here: [pkg-llvm / swiftlang · GitLab](https://salsa.debian.org/pkg-llvm-team/swiftlang) I have a 5.8 development branch, but I don't think I've pushed to it yet as I've been working alone and don't push builds that don't work. Anyone can clone this repo and hack away at it, just don't forget to mind Debian policies. ---
**Author:** ![Finagolfin](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/finagolfin/32/34388_2.png) [@Finagolfin](https://forums.swift.org/u/Finagolfin)\ **Post date:** [January 5, 2026, 10:05am UTC](https://forums.swift.org/t/announcing-swift-5-10-1-for-linux-and-windows/72292/20 "2026-01-05T10:05:31Z")
How is this going now, @SteveM? I notice that [you have it up to 6.1.3](https://git.launchpad.net/ubuntu/+source/swiftlang), anything holding up 6.2.3, other than lack of your time? It would be good to [get the Swift packages in distros up to date](https://repology.org/project/swift-lang/versions), let us know what else needs to be done. [Next page](https://forums.swift.org/t/announcing-swift-5-10-1-for-linux-and-windows/72292.md?page=2)