Bug#550938: safe-rm not working any more with perl 5.10.1-5

[Mader, Alexander (N-MSR)]

Hello,






8< ------------------------------------------------------------------ >8
rm -f *.o

Execution of /usr/bin/rm aborted due to compilation errors.
make[1]: [clean] Fehler 255 (ignoriert)
8< ------------------------------------------------------------------ >8

Using /bin/rm directly solved the upgrade problem with perl, but safe-rm




Best regards,
--
Alexander Mader <alexander.ma...@niles.de>

although #550946 is merged with this bug I re-post my observations with safe-rm to have the information in this bug report: *Both* during *and* after the perl-upgrade to 5.10.1-5 safe-rm produced messages like this: Insecure $ENV{PATH} while running with -t switch at /usr/share/perl5/Debconf/Client/ConfModule.pm line 78. Insecure dependency in exec while running with -t switch at /usr/share/perl5/Debconf/Client/ConfModule.pm line 78. debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Keine Berechtigung Global symbol "$PROGRAM_NAME" requires explicit package name at /usr/bin/rm line 106. continued to misbehave after the upgrade as well as after a purge followed by an re-install of safe-rm. To make it clear: Even after successful perl upgrade the safe-rm did not work. This could be seen during run of make for instance. Purging safe-rm from the system an re-installing it with the new perl version already present did not solve the issue.

smime.p7s
Description: S/MIME Cryptographic Signature