#1185 Issue closed: SUSE_LINUX/610_link_systemd_lib.sh fails with "failed to create symbolic link"¶

Labels: cleanup, won't fix / can't fix / obsolete, minor bug

jsmeix opened issue at 2017-01-31 16:43:¶

On my SLES12 test system I did
"rear -d -D mkrescue"
and got in the log (excerpt):

+ source /root/rear/usr/share/rear/build/SUSE_LINUX/610_link_systemd_lib.sh
++ pushd /tmp/rear.UsbkVIYhpMrUQB1/rootfs
++ [[ -d usr/lib/systemd/system ]]
++ [[ ! -d lib/systemd/system ]]
++ ln -sf -v ../../usr/lib/systemd/system /tmp/rear.UsbkVIYhpMrUQB1/rootfs/lib/systemd/system
ln: failed to create symbolic link '/tmp/rear.UsbkVIYhpMrUQB1/rootfs/lib/systemd/system': No such file or directory
++ popd

but I never noticed real issues because of that.

I will have a look.
Perhaps it it a real issue, perhaps it can be ignored.
In any case the code in 610_link_systemd_lib.sh
must be enhanced to not fail with error messages in the log.

Cf.
https://github.com/brainupdaters/drlm/issues/44

jsmeix commented at 2017-05-22 07:21:¶

I post-pone it for a later release (after 2.1 - for now for 2.2)
because no real bad consequence is currently known.

---

[Export of Github issue for rear/rear.]