Johannes Meixner

I know nothing at all about Debian/Ubuntu packaging so I cannot review it - in particular I know nothing whether or not that change could cause regressions when building it...

@gdha I noticed that also you did something in the past for Debian/Ubuntu packaging, so perhaps you might know if increasing the vaule in packaging/debian/compat could cause regressions when building...

I think I will "just merge" it today afternoon. If something breaks with package building on Debian/Ubuntu we can fix it as needed (e.g. revert this change as a band...

@DEvil0000 thank you for your continuous improvements of ReaR!

@anarayancv1 I cannot find `COMMVAULT` in our current ReaR upstream sources, in particular no variable names with `COMMVAULT` or `CV_...` so I am wondering what ReaR you use - it...

From my experience the kernel firmware files need much more space than the kernel modules, see https://github.com/rear/rear/discussions/2640#discussioncomment-908335 that reads (excerpt) ``` ... I get about 200M for the bare ReaR...

See also https://github.com/rear/rear/issues/2386#issuecomment-625109346

In current ReaR 2.7 code there is no longer a global variable RSYNC_PORT. Instead there is a function `rsync_port()` in usr/share/rear/lib/rsync-functions.sh see https://github.com/rear/rear/commit/e0d3c6e8da6d72cfaff580683839397ceab45cf4 which reads (excerpt): ``` ... introducing generic...

@fadamo by the way: Your ``` readonly VARIABLE=value export VARIABLE ``` method in etc/rear/local.conf is a good real world example why `make rear working with "set -ue -o pipefail"`, cf....

Regarding `set -eu -o pipefail` see the whole text in the section "Try hard to care about possible errors" in https://github.com/rear/rear/wiki/Coding-Style that also reads (excerpt) ``` Preferably during development of...