pcahyna

Note that there are other system extended attributes that the system may depend on, so I am afraid that systems restored with "rsync with remote filesystem not able to manage...

Thanks for the link. Indeed, TSM docs show that the problem is specific to SELinux and symbolic links, so the proposed workaround is probably enough. For RSYNC, see https://github.com/rear/rear/pull/2717#issuecomment-976382378

> Hi, > > Personally I see this less on an issue in ReaR but more an Issue with RedHats autorelabeling. The problem emerged with RHEL 8.4 but worked before....

> If I can help with this issue in any way I would be happy to help. As it seems this issue is relöated to my issue reported to RedHat....

bwelterl convinced me that we still may need some fix for selinux relabelling, because although the particular probem that triggered it has been fixed in systemd, there may be other...

@jsmeix My check was not very thorough. I basically looked ad what Debian is doing - they had stopped shipping `doc/rear-release-notes.txt` already. I also looked at usr/sbin/rear and noted that...

My understanding is that you should get agreements from all authors, or delete their contributions (@lzaoral is that right)? `git log [email protected] [email protected] [email protected] [email protected] [email protected] master -- doc/rear-release-notes.txt` shows...

> A possible way out could be to keep the current doc/rear-release-notes.txt as is but renamed e.g. to doc/rear-release-notes-until-2.7.txt Keeping the current release notes in the repo does not solve...

@jsmeix The main issue for us (at least in my POW) is not the lack of release notes in the package, but the inability to use the upstream source tarball...

> If this is insufficient for what you need, please help with getting agreements from all authors. sure, but we need a plan B here in case we don't get...