Confirmed. It's the chmod in Install.pm that does it.
I can reproduce it as follows:
- first run "sa-compile" as root. body_0.so is owned by root after that
- next run 'su debian-spamd -c "sa-compile --quiet"', the message about
chmod is generated, but the permissions end up correct.
After commenting out the chmod in Install.pm and repeating the
sa-compiles as above, the message is gone. Remove the comment and the
message is back.
sub _unlink_or_rename { #XXX OS-SPECIFIC
my ( $file, $tryhard, $installing )= @_;
# _chmod( 0666, $file );
my $unlink_count = 0;
while (unlink $file) { $unlink_count++; }
return $file if $unlink_count > 0;
...
So it looks that they way it is used above is not so harmful afterall,
but it stll seems like a strange construct. I can't immediately see what
purpose it serves to change the permissions of a file before unlinking it.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
