Hi! On Tue, 2022-05-24 at 09:36:45 +0200, Harald Dunkel wrote: > Package: dpkg > Version: 1.20.9 > Severity: wishlist
> To avoid confusion the man page to dpkg-statoverride should > mention explicitly that it does *not* run chmod or others to > actually change the access permissions to already installed > files, or to files that are not part of a Debian package, or > to files that are generated by a package maintainer script. It does not change the owner or permissions as long as --update is not used, otherwise it will change the attributes for any pathname in the filesystem regardless of it being (currently) known dpkg or not. If no --update is used, then if the pathname is "never" unpacked then it will never receive an override, yes. (I'm assuming the confusion is about the attribute change semantics and not whether it forks the chmod(1) and chown(1) tools though.) But I can see how this can be not entirely clear from the man page and I'll try to clarify. Thanks, Guillem
