macOS 5.1.0 build not available on FOSSHUB

[Piccirello]

qBittorrent & operating system versions

qBittorrent 5.1.0 on macOS

What is the problem?

FOSSHUB is still hosting the 5.0.5 binary for macOS, while 5.1.0 is available for Windows and AppImage.

[xavier2k6]

There nearly has always been some delay in providing macOS builds, it's expected at this stage.........(not well supported & even a few of us @qbittorrent/bug-handlers have suggested to stop releasing builds for macOS.)

---

macOS builds will be available on a later date.

https://www.qbittorrent.org/news#sun-apr-27th-2025---qbittorrent-v5.1.0-release

NOTICE: macOS builds will be available later.

https://www.qbittorrent.org/news#tue-dec-17th-2024---qbittorrent-v5.0.3-and-v5.1.0beta1-releases

The macOS version is not well supported, because we don't have active macOS developers/contributors. The project is in need of macOS developers.

https://www.qbittorrent.org/news#tuesday-aug-30th-2022---qbittorrent-v4.4.5-release
https://www.qbittorrent.org/news#monday-aug-22nd-2022---qbittorrent-v4.4.4-release

MACOS: Builds will take a few days to be uploaded.

https://www.qbittorrent.org/news#tuesday-february-15th-2022---qbittorrent-v4.4.1-release

MACOS: Builds will be uploaded in the next days.

https://www.qbittorrent.org/news#thursday-january-06th-2022---qbittorrent-v4.4.0-release

The macOS build will follow.

https://www.qbittorrent.org/news#thursday-november-21st-2019---qbittorrent-v4.2.0rc_20191121_9c1617b9778-release

The macOS builds will follow in a couple of days.

https://www.qbittorrent.org/news#monday-november-19th-2018---qbittorrent-v4.1.4-release

macOS builds will follow.

https://www.qbittorrent.org/news#friday-december-1st-2017---qbittorrent-v4.0.2-release

macOS packages might follow.

https://www.qbittorrent.org/news#monday-august-7th-2017---qbittorrent-v3.4.0beta_20170807_0320f9d5b5e-release

[Piccirello]

I didn't realize this. What's the cause of the delay?

[xavier2k6]

What's the cause of the delay?

You'd have to ask our maintainer....it may be to do with Xcode/Signing, time constraints or they may have been waiting for Qt 6.9.1 to be released, which it since has.......

Not sure what physical mac or indeed macOS Version/Xcode maintainer has access to.

[Piccirello]

macOS builds aren't notarized, so I don't believe the delay is from that. GitHub also has macOS runners that we can use for these builds. I personally would love to see all binaries moved to GitHub.

Is the maintainer in this case @sledgehammer999?

[xavier2k6]

Is the maintainer in this case @sledgehammer999?

Yes

[Piccirello]

@sledgehammer999 can be difficult to get a hold of. Perhaps @glassez or @Chocobo1 have more context?

[glassez]

@sledgehammer999 can be difficult to get a hold of. Perhaps @glassez or @Chocobo1 have more context?

What kind of context are you interested in?

1. @sledgehammer999 is often unavailable (through any communication channels).
2. In recent years, @sledgehammer999 has been repeatedly offered to automate the production of release builds (e.g., transfer them to GitHub), but he has always rejected this.

[Piccirello]

That's exactly the context I was looking for.

Performing production builds locally, in 2025, is a bit surprising. Has there been a reason stated for why builds are still done this way? (Asking in case @sledgehammer999 has previously mentioned it, but of course would be great to hear from him directly)

Building out the infrastructure/GitHub Actions for these builds is surely something many people would be happy to volunteer their time doing. It would also more easily enable notarized builds on macOS (relevant).

[userdocs]

Maybe they have access to better/faster systems locally, compared to default runners, so i'm going to drop this link here since you can get access to decent third party runners pretty affordably.

https://github.com/neysofu/awesome-github-actions-runners

[Piccirello]

Releases are performed, on average, ~once per month, so speed isn't a major concern.

[glassez]

would be great to hear from him directly

So let him answer. Perhaps this will encourage him to think about it again.

[userdocs]

https://www.qbittorrent.org/news

Builds are currently available only from old trusty SourceForge. FossHub either locked the account or has login issues. Time will tell.

ok.

[xavier2k6]

Builds are currently available only from old trusty SourceForge. FossHub either locked the account or has login issues. Time will tell.

This affects the "check for updates" as 5.1.0 will only be offered to users who are using lower versions & those already on 5.1.0 will be informed they're running the latest due to us only relying on FossHub's feed via "check for updates", a backup to alternative/failover feed e.g. -> sourceforge needs to be looked at too.