-
-
Notifications
You must be signed in to change notification settings - Fork 758
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
file changed warning: Add message id and path #7080
Milestone
Comments
ThomasWaldmann
added a commit
to ThomasWaldmann/borg
that referenced
this issue
Dec 2, 2023
ThomasWaldmann
added a commit
to ThomasWaldmann/borg
that referenced
this issue
Dec 15, 2023
ThomasWaldmann
added a commit
to ThomasWaldmann/borg
that referenced
this issue
Dec 23, 2023
ThomasWaldmann
added a commit
to ThomasWaldmann/borg
that referenced
this issue
Dec 23, 2023
ThomasWaldmann
added a commit
to ThomasWaldmann/borg
that referenced
this issue
Dec 25, 2023
will be fixed as part of #7976. |
ThomasWaldmann
added a commit
to ThomasWaldmann/borg
that referenced
this issue
Dec 27, 2023
borg 1.4 fixed by #7976 - please test! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Why not another issue about "
<path>
: file changed while we backed it up" 🙃I don't think any of the existing issues #6622 #6989 #6379 propose a global solution that can avoid this message.
However, I want to treat those warnings differently in Pika Backup. For this, I would like to have a
msgid
and the file's path. AFAIK there are no warnings withmsgid
yet but, I don't think that is a problem. Not sure if just adding apath
key to the message would be okay?It would probably be good to do the same thing for 'deleted during backup' or whatever the message is.
Application:
The text was updated successfully, but these errors were encountered: