mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Provide Github Releases (2) #16122
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#16122
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Korb on GitHub (Oct 1, 2024).
Suggestion
I ask you to post fresh releases not only on qbittorrent.org and fosshub.com, but also here, where there is a discussion of errors and wishes for the application.
Use case
I am quite satisfied with the interaction in the context of improving the application with only one site, and not with several, and even with redirects and timeouts. Here I can immediately download the necessary distribution, unlike the site to which the portable application running on me sends, and from which it automatically downloads not the portable application, but the installer, ignoring the existing copy of qBittorrent during installation.
Extra info/examples/attachments
~ #10005
@xavier2k6 commented on GitHub (Oct 1, 2024):
Also see:
@Aesthermortis commented on GitHub (Oct 1, 2024):
It would be nice to have the files in zip format, since I currently have to use UniExtract to extract the executable and use it in portable mode.
@shama84 commented on GitHub (Oct 2, 2024):
BTW any reason to not have ARM64 Linux version on either Fosshub or Git?
@HanabishiRecca commented on GitHub (Oct 2, 2024):
Because there are no devs wanting to maintain it, obviously.
Due to lack of Linux ARM devices or desire to deal with it, doesn't really matter.
@mzhboy commented on GitHub (Oct 2, 2024):
recommend qbittorrent-nox-static
it's static build binary
@johnyb0y commented on GitHub (Oct 2, 2024):
Yes, also am using this since years. But important: It's the "nox" variant, so no GUI. Only CLI/webinterface.
@HanabishiRecca commented on GitHub (Oct 2, 2024):
I think that's because pretty much all desktop distros have qBittorrent in official repos. So why even bother.
Static binaries mostly needed for embedded/containers.
@shama84 commented on GitHub (Oct 3, 2024):
Not at stake for the moment, Ubuntu ARM64 with PPA is what I'm using.
Just considering option for the future (RPI OS or anything else with snap/flatpack/built.
This setup is rock solid and cost effective, even with many torrents loaded. But yeah my own stuff, maybe not the one used by the most.
@Korb commented on GitHub (Feb 1, 2025):
I don't use the Microsoft Store service on Windows, just like many Google Android users don't use the Google Play service. The mere presence of an application in official stores should not be a reason for the absence of the application in alternative application repositories. In this case, F-Droid (and third-party repositories connected to it) and Github, respectively.I missed the point of the message
@HanabishiRecca commented on GitHub (Feb 1, 2025):
You completely missed the point of the message. It was about
qbittorrent-nox-staticrepo, not about uploading official builds to this repo.