http://bugzilla.suse.com/show_bug.cgi?id=1013276 http://bugzilla.suse.com/show_bug.cgi?id=1013276#c1 --- Comment #1 from Ralf Bueker --- version from https://github.com/rear/rear (cloned yesterday) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1013276 http://bugzilla.suse.com/show_bug.cgi?id=1013276#c2 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |UPSTREAM --- Comment #2 from Johannes Meixner --- A SUSE customer uses openSUSE Tumbleweed with current ReaR master code from GitHub? Please report such issues at ReaR upstream, see http://relax-and-recover.org/support/ as GitHub issue at https://github.com/rear/rear/issues As far as I see ISO_DEFAULT="unattended" is only used for the backup method BAREOS. Does the customer use the backup method BAREOS? If yes there is nothing what I could do because I cannot help with issues for third-party backup methods. In case of issues for third-party backup methods it is best to report them at ReaR upstream where (hopefully) someone could help. If the customer does not use the backup method BAREOS it does not make sense to use ISO_DEFAULT="unattended". As basically always in bug reports no reason behind is told. Why does customer sets ISO_DEFAULT="unattended" - i.e. what behaviour does the customer like to get with that setting? Why is the default ISO_DEFAULT=boothd not what the customer likes to have? In any case, this issue is not caused by openSUSE but an ReaR upstream issue. -- You are receiving this mail because: You are on the CC list for the bug.