One thing I am wondering about with the fixed suse-missing-rclink rpmlint rule is

simon@linux-82h5:~/Work/home:mrmorph:branches:system:snappy/snapd> sudo zypper install /var/tmp/build-root/openSUSE_Tumbleweed-x86_64/home/abuild/rpmbuild/RPMS/x86_64/snapd-2.24-1.x86_64.rpm Retrieving repository 'Main Update Repository' metadata ............................................................................[done] Building repository 'Main Update Repository' cache .................................................................................[done] Loading repository data... Reading installed packages... Resolving package dependencies...

The following package is going to be upgraded: snapd

1 package to upgrade. Overall download size: 4,7 MiB. Already cached: 0 B. After the operation, additional 77,9 KiB will be used. Continue? y/n/? shows all options: y Retrieving package snapd-2.24-1.x86_64 (1/1), 4,7 MiB ( 23,8 MiB unpacked) Checking for file conflicts: .......................................................................................................done Installing: snapd-2.24-1.x86_64 ..............................................................................................[done] Additional rpm output: SysV service snapd.autoimport does not exist SysV service snapd.system-shutdown does not exist /usr/sbin/systemd-sysv-convert: line 62: /var/lib/systemd/sysv-convert/database: No such file or directory Please reboot, logout/login or source /etc/profile to have /snap/bin added to PATH.

This seems to be a known problem (see https://bugzilla.suse.com/show_bug.cgi?id=982303) but nobody fixed it yet.

I don't think we should ship the two extra systemd units. They are only designed for core systems and if we ever make a mistake in the mechanism that prevents them from running on classic systems we would just add trouble.

@zyga We're shipping them on Fedora, Ubuntu and Debian in the deb/rpm package so we should do the same here as well.