-
-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prune error when using forget: yes #297
Comments
Interesting, could you try |
That worked. So why does prune not need the quotes? |
Because the yaml library used here interprets the yes as |
I have "forget" to "prune" in backup command. But I get this error:
|
Hi, I also have a problem with prune option. Right after the backup log, there is the "forgetting" part and always in error like that:
Config extract:
|
I have the same issue with an SFTP backend:
I tried Edit: |
@FunctionDJ I had the same issue and tried |
@pew wow if i had known about i wonder why the two behave differently. i assumed |
Thanks for the workaround! I hope this bug will be solved soon, or this is just an "historic" issue, as I am using autorestic for years now. Thanks @cupcakearmy for the tool, I absolutely love ❤️ |
I was also getting the repo lock error when running a prune. I have had to seperate my scheduled backup tasks into two seperate jobs to overcome the lock issue. |
Describe the bug
The example config has this option for 'forget':
forget: prune # Or only "yes" if you don't want to prune
If I try:
forget: yes
I get the error below:
invalid value for forget option: 1 Error: 1 errors were found
The below works fine:
forget: prune # Or only "yes" if you don't want to prune
Expected behavior
Forget should run without pruning
Environment
Debian 11
The text was updated successfully, but these errors were encountered: