Bug#829649: lintian: Spurious error: init.d-script-missing-dependency-on-remote_fs
Package: lintian
Version: 2.5.45
Severity: normal
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
In preparing a new upstream release of the shorewall-init package, I
found that lintian gave the following errors:
E: shorewall-init: init.d-script-missing-dependency-on-remote_fs etc/init.d/shorewall-init: required-start
E: shorewall-init: init.d-script-missing-dependency-on-remote_fs etc/init.d/shorewall-init: required-stop
I checked with upstream was informed that shorewall-init doesn't work
with NFS mount /usr and so assumes /usr is accessible without the need
for $remote_fs in Required-Start and Required-Stop. I inquired in
#debian-devel on OFTC about this to see if it was OK to override. I was
told that this error is spurious as initramfs now mounts /usr and was
suggested to file a bug report against lintian.
Please let me know if I can provide any additional information to help
resolve this.
Regards,
- -Roberto
- -- System Information:
Debian Release: 8.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCgAGBQJXexsIAAoJECzXeF7dp7IP1ncP/iLrjg9C57918NMRL0gLauN9
wdgqLgzFeZ8NgzWNMzfUEvuJcQtZoXb1LQnQ+eId53BM7fF35rfmuRgLk6K3tMAm
C1R4uR+BXs65lJyDLjG/GTHqwTCXeDXe6dISsHrSmSBCKJHJV7RHGnW5eNUzXWYU
rmOuCEz6CeDlO+Ei2oWZT8ahUucsiGL8Xika9KurWwNMHP3u4zjE7ALt9AEePJBO
0Eewpk5mXoK3da4QWDuZsFNfGPX9s7DdQp0MAPLBueyWMXv0G+RrLDdPEdX41yt9
J22XtiSO+biPHNI1OUlJJKiBfyJedY7AzpjwxmAFH4R+8sxfdkSELuZOzvETTijV
KFS+Ejwnca978EMwfdPAFU7NIl6ZEICZG7S76SVdhLrx2n6PXKCQdGxEj/oMhDMJ
zyD121n2dI4VQ0G9CdhLWJNs5cyhVBJ8ZYod6a1/LIKRPsDQenEwY+igZ32ts/L2
e9+zmusK+DpCHCAaYM+UfGmskYjUD4ZyHfwAVwf16lKkt0yrTinZElbySBDlz0Vy
u3h1Be6+WsUzEjxaEkCW2j5C7o9636ZYH10zVcu9aK1YGxIYOgvBMiTWncrZwTRo
sDE3FvML2xnyy78pSRjRPYbDrJL8ZkojpAVuuYanPgEyPA7Kl6K7ov5pUa5EhmSm
3OOvkDtecZ4tAn+hvI19
=JL6U
-----END PGP SIGNATURE-----
Reply to: