mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Prompt to update database message on upgrade does not make sense for a service #3141
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#3141
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 @dsm1212 on GitHub (Sep 29, 2015).
I built/installed 3.3 beta of qbittorrent-nox. I have an init.d script which starts qbittorrent-nox piping output to /var/log/qbittorrent-nox.log using systemctl. Within seconds my root partition was full because this log contained a continuous reprompt for the question about whether the data files should be converted to the new version. I run this from a non-login account so I actually can't run interactively using these config files very easily. I had to modify the init.d script to pipe yes into qbittorrent-nox. I guess this is somewhat self-inflicted using systemctl, but this was pretty nasty to recover from. Honestly I don't think the prompt is necessary. If I'm running it, just upgrade the files. Copy them aside maybe so the originals don't get lost. Much better in my opinion.
thanks
@ngosang commented on GitHub (Nov 6, 2015):
@sledgehammer999 ping.
@sledgehammer999 commented on GitHub (Nov 9, 2015):
I think we should auto-migrate on nox builds.
@glassez better idea?
@glassez commented on GitHub (Nov 9, 2015):
No. Except that to copy the old files somewhere before.
@dsm1212 commented on GitHub (Nov 19, 2015):
Thanks!