I acknowledge that (and as I said, it hasn’t really caused any issues with the backups), I was just responding to this being ”fixed” (above). If it’s not really an issue in the code, maybe we should close this as invalid? (Although I could argue that the message makes it seem as if there is a problem with the code when in fact there isn’t, so the bug could be ”this warning is slightly misleading”. But that’s up for interpretation.)