Increase archive_tag.ui maximum keep_ limit.#2282
Conversation
|
Its a hard no from my side to this change.
|
|
Well, there is no limit in upstream borg, so why do we have one here? This is my use case, I don't need more than that, maybe we can put 9999 in or some other number of your discretion accomadating this: 
It breaks my way of using vanilla Borg/Borgmatic, hence why I considered it a bug. |
Ok, i can see your view point if you look at it like this. Maybe they limited for some reason. Could be some size limit in a database or a Vorta dependency or what. The strange numbers, just shy of the next bit, make me pause. Lets see if someone more involved can tell more about this, but it should also be this old issue considered: #1082. |
|
I have used this branch extensively and there seem to be no regressions of any kind. I assume the default values are an artifact of either Qt Creator or Qt Designer as recommended to be used here: https://vorta.borgbase.com/contributing/#working-on-the-gui |
|
Ahh, it looks like the old PR is not yet in the version released when you do brew install --cask vorta, there I ended up with 99 weekly and 99 monthly which is not nearly enough and I forgot trying the master without any changes. My apologies 🫠 |
No worries. 👋🏻 |
|
Should be fine to just have a higher maximum. Thanks for the addition. Will release this today. |
3 participants
Description
I increase the keep_hourly, keep_daily, keep_weekly, keep_monthly and keep_yearly to a higher but still sane number, I chose 65535.
Related Issue
#2280
Motivation and Context
I wanted to apply this regimen (in borgmatic-syntax for simplicity) to my backups and it wasn't possible before:
How Has This Been Tested?
Code review and thorough test of application after change.
Screenshots (if appropriate):
Types of changes
Checklist:
I provide my contribution under the terms of the license of this repository and I affirm the Developer Certificate of Origin.