Gratien D'haese
Gratien D'haese
@jsmeix Why do you label it with "bug"? If you use an external tool to restore LVM volumes then ReaR cannot be held responsible for differences, or perhaps I did...
Wouldn't it be safer to reduce the amount of configuration files in place?
@jsmeix Personally, I think this task is so complicated that release 3.0 would be delayed by many, many months. Perhaps, release 3.1 would make it more feasible?
> With probability one no chance to do something for ReaR next week. Right now got several new security issues assigned that I need to fix at SUSE. No problem...
@jsmeix @schlomo @pcahyna Why checking for ownership? I would compare md5sums of the config files with the original md5sums. I guess now you will say that can may tampered as...
@jsmeix As this issue is "on hold" I was so free to remove the current milestone "2.8" - I hope that was okay for you?
@saschalucas Did you check '/rear/var/log/rear/rear-server1005-rescue.log' why /usr/bin/dracut failed?
@damm620 PR #2907 fixed this and will be part of ReaR v3.0 once it gets released. When will it be released? The answer you can find in https://relax-and-recover.org/events/ - "Why...
> Because in general ReaR is under GPL v3 license I suggest to also have rear-release-notes.txt under GPL v3. > > Hereby I (as one of the by git listed...
@jsmeix okay will do it soon.