Source: systemtap Source-Version: 2.6-0.1 Severity: important Tags: patch Hi!
This package is using obsolete absolute paths when stating or calling dpkg-statoverride. This has been a compatibility symlinks for a while and got removed in dpkg 1.17.0, I'll reintroduce it in dpkg 1.17.22 but will be removing it again in 1.18.x. Please stop using absolute paths in maintainer scripts, as they will suffer this kind of problem. For more info please see: <https://lintian.debian.org/tags/command-with-path-in-maintainer-script.html> although that lintian check does not currently trigger for this issue, but it should. Attached a patch fixing this, by always assuming that dpkg-statoverride is present, which has been true for a very long time now. Thanks, Guillem
diff --git a/debian/systemtap-runtime.postinst b/debian/systemtap-runtime.postinst index baed52b..32b5c69 100644 --- a/debian/systemtap-runtime.postinst +++ b/debian/systemtap-runtime.postinst @@ -18,8 +18,7 @@ configure) fi # Fixup staprun binary for new group 'stapusr'. - if [ -x /usr/sbin/dpkg-statoverride ] && - ! dpkg-statoverride --list /usr/bin/staprun > /dev/null ; then + if ! dpkg-statoverride --list /usr/bin/staprun > /dev/null ; then dpkg-statoverride --update --add root stapusr 4754 /usr/bin/staprun fi ;;
